Method
What the vault will and will not say
All tracks and rankings derive exclusively from onchain receipt matches via the Robinhood Chain adapter. Unverified or stalled steps remain visibly stalled until corrected by the performer.
Questions
What counts as a verified cut?
A receipt with status 1, sent by your wallet, whose logs show the action the cut prescribes.
Does LINEAGE send anything for me?
No. You send every transaction yourself, from your own wallet, to the protocol itself.
What if a cut reverts?
It is recorded as attempted. The groove stays open until a receipt answers yes.
Is a track advice?
No. It is a record of what someone did. The chain says it happened, not that it was wise.
Who is the performer on a receipt?
receipt.from, and nothing else. On this chain the sender inside a swap log is the router, not the person, so the log is only asked what happened.
What happens when the vault is empty?
The charts print their empty state and wait. No row is ever written so that a page has something to show.
Provenance
Where the rows on this site came from
- Source
- https://rpc.mainnet.chain.robinhood.com — Robinhood Chain, chain id 4663, keyless JSON-RPC
- Method
- Targeted, protocol-first (v2). (1) eth_getLogs on Morpho Blue 0x9d53d5e3bd5e8d4cbfa6db1ca238aea02e651010 over blocks 58646341..61646340, paged so no query matched more than 10000 logs; the user of each Supply/SupplyCollateral/Borrow/Repay/Withdraw/WithdrawCollateral was read from the indexed onBehalf topic (topic2 for Borrow/Withdraw/WithdrawCollateral, topic3 otherwise) and kept only if it is an EOA. (2) eth_getLogs for ModifyLiquidity on the v4 PoolManager 0x8366a39cc670b4001a1121b8f6a443a643e40951 over blocks 61586341..61646340; the wallet behind a sample of those transactions was read from receipt.from, dropping bot-scale senders. (3) For the 26 most active Morpho EOAs and 12 position wallets, its ERC-20/721 Transfer logs from and to the wallet plus its Morpho transactions over the window; every hash was read with eth_getTransactionReceipt and kept only at status 1 with receipt.from equal to the wallet. (4) Receipts decoded with the verifier's own rules (web/src/lib/verify.ts): a Morpho event bound on onBehalf, then v4 Swap/ModifyLiquidity, then any Morpho event, then an ERC-20 Transfer; nothing decodable is not a cut. (5) A track is ten of the composer's own receipts in the order sent, the chronological run that mixes the most protocol actions, with at most 3 plain token moves. (6) A replay is another candidate wallet's own verified receipt, sent after the composer's cut, that the verifier accepts for that cut (same kind, same protocol contract); the earliest such receipt per cut, at most 10 cuts per performer per track. Titles count the real cuts; hints and notes are display strings; no number here is a market fact.
- Generated at
- 2026-09-13T03:59:05Z
- Command
- node output/LNGE/supabase/seed/build_showcase.mjs --window 3000000 --positions-window 60000 --tracks 10 --morpho-candidates 26 --position-candidates 12 --morpho-tracks 6 --max-performers 16 --max-rows-per-performer 10
Titles, hints and notes are display strings written in the vault’s voice. Every hash, block, address and count is a value read back from chain 4663. No number on this site is a market figure — there is no price, no volume and no valuation anywhere in the vault.