Open app

WBTC vs RDK — price, size and safety, side by side

WBTC (Arbitrum) 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.

WBTCB

$75.75K
Wrapped BTC on Arbitrum
Trade WBTC
vs

RDKB

$2.07K
Rudake on Base
Trade RDK

WBTC vs RDK — normalized performance, 2026-09-15 to 2026-09-17T20:24:07

100 — shared start
WBTC +0.31%  ·  RDK 0.00% — both series rebased to 100 at the first measured point in the shared window; not a raw-price chart.
WBTCRDK
Price$75.75K$2.07K
Market cap
24h volume$32.90M$2.89B
Liquidity$35.34M$1.74B
FDV
Holders
Age (days)1,6821
Safety gradeBB

Where they differ

What the data says

WBTC

WBTC on Arbitrum is the same BitGo-custodied claim as its Ethereum parent, deployed at the canonical L2 address 0x2f2a2543b76a4166549f7aab2e75bef0aefc5b0f. The September 16, 2026 snapshot reads $35.3 million of tracked pool liquidity — the standard wrapped-Bitcoin venue for Arbitrum DeFi.

What a chain hop does and doesn't change: the custody question (BitGo, KYC'd merchants, the mint/burn pipeline) is identical to mainnet WBTC — the L2 deployment is a claim on the same reserve. What does change is the routing surface: L2 liquidity concentrates in fewer pools, so depth reads lower while redemption still routes through the same custodial spine.

Full WBTC safety read →

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.

Full RDK safety read →

FAQ

Which is bigger, WBTC or RDK?

By tracked market cap: WBTC (Arbitrum) measures — and RDK (Base) measures — — dated snapshots, not a live feed.

Which is safer, WBTC or RDK?

On the contract checks we publish: WBTC (Arbitrum) grades B and RDK (Base) grades B. A grade is a structural check on the contract, not a promise about the asset.

How have WBTC and RDK performed over the shared window?

Between 2026-09-15 and 2026-09-17T20:24:07, the measured snapshots show WBTC at +0.31% and RDK at 0.00%.

More comparisons

WBTC vs RYYWBTC vs FKBWBTC vs CRDWBTC 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-15→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.