> For the complete documentation index, see [llms.txt](https://docs.ichigeki.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ichigeki.app/security/custody.md).

# Custody

ICHIGEKI is non-custodial by construction, not by policy. There is no ICHIGEKI wallet that could hold your funds even briefly.

## The model

* **You control your wallet.** ICHIGEKI connects to it; it never holds keys.
* **You own your Derive subaccount.** Positions and collateral live in a subaccount controlled by your wallet on Derive Chain — Derive Protocol is self-custodial at the contract level.
* **You sign every order.** At launch, order signatures come from your wallet directly. In Phase 2, you may optionally approve a narrowly scoped session key (see below).
* **Bridge transactions go from your wallet.** Both funding legs are signed by you and move funds between addresses you control and Derive's audited deposit contracts. Funds never pass through an ICHIGEKI-controlled address.
* **There is no ICHIGEKI master account.** No omnibus wallet, no pooled customer collateral, no server-side trading key with access to user funds. That architecture was considered and rejected: it would concentrate custody, security and regulatory risk in exactly the place users cannot see.

## Session keys (Phase 2)

Derive supports session keys: a secondary key your wallet authorizes to sign orders on its behalf, with a defined scope and expiry. When ICHIGEKI enables trading beyond direct wallet signatures, session keys will be:

* **Explicitly approved** by a transaction you sign
* **Narrowly scoped** — order signing for your subaccount, not withdrawals
* **Expiring** — time-limited, with revocation exposed in the interface
* **Yours to revoke** at any time

A session key improves UX (no wallet popup per order) without transferring custody: it cannot move funds out of your subaccount.

## What ICHIGEKI can and cannot do

|        | Can                                     | Cannot                                                |
| ------ | --------------------------------------- | ----------------------------------------------------- |
| Read   | your public positions, orders, balances | your private keys                                     |
| Prompt | you to sign orders and deposits         | sign anything for you without an approved session key |
| Route  | your signed orders to Derive            | withdraw, transfer or redirect your funds             |

## The honest caveat

Non-custodial does not mean risk-free. Your positions depend on Derive Protocol's contracts and on Derive Exchange's operated matching engine and API. Custody risk is removed; protocol and operational risk are not. Read [Risks](/security/risks.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ichigeki.app/security/custody.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.