Bridge

A full bridge, both directions, running entirely in your browser. Bring BONE in from Ethereum, send BONE or a Shiboshi back out, and finish a withdrawal: the Merkle proof is built here from public RPC, with no proof service in the middle. Leaving takes three steps separated by hours, so a withdrawal can be picked up later from nothing but its transaction hash.

← back to the dashboard

Needed to move funds. Looking up and tracking an exit works without one.

Move funds

From

Shibarium

Bridge out

Ethereum

Plasma

Balance on Shibarium: — BONE · leave a little behind for gas, it is the native token here

Burn now, wait for a checkpoint, start the exit, then finalise about seven days later. Every step after the burn is tracked below.

Connect a wallet to move funds. The exit finder below works without one.

Your exits

Lost a withdrawal? Paste the burn transaction hash, or the wallet that burned

The burn is on chain, so the hash alone rebuilds the whole withdrawal: asset, amount, stage and proof. Nothing needs to have been saved on this device. An address works too and searches that wallet for burns, which takes longer but needs nothing written down. This only reads the chain, so your wallet will not ask you to approve anything: the withdrawal appears above, and signing comes later, at the claim.

Exits can be claimed from here. The proof is built in your browser from public RPC, with no proof service in the middle, and both Merkle roots are checked against Ethereum and Shibarium before a claim button appears. Shiboshi goes out over the PoS bridge in one call. BONE goes out over the older Plasma bridge, which takes the same proof but needs two calls about seven days apart, so start it here and come back to finalise. A burn stays claimable indefinitely, and your wallet simulates before you sign, so an exit that would fail is never broadcast.

Which lanes actually work

BONE ⇄ in / outShiboshi NFT → out onlySHIB — closedLEASH — closedTREAT — closed

Still mapped in the bridge but no movement either direction through the ERC20 predicate in over 200 days, rechecked 2026-09-22. ERC-20 over the PoS bridge is not merely idle: MANAGER_ROLE was revoked from the RootChainManager on the ERC20Predicate after the 2025 bridge exploit, so those deposits cannot execute at all. The ERC721, ERC1155 and Ether predicates still hold it. Turning it back on is Shib's call, so treat this as the current state rather than a permanent one.

Official contracts

Every address below is on the ShibWatch watchlist and verified on chain. If a bridge UI ever asks you to approve something that is not one of these, stop.

Contract	Chain	Address
RootChain (checkpoints)	Ethereum	0xd46042f503b8ec0a166af8c0bfbb0a3c562353f9
DepositManager	Ethereum	0x885fce983b6a01633f764325b8c3c5d31032c995
WithdrawManager	Ethereum	0x5f683665ca87dbc3d1358913da80e3c71c328fb0
ERC20Predicate (escrow)	Ethereum	0x6aca26bfce7675ff71c734bf26c8c0ac4039a4fa
ERC721Predicate (escrow)	Ethereum	0x98c831cfb18852f7deb3e3a970e907475b49730f
BONE (L1)	Ethereum	0x9813037ee2218799597d83D4a5B6F3b6778218d9
Shiboshi (L1)	Ethereum	0x11450058d796b02eb53e65374be59cff65d3fe7f
Native BONE (system)	Shibarium	0x0000000000000000000000000000000000001010