HostSUSHI vs RDK — price, size and safety, side by side
SUSHI (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.
SUSHI vs RDK — normalized performance, 2026-09-06 to 2026-09-17T20:24:07
| SUSHI | RDK | |
|---|---|---|
| Price | $0.2465 | $2.07K |
| Market cap | — | — |
| 24h volume | $753.42K | $2.89B |
| Liquidity | $1.09M | $1.74B |
| FDV | — | — |
| Holders | — | — |
| Age (days) | 1,042 | 1 |
| Safety grade | B | B |
Where they differ
- RDK measures ~1,603× the liquidity of SUSHI
- RDK measures ~3,831× the 24h volume of SUSHI
What the data says
SUSHI
SUSHI is SushiSwap's token — the exchange that famously vampire-attacked Uniswap's liquidity in 2020 and has run as a multichain DEX brand ever since. The contract 0x6b3595068778dd592e39a122f4f5a5cf09c90fe2 is the canonical mainnet deployment; our September 6, 2026 read shows $1.1 million of tracked pool liquidity at a $0.25 handle.
The honest read: SUSHI is a legacy-major trading a long way below its peak — the protocol still ships (aggregator routing, the v4 work, a broad chain footprint), and xSUSHI staking still routes a share of venue fees, but the token's valuation is a bet that a crowded DEX market leaves room for a fifth-generation contender. The brand is the asset and the ceiling.
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, SUSHI or RDK?
By tracked market cap: SUSHI (Ethereum) measures — and RDK (Base) measures — — dated snapshots, not a live feed.
Which is safer, SUSHI or RDK?
On the contract checks we publish: SUSHI (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 SUSHI and RDK performed over the shared window?
Between 2026-09-06 and 2026-09-17T20:24:07, the measured snapshots show SUSHI at 0.00% and RDK at 0.00%.
More comparisons
SUSHI vs RYYSUSHI vs FKBSUSHI vs CRDSUSHI 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-06→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.