Live mode & data
The platform runs in two modes, and uses live, keyless on-chain and market data sources throughout.
Public vs Live
| Mode | Data | Use |
|---|---|---|
| Public | Curated demo data | Presentations, walkthroughs, public viewing. |
| Live | Real on-chain reads + live market data | Real operations — actual balances, clients and pool metrics. |
In Live mode, a client is defined as a unique address with a real deposit. Spam and address-poisoning are filtered out by valuing every transfer at its real per-contract price and discarding dust below a minimum USD threshold — so client and AUM counts reflect genuine capital.
Data sources (no API keys required)
| Source | Used for |
|---|---|
DefiLlama — yields.llama.fi/pools | Live yields, TVL and momentum across ~13,000 pools on 50+ chains. |
DefiLlama — coins.llama.fi/prices/current/ | Token prices by contract, for honest USD valuation and spam filtering. |
Public RPC — ethereum-rpc.publicnode.com | Direct on-chain reads (balances, token data). |
Blockscout — eth.blockscout.com/api | Transfer history and on-chain analytics. |
| Block explorers | Etherscan / BscScan / BaseScan for verification links. |
Live metrics
In Live mode the console derives, directly from chain:
- AUM — sum of real deposits across L1→L4, broken down by index.
- Clients — count of unique real depositors.
- Deposits / withdrawals — inflow and outflow to date.
- Pool metrics — live APY, TVL and momentum for the candidate set.
- Market signals — sector and chain flows, entry/exit pressure.
Graceful fallback
Live data pipelines (e.g. the DefiLlama signal feed) degrade gracefully: if a source is briefly unavailable, the console falls back to last-known/curated values rather than failing, and flags the state. Operations never depend on a single fragile call.
Refresh cadence
Market signals and pool scoring refresh on a regular cadence (on the order of every 15 minutes) so decisions are made on current data without hammering public endpoints.