> 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/getting-started/funding.md).

# Funding

Options on ICHIGEKI are premium-paid and settled in USDC on Derive Chain. If your funds start on Robinhood Chain, they travel two legs to get there. There is currently no confirmed direct Robinhood Chain → Derive Chain bridge, so ICHIGEKI orchestrates the composed route below — and keeps both legs visible.

## The route

```
Robinhood Chain USDG          (chain id 4663)
        │
        │  LI.FI / Across
        ▼
Arbitrum USDC                 (chain id 42161)
        │
        │  Derive Socket connector
        ▼
Derive Chain USDC             (chain id 957)
        │
        ▼
your Derive subaccount
```

## The guided flow

1. Connect Robinhood Wallet or another compatible EVM wallet.
2. ICHIGEKI requests a live USDG → Arbitrum USDC quote from LI.FI.
3. You review the output amount, fees, slippage and estimated duration.
4. You sign the Robinhood Chain bridge transaction.
5. ICHIGEKI tracks the transfer until USDC arrives on Arbitrum.
6. The interface prompts you to switch networks to Arbitrum.
7. You sign the Derive Socket deposit transaction.
8. ICHIGEKI detects the funded subaccount and enables trading.

The interface presents this as one **Fund ICHIGEKI** workflow, but it is two separate bridge operations and it stays labeled that way. Every transaction is signed from your wallet; funds never pass through an ICHIGEKI-controlled address.

## Constraints — read before bridging

* **Not atomic.** The transfer crosses three chains in two independent legs. One leg can complete while the other has not started. ICHIGEKI shows per-leg status and recovery states, but a stalled leg is a real state you may sit in.
* **Quotes are live only.** Bridge routes, fees and output amounts change; ICHIGEKI requests them at the moment of funding and never caches a quote.
* **You need gas.** The first leg needs native gas on Robinhood Chain; the deposit leg needs gas on Arbitrum. Bridging your entire balance with nothing left for gas will strand the flow.
* **Bridge completion is not account funding.** USDC arriving on Arbitrum is not the same as USDC in your Derive subaccount. ICHIGEKI tracks both separately and only enables trading when the subaccount is actually funded.
* **The canonical exit is slow.** Withdrawing from Robinhood Chain through the canonical Ethereum bridge carries a challenge period of approximately seven days. It is unsuitable for normal onboarding or quick round-trips; the LI.FI/Across route exists precisely to avoid it on the way in. Plan withdrawals accordingly.

## Alternatives

Derive accepts USDC deposits from Ethereum, Arbitrum, Optimism, Base and HyperEVM. If you already hold USDC on any of those networks, you can skip the first leg entirely and deposit directly via the Socket connector.


---

# 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/getting-started/funding.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.