XRD ⇄ NEAR Intents statement of accounts no wallet · no keys

Is every wxrd backed by XRD sitting in the vault?

Reading both chains…

Radix mainnet and NEAR, read directly by your browser. Nothing here is cached and nothing is sent anywhere.

The numbers the claim rests on

XRD in the vault

— XRD

the chain's own accounting

wxrd in existence

— wxrd

minted, not yet burned

Burned, awaiting release

— wxrd

owed to holders right now

Most the vault can ever hold

— XRD

owner-set ceiling

Each check, and what it would mean if it failed

Reading…

Owed right now — the release queue

Reading the queue…

The limits, and who holds the keys

Ceiling on the vault—

Ceiling on one release—

Locking paused—

Locks taken so far—

Blueprint—

Radix component — …

Radix package — …

NEAR token — …

NEAR Intents verifier — …

Custodian account — …

What this page does not prove

The custodian can still misdirect a release. It can pay the right amount to the wrong Radix address, and no accounting gate catches that. This is a custodial bridge with a gate, not a trustless one.
It says nothing about the swap desk. Buying wxrd from the operator's desk is a separate, bilateral thing; this page is only about whether the tokens are backed.
"Backed" is not "liquid". The XRD is in one vault on Radix; a holder's ability to redeem depends on the relayer running and on the component's per-release ceiling.
Not financial advice, and not a solicitation. This is a prototype, published so that the arithmetic can be checked rather than believed.

Not read yet.

Read at final finality, which is the honest choice: a balance that is not yet final has not settled. Two reads can straddle a mint, so the numbers above are one snapshot of both chains rather than an atomic view of either.

Check it yourself, without this page. Everything above comes from three public reads:

curl -s -X POST https://mainnet.radixdlt.com/state/entity/details \
  -H 'Content-Type: application/json' \
  -d '{"addresses":["component_rdx1crky4mhm2vknwc5xsmcycdvehy69uvlzmm6tjydkewklfmka6sj2cn"]}'
#   details.state.fields   -> lifetime_locked, released_total, max_locked, max_release, paused
#   fungible_resources     -> the vault's actual XRD, as the chain accounts for it

curl -s -X POST https://free.rpc.fastnear.com -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"query","params":{"request_type":"call_function",
       "finality":"final","account_id":"wxrd.near","method_name":"custody_state","args_base64":"e30="}}'
#   e30= is base64 of {} — and "pending_burns" instead of "custody_state" gives the queue above