HostFWWETH vs RDK — price, size and safety, side by side
FWWETH (Ethereum) vs RDK (Base) — every figure is the freshest dated measurement we hold for that token, never a live-feed guess. Prices stamped 2026-09-17T20:24:07 / 2026-09-17T20:24:07.
FWWETH vs RDK — normalized performance, 2026-09-08 to 2026-09-17T20:24:07
| FWWETH | RDK | |
|---|---|---|
| Price | $2.54K | $2.07K |
| Market cap | — | — |
| 24h volume | $5.30M | $2.89B |
| Liquidity | $99.94M | $1.74B |
| FDV | — | — |
| Holders | — | — |
| Age (days) | 511 | 1 |
| Safety grade | B | B |
Where they differ
- RDK measures ~17× the liquidity of FWWETH
- RDK measures ~545× the 24h volume of FWWETH
What the data says
FWWETH
FWWETH is the same wrapped-wrapper pattern applied to Ether — a claim on wrapped ETH, meaning the holder is one contract further from the asset than a WETH holder. The address 0xa250cc729bb3323e7933022a67b52200fe354767 is this deployment; our September 14, 2026 snapshot reads $100 million of tracked pool liquidity.
Honest framing: an extra wrapper only exists because some protocol needed a different claim shape — fee-on-transfer handling, rebasing isolation, vault mechanics — so the useful question is which wrapper contract stands between you and WETH, and whether its custody is verifiable. Nine figures of tracked depth says the wrapper sees real use; it doesn't say whose custody that use flows through.
RDK
Sometimes the read on a token is defined by what is missing, and Rudake is that case. HostDeFi's August 19, 2026 capture of RDK — taken when the token was about one day old — has no holder count, no market capitalization, no mint- or freeze-control assessment, and no identifying history. What it does have is a pair of claims from the listing venue: roughly $1.74 billion in pool liquidity and $2.89 billion in daily volume. When the only two numbers present are the two easiest to fabricate, and every number that is hard to fabricate is absent, the shape of the data is itself the disclosure.
Why those two, specifically? Because screeners and aggregators rank by them. An operator who cycles trades against their own pool manufactures "volume" for the cost of gas; reserve figures arrive via feeds that don't audit what they relay. Holder counts and contract state, by contrast, live on-chain where anyone can check — which is why they are the fields that go missing when the goal is to look large rather than be large.
FAQ
Which is bigger, FWWETH or RDK?
By tracked market cap: FWWETH (Ethereum) measures — and RDK (Base) measures — — dated snapshots, not a live feed.
Which is safer, FWWETH or RDK?
On the contract checks we publish: FWWETH (Ethereum) grades B and RDK (Base) grades B. A grade is a structural check on the contract, not a promise about the asset.
How have FWWETH and RDK performed over the shared window?
Between 2026-09-08 and 2026-09-17T20:24:07, the measured snapshots show FWWETH at +2.93% and RDK at 0.00%.
More comparisons
FWWETH vs RYYFWWETH vs FKBFWWETH vs CRDFWWETH vs CCVRDK vs RYYRDK vs FKBRDK vs CRDRDK vs CCV
The grade column is the one CMC's compare page cannot print — our grade is computed from the contract itself (mint/freeze authority, liquidity, holder concentration). Changes are measured over the shared window stated on the chart, 2026-09-08→2026-09-17T20:24:07; a token with fewer measured points measures a shorter span inside it.
Figures are dated on-chain snapshots, not a live feed. Safety grades are structural checks — not investment advice. Free · no signup · a HostDeFi product.