Economics
JIKA has no token, no fee and no reward. It holds no liquidity. This page lists every cost in the system and who pays it.
Who pays for what
| Cost | Amount | Paid by |
|---|---|---|
| Program deploy | about 2.11 SOL rent for 302,952 bytes of program data, plus a buffer of about the same returned after the deploy | the deployer, once |
| A feed | 0.0059 SOL rent for a 720-byte account | whoever calls create_feed, anyone |
| Adding a pool | no rent, only the transaction fee | anyone |
| Keeping a feed fresh | about 0.043 SOL a day for one update every 10 seconds at the base fee (8,640 transactions a day; feeds can share a transaction) | whoever relies on the feed |
| Reading a price | 6,400 compute units inside the reader's own transaction | the reader |
Why updates are not rewarded
Updaters get nothing from the program. Freshness is paid by whoever relies on a feed, the same model as pull oracles. A feed nobody updates is refused by read, never served stale. Pool owners add their pools because being counted is free.
What an attacker pays
On TERMINAL, a thin token with 44.93 SOL of depth within 2%:
| To move the price | With nobody updating | With a keeper updating every 10 s |
|---|---|---|
| 1% | 14.32 SOL over 80 s | 360.51 SOL to hold the market (estimate) |
| 5% | 69.16 SOL over 110 s | 2,595 SOL to hold the market (estimate) |
| 20% | 241.51 SOL over 260 s | 24,230 SOL to hold the market (estimate) |
With a keeper, spiking every 10 seconds moved the price 0.00% after 60 spikes; only holding the whole market works, and that costs arbitrage every slot. Every push is an arbitrageur's profit, so they show up because it pays.
The rule for a lender
- Run a keeper, or pay for one: one
updateper feed every 10 seconds. - Value collateral at the steady price, and refuse reads whose band is wider than your margin.
- Without a keeper, keep what can be borrowed against a token below its walk cost. For TERMINAL, a 20% walk costs about 242 SOL ($29k) and 4 minutes 20 seconds.
Day one
JIKA cannot become one more liquidity fragment: it holds none. To go live needs the deploy, the USDC feed first (USDC-quoted pools need it), then one feed per token, and a keeper. Readers in an app need no integration; programs read through CPI.
NextGetting started