Methodology
No source, no data.
Everything ILMI draws can be traced to a block and a transaction on Robinhood Chain. This page explains what is read, how it becomes form, and what is deliberately left out.
01
Sources
- https://rpc.mainnet.chain.robinhood.com
Public JSON‑RPC. Used for eth_getLogs, code, balance, nonce, token metadata calls and block timestamps. - https://robinhoodchain.blockscout.com
Blockscout. Used for public contract names and verification status, and every deep link in the app.
Chain ID 4663 (0x1237). Native asset ETH.
02
What an event is
An event is one log entry in a block. For a contract, ILMI reads every log the contract emitted and decodes known signatures — Transfer, Approval, Swap, Sync, Deposit, Withdrawal. Transfers from the zero address are shown as mints, to it as burns. Unknown logs are kept and labelled by their raw signature.
For a wallet, ILMI reads ERC‑20 and ERC‑721 Transfer logs where the address appears as sender or recipient, across every token on the chain.
03
How form is derived
Event occurrence
→ Disturbance
Each log becomes one deformation of the surface. No log, no deformation.
Recency
→ Prominence
Newer events sit on outer rings and burn brighter. The single newest event is scarlet.
Repetition
→ Rhythm & density
Events are bucketed into time rings by block. Busy periods produce dense, rippled strata.
Amount
→ Magnitude
For ERC‑20 values of the same token, height is log‑scaled within that token’s observed range. Different tokens are never compared.
Counterparty
→ Angle
The other address is hashed to a fixed angle. The same counterparty always appears in the same direction.
Direction
→ Push or pull
Inbound value pushes the surface outward; outbound pulls it in.
The mapping is a pure function of the data: the same events always produce the same field. Where amounts are not comparable — NFTs, approvals, unknown logs — each event receives the same fixed occurrence height. Nothing is randomised.
04
What is not available
- USD prices or market value — Robinhood Chain logs carry no prices.
- Plain ETH transfers inside internal calls — only token logs and the address’ own logs are read.
- Activity older than the scanned block window — the public RPC limits how far one pass can reach.
- Identities behind addresses — an address is shown as an address unless Blockscout has a public name.
- Transaction status for every event — a log only exists if its transaction succeeded, so failures are not shown.
05
Freshness
On first load ILMI scans backward from the chain head in windows until it has enough events or reaches its block budget. The scanned range is always printed on the page.
While the page is open, ILMI asks the RPC for new logs since the last block it saw, every few seconds. New events rise into the outer ring. The WATCHING indicator only shows when that check is succeeding; if the RPC fails or rate limits, it says so and backs off.
Timestamps are fetched per block for the most recent events. Where a timestamp was not fetched, ILMI shows the block number instead of estimating a time.