INDEX · SELECTION BASKET
RWA
highThe basket with the highest rate ceiling in the selection snapshot: everything above the ceiling is dropped as suspected broken rather than taken as a find.
Movement is high: the criterion carries the widest 30-day mean ceiling in the whole selection snapshot. A high ceiling is not a promise but a boundary beyond which a figure is treated as suspect.
PUBLISHED BASKET CRITERION — VERBATIM
ETH/BTC pair on Velodrome or Aerodrome, TVL >= $1M, 30d mean <= 350%
Selection snapshot: 2026-09-08 · source: DeFiLlama yields.llama.fi/pools · the RWA basket has no center catalogue — criterion from the selection snapshot
RWA · SNAPSHOT CONTENT
What is inside right now
This is the published shortlist of the selection, not a list of holdings. A pool on this list means one thing only: it passed the basket criterion on the snapshot date. The decision about money is taken separately, by a person.
| Pair | Chain | Venue | TVL | Stage | Note |
|---|---|---|---|---|---|
| WETH-CBBTC | Base | aerodrome-slipstream | $9.9M | passed screening | ETH/BTC pair on Velodrome/Aerodrome |
| CBETH-CBBTC | Base | aerodrome-slipstream | $1.6M | passed screening | ETH/BTC pair on Velodrome/Aerodrome |
| WETH-USDC | Base | aerodrome-slipstream | $8.4M | passed screening | ETH/BTC pair on Velodrome/Aerodrome |
| USDC-CBBTC | Base | aerodrome-slipstream | $7.2M | passed screening | ETH/BTC pair on Velodrome/Aerodrome |
| USDC-CBBTC | Base | aerodrome-slipstream | $4.0M | passed screening | ETH/BTC pair on Velodrome/Aerodrome |
| AERO-CBBTC | Base | aerodrome-slipstream | $1.1M | passed screening | ETH/BTC pair on Velodrome/Aerodrome |
Selection snapshot: 2026-09-08 · source: DeFiLlama yields.llama.fi/pools · passed screening: 38 · pools scanned: 15 589
There are no positions in pools right now: funds were returned to the founder on 24 Sep 2026 — a recorded fact, not “no data”. details and proofs →
QUEUE · TOP-50
Queue into this index
A ranked list of candidates, not a quality score: the order comes from the selection-snapshot criterion printed above the table — the snapshot date is below the table. Every row shows whether the candidate passes and which rule it fails.
Reading the queue…
ENTRY PATH
How an entry happens
Six steps from a row in a feed to a position. No step moves money on its own.
01Scan
The engine takes the whole pool feed and stamps the snapshot with a time: from there on snapshots are compared with snapshots, not memory with memory.
02Criterion
Candidates that pass the published basket criterion remain. A rejected candidate leaves with a named reason, never silently.
03On-chain re-verification
The candidate's numbers are re-read on chain, not taken from the feed's word. If they disagree, the candidate stops here.
04Human confirmation
The founder looks at the candidate and says yes or no. Without that word the next step does not happen.
05Entry
The key signs exactly the plan that was confirmed. Key and declared address are matched before the plan is built; a mismatch is a stop.
06Monitoring
The position is re-verified on chain daily. A disagreement between the ledger and the chain halts the payout loop instead of hiding in a report.
The last word before money moves belongs to a person. The engine searches, measures and stops; the founder confirms the entry.
RISKS
Risks of this basket
What breaks in a basket built this way — and how it becomes visible.
Issuer and redemption
A real-world-asset instrument is worth exactly what the issuer's promise to buy it back is worth. The redemption right, its term and the creditor queue are the risk — and none of it shows up in the rate.
What is in the basket today
On the current snapshot this basket's criterion selects ether and bitcoin pairs on two venues. While such pairs are in it, the risks that apply are venue, range and impermanent loss — not issuer risk. The criterion is printed verbatim above; check it yourself.
A high rate as a signal
A rate above the ceiling almost always means a broken calculation at the source or a short emission, not a find. Such a candidate is dropped and named aloud in the rejection reasons rather than hidden.
VERIFY
Where to verify
Every statement above can be checked without us. Four places.
- Transparency: addresses proven on chain and what is connected/transparency
- Public pool selection: candidate stages and rejection reasons/kanban
- Analytics: measured values, each with its own time/analytics
- Selection snapshot file in the repository
frontend/lib/pool-board/selection.json