Overview
JIKA gives every token on Solana one on-chain price, computed inside a Solana program from the DEX pools that trade it, with a band that says how far to trust it. There is no publisher, no issuer approval and no admin key. Any program reads a price with one CPI.
The name is the Japanese word jika: what a Tokyo sushi counter writes next to the fish when there is no list price, only the market. A JIKA price exists the moment a token has a pool.
What you get from one read
| Field | Meaning | Unit |
|---|---|---|
price_q64 | The steady price, the one to value things at | Q64.64 quote raw units per base raw unit |
steady_tick | The same price as a tick | 1.0001^tick quote per base raw unit |
spot_tick | The depth-weighted median of the pools right now | tick |
conf_ticks | Half-width of the band around the price | ticks (1 tick = 1 basis point) |
depth | SOL that trades within 2% of the price, summed over pools, each pool counted only up to the depth it has held | lamports |
top_share_bps | The largest single pool's share of that depth | basis points |
last_update_slot | When the price was last computed | slot |
base_decimals, quote_decimals | To turn raw units into whole tokens |
read refuses rather than return a price the caller said it cannot use: still warming up (NotLive), older than max_age_slots (Stale), or a band wider than max_conf_ticks (TooUncertain).
Who it is for
- Lending markets that want to accept long-tail tokens as collateral. Pyth only prices assets its publishers choose; JIKA prices any token with a pool.
- LPs in a fresh token's concentrated pools who want to know where the whole market is, not only their own pool.
- Perpetuals, options and liquidation keepers that need a mark price no single pool can drag.
What it is not
- Not a feed someone pushes. Nothing runs on its own: anyone calls
update, andreadrefuses a price that is too old. - Not a TVL number. Depth is what can trade within 2% of the price, never the size of a pool.
- Not manipulation-proof by decree. What a manipulation costs and what it buys is measured on real pools in Security and trust.
Where things are
| Page | Read it for |
|---|---|
| How it works | The median, the confirmed depth, the band and the steady price, step by step |
| Architecture | Accounts, PDAs, the seven DEX adapters, compute |
| Security and trust | The measured attack table and every threat with its defence |
| Economics | Who pays for what: rent, keeper, attack costs |
| Getting started | Create a feed, add pools, run a keeper, read a price |
| Integration | CPI from your program, and the checks to make |
| API reference | Every instruction, account and field |
| Error reference | Every error code and what to do about it |
| FAQ | The questions people ask first |
Status
Program id 3EgkAd9FSZhofeh7MZVPk7QdSVKQUCuz8qyYQ2xabzdP (Anchor 0.30.1). The program is built and tested (34 tests: 13 unit, 16 against the real mainnet DEX programs and pool snapshots, 5 for the JavaScript mirror) and runs on a local validator with cloned mainnet programs and pools. It is not deployed to devnet or mainnet yet, and it has no external audit yet.