> 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/project/roadmap.md). # Roadmap Three phases, each shippable on its own. Estimates are indicative engineering effort and exclude external approvals. ## Phase 1 — Read-only prototype *Live market truth, zero trading surface.* * Connect wallet * Read active BTC options from Derive's public API * Identify the nearest daily expiry * Display the liquid strikes as a quote-driven ladder * Stream quotes and the settlement countdown * Model premiums, fees and maximum loss exactly as the confirmation screen will **Indicative effort:** 1–2 weeks. ## Phase 2 — Trading on testnet *Real signatures, fake money.* * Create or connect a Derive subaccount * Register scoped, expiring session keys * Submit and cancel signed market/limit orders (against `api-demo`) * Display fills, positions and settlement history * Error and recovery states for every order path **Indicative cumulative effort:** 4–6 weeks. ## Phase 3 — Production funding and launch *Money moves; paperwork lands.* * Integrate Robinhood Chain USDG → Arbitrum USDC routing (LI.FI/Across) * Integrate Arbitrum → Derive Chain Socket deposits * Bridge monitoring and per-leg recovery states * Compliance and location controls * Security review and production QA * **Commercial confirmation with Derive** — written answers on: embedded-frontend permission, a stable `client` identifier, the builder fee, production REST/WS rate limits, compliance and geographic requirements, market-data usage, expected support for daily BTC expiries, Robinhood Chain as a future deposit origin, and use of Derive's name in execution disclosures **Indicative cumulative effort:** 8–12 weeks, excluding external approvals. ## After launch Not commitments — candidates, in rough order of pull: * ETH dailies (already surfaced in the interface as coming soon) * WebSocket market data replacing REST polling * Sell-to-close before expiry, where the book supports it * A direct or composed Robinhood Chain → Derive route, if one becomes supported ## Token A token launch is planned. Full details (supply, distribution, fee routing) will be published before launch. One commitment is fixed now: * The team will buy 10% of the token supply at launch and lock it for 12 months. ## What will not change * Non-custodial, always. No omnibus accounts, no pooled collateral. * Truthful labeling: exact settlement timestamps, "0DTE" only when literally true, quotes only when they exist. * One day. One strike. --- # 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/project/roadmap.md?ask=&goal= ``` `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.