WIRE on BLOCKCLAIMED

Guides / Architecture

How bridgeless deposits and deposit roots work

The escrow plus hash-chain design that replaces third-party bridge validator sets.

Bridges fail in one specific way: a pool of locked assets sits behind a validator set that is smaller and softer than the chains it connects. Compromise the validator set and the pool is gone. Wire's deposit design removes that target by never pooling assets behind a bridge validator set in the first place.

Bridgeless deposits The asset never crosses a bridge. A proof of the deposit does. STEP 1 · NATIVE CHAIN Deposit into escrow ETH locks in the escrow contract on Ethereum. It stays there. STEP 2 · DEPOSIT ROOT Hash-chained proof Each deposit extends a hash chain. The root commits to every deposit. STEP 3 · ON WIRE Shadowed balance A spendable representation backed one to one by the escrow deposit. The deposit root hash chain root n-1 = H(root n-2, dep) root n = H(root n-1, dep) root n+1 = H(root n, dep) Tampering with any past deposit breaks every root after it, so the chain of proofs is verifiable end to end. Withdraw anywhere: burn the shadowed balance on Wire and release the native asset from escrow on the destination chain. BLOCKCLAIMED

Step by step

1. The deposit stays home

To bring ETH into the system you deposit it into an escrow contract on Ethereum itself. The ETH does not move to a custodian or a multisig on another chain. It sits in a contract whose rules are visible on Ethereum, secured by Ethereum.

2. The deposit root proves it

Each deposit extends a hash chain: the new root is a hash of the previous root plus the new deposit's data. The latest root therefore commits to the entire deposit history. Rewriting any past deposit would change every subsequent root, which makes the proof chain tamper-evident. Wire consumes these roots to credit balances; it does not need to trust an oracle's opinion about what happened on Ethereum, it verifies the chain of hashes.

3. The shadowed balance spends on Wire

Against a proven deposit, Wire credits a shadowed balance: a representation backed one to one by the escrowed asset. Shadowed balances are what trade on Wire. A swap between two of them settles in one atomic transaction - both sides move or neither does. There is no pending state where one leg has executed and the other might not.

4. Withdraw anywhere

Burning a shadowed balance releases the corresponding native asset from escrow. Because every supported chain runs the same escrow pattern, the exit chain does not have to be the entry chain: deposit on one chain, trade on Wire, withdraw on another.

The honest trade-offs

  • The escrow contract on each native chain is still code and code can have bugs. The claim is not "no contract risk"; it is "no third-party bridge validator set holding pooled assets". The security of each escrow rests on the chain it lives on.
  • Deposit recognition is bounded by how long the native chain takes to settle. A deposit on a slow chain takes as long as that chain takes; Wire cannot make Ethereum settle faster.
All flows described here run on the Wire V2 testnet today with testnet assets. Testnet deposits carry no value. For anything token-related, Wire's official channels are the only source that counts.

See it from the user side: the InstaSwap guide trades two shadowed balances and reads the atomic receipt.