> 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/readme.md).

# What is ICHIGEKI

一撃 — "one strike." One day. One strike.

ICHIGEKI is a non-custodial interface for daily BTC, ETH & SOL options. You log in with an email or your own wallet, fund from whatever chain your money already lives on, pick a strike on the nearest daily expiry, see the exact premium, fees and maximum loss, and the order is signed with keys only you control. Execution, liquidity, margin and settlement are provided by [Derive](https://derive.xyz).

That sentence is the whole product. ICHIGEKI does not run a matching engine, does not hold your funds, and does not make markets.

## What ICHIGEKI is

* A simplified front end for existing daily BTC, ETH and SOL options order books
* Non-custodial: your keys, your own trading subaccount, your signatures
* Buy-only at launch — the most you can lose is the premium you paid plus fees
* Countdown-first: the exact settlement timestamp and the remaining time are always visible
* Three markets: BTC, ETH and SOL, each on its own consecutive daily expiries

## What ICHIGEKI is not

* Not an exchange. Orders match on Derive's order book; options settle on Derive Chain.
* Not chain-native to wherever you fund from. The chain your money starts on is a funding detail; the option lives and settles on Derive Chain.
* Not a source of guaranteed liquidity. ICHIGEKI shows only what is actually quoted; when the book is quiet, the interface says so.
* Not financial advice.

## How a trade works, in one paragraph

The venue lists consecutive daily BTC, ETH and SOL options that settle at 08:00 UTC. ICHIGEKI reads the chain for the market you pick, keeps the strikes with live asks near the current index price, and shows each one with its exact premium in USDC. You choose a strike, review cost, max loss and breakeven, and confirm. The order goes to the book; if it fills, the position sits in your own subaccount until it settles in cash at expiry.

## Where to go next

* [How it works](/getting-started/how-it-works.md) — the architecture and who does what
* [Funding](/getting-started/funding.md) — depositing from any supported chain, quote first
* [Daily options](/product/daily-options.md) — the contract, the clock, and what "0DTE" actually means
* [Risks](/security/risks.md) — read this before trading

***

ICHIGEKI is a non-custodial interface. Execution, liquidity, margin and settlement are provided by Derive. Options involve risk: a bought option can expire worthless — maximum loss is the premium paid plus fees. Not available in restricted jurisdictions. Nothing here is financial advice.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ichigeki.app/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
