vAssets

A verifiable asset: a real asset locked on its origin chain, usable where you need it, with a published post-quantum proof of every lock. Crossings, assets, fees.

Last updated 2026-09-03 · maintained in the Final Wiki

#What a vAsset is

A vAsset is the representation on one chain of an asset locked on another. The real asset never leaves its origin chain: the settlement contract there holds it locked, and an equal amount of the vAsset is issued on the target chain. Burning the vAsset on the target releases the original on the origin. Both directions settle as soon as the protocol's settlement quorum has observed the operation at finality; there is no seven-day exit.

A vAsset is not a custodial wrapper. It carries the proof that unlocks the asset on its origin chain — the vAsset is the key, not a receipt for one.

#The v is for verifiable

Every settled operation carries a post-quantum zero-knowledge proof, built with a LaBRADOR-based scheme, of the lock behind it: the origin chain, the block the asset was locked in, the address and the amount. The proof's hash is published on the target chain and anchored in the state plane's vAsset record, so anyone holding a vAsset — or looking at one — can check that a real lock backs it, without taking the protocol's word for it.

The proof is verified by the settlement quorum, each member independently, the same way post-quantum signatures are verified today. The target chain checks the published hash against the anchored record; it never runs a lattice verifier itself.
The scheme is lattice-based, in the same post-quantum family as the signatures and key encapsulation the protocol already uses.
A vAsset without a published proof is inert: nothing backs it and no release honours it.

#How a crossing works

Lock on the origin chain. Anyone can lock; the operation names its target chain and a beneficiary (unspecified means the sender, resolved at the source so the destination never interprets a blank).
Observe and admit. The settlement quorum reads the lock at finality and admits it into the settlement record on the state plane, together with the commitment to its proof.
Settle on the target: the vAsset is issued to the beneficiary and the proof's hash is published beside it. The destination is carried by the record and re-derived at the target; altering it derives a different operation and settles nothing.
Return when an operation can never settle on its target: the origin releases it back on the chain it started from.

#Which assets

Assets are allowed by default on any registered chain, minus a published exclusion list: rebasing tokens are excluded outright (their balances break the backing invariant), and stablecoins are excluded because they are served by a dedicated path. The chain set and the asset set are published from the state plane and copied to every chain by proof, so no two chains disagree about either. Asset metadata (symbol, decimals) is committed at registration, never supplied by an operator at settlement time.

#Fees

0.05 % per crossing, with a floor of USD 0.50 each way and no cap. Tier discounts from the particle ladder apply.

#What you can rely on

The asset is locked on the origin chain, in a contract that cannot release without a settled record.
Every vAsset is backed by a published, verifiable proof of its lock; one without a proof is inert.
Every operation is returnable if it will not settle.

#Status

Live on the test environment end to end. On mainnet the settlement contracts hold the current registries; the per-chain asset records are being copied in. Next, scheduled with the Final Chain release, vAssets morph on Final Chain: that is the Liquidity Cloud.