RNBW.wiki
🇬🇧
🇷🇺Русский 🇬🇧English 🇪🇸Español 🇨🇳中文 🇩🇪Deutsch

Public RNBW data

Everything shown on this site is also served to machines as JSON. No keys, no sign-up, open CORS — call it from a browser, a script or an agent. The data is read by our server straight from the Base blockchain rather than repeated from aggregators.

Live state

GET https://rnbw.wiki/api/dashboard.json — everything at once, updated from contract events and once a minute on a timer.

FieldWhat is inside
stakingthe contract state in wei: totalPooledRnbw, totalShares, rewardRate, undistributedFees, cashbackReserve, exitFeeBps, dripEndTime, lastSyncTime, totalCashbackAllocated
apryield in percent a year: now instantaneous, d7, d30, d90 averages over windows, perDay the daily drip in wei
priceusd, mcap, change24 — from CoinGecko, refreshed every two minutes
poolthe main RNBW/USDC pool on Uniswap v4: tvl, vol24, fee, apr24
balRNBW balances of fifteen project addresses, in wei. The keys are the same as on the flows diagram
tvlpool size by day, [timestamp, RNBW]
feedthe last 200 contract events with address and hash
block, updated, sourceblock number, snapshot time, and how the data was obtained: ws or poll

Token amounts are strings, not numbers. Values in wei do not fit in a double: 23760886701054000000000000 loses precision when parsed with an ordinary JSON.parse. Read them as BigInt or Decimal.

Time series

AddressFormatStep
/api/tvl.json[timestamp, RNBW in pool]daily, since 31.03.2026
/api/apr.json[timestamp, 7-day, 30-day, 90-day] in percentdaily
/api/pool.json[timestamp, volume $, fees $]daily, since 14.03.2026
/api/exitfees.json[timestamp, exit fee in wei]per event

Timestamps are Unix seconds in UTC. The series are rebuilt by the collector, and old points are not rewritten.

Every entry and exit

The full staking history is split into chunks of 250 events — nobody needs to download a megabyte in one file.

01

GET /staking/events/index.json

Returns {"total": N, "chunk": 250, "chunks": K}. Chunks are numbered from oldest to newest, so only the last one changes and the rest can be cached indefinitely.

02

GET /staking/events/000.json … NNN.json

An array of events, [timestamp, type, RNBW, address, hash]. Type: 1 for an entry, 0 for an exit. The amount is rounded to whole RNBW; for the exact value in wei, take it from the blockchain by hash.

03

GET /staking/events/bal/000.json … NNN.json

How much the address had in staking after each entry: {"0183bfeff7": 7828} — the key is the last ten characters of the transaction hash, the value is whole RNBW. One file per feed chunk; exits are not here. The key is the hash rather than the row number, so the order of rows in the feed does not affect the lookup. This is not the sum of deposits: a position grows with the drip, and an address whose three entries add up to 104,626 holds 104,628.

Live stream

wss://rnbw.wiki/ws — a socket with contract events in real time. On connect you get a snapshot of the state, then changes as blocks arrive.

Keep your own heartbeat. Cloudflare drops an idle socket after roughly 100 seconds, and protocol-level pings are not enough for it — send a text ping every 30 seconds. We stepped on this first so you would not have to.

Examples

TaskHow
30-day yieldcurl -s https://rnbw.wiki/api/dashboard.json | jq '.apr.d30'
pool size in RNBWcurl -s https://rnbw.wiki/api/dashboard.json | jq '.staking.totalPooledRnbw | tonumber / 1e18'
recent exitscurl -s https://rnbw.wiki/api/dashboard.json | jq '.feed[] | select(.event=="Unstaked")'
the whole TVL seriescurl -s https://rnbw.wiki/api/tvl.json

Rules of use

01

No keys needed, no limits

But go easy: the files are static, and polling more than once a minute is pointless — they do not change that often. If you need every second, the live stream beats polling.

02

Check against the primary source

All of the above is derived from the contract 0x288ea8Bcb51d53aD361D786EFa904C401904aF70 on Base. If a number matters for a decision, ask the contract directly: we can fall behind or make a mistake, the blockchain cannot.

03

A link is welcome but not required

The data is public and belongs to the blockchain, not to us. Take it and use it.