Deposit DASH
Send DASH from Dash mainnet to your personal deposit address. After the Dash transaction is ChainLocked and proven to the bridge canister, your DashEVM account is credited, minus the mint fee.
Connect your DashEVM wallet
The deposit address is bound to one DashEVM account. Coins are credited to the account you connect here.
Ask the relayers to watch your address
Relayers need to know which Dash address belongs to your account. This page asks them for you. No transaction and no gas are needed. Each relayer works out the address itself, and this page checks it on its own as well.
If an address receives no deposit for 30 days, relayers may stop watching it. Opening this page again registers it again, and a deposit sent in the meantime is then found and credited. Registering on chain keeps it watched for good.
Your Dash deposit address
Deposit progress
Updates every few seconds while this page is open. Each Dash output to your address is tracked separately.
Withdraw to Dash
Burn DASH on DashEVM and receive it at a Dash mainnet address. The bridge waits a safety delay before it signs the payout.
Withdrawal status
History
Deposits and withdrawals of an account, read from the gateway's events on DashEVM.
Deposits
Withdrawals
Bridge status
ICP canister
DashEVM gateway
Limits and fees
Recent canister jobs
Settings
How it works
This bridge moves DASH between Dash mainnet and DashEVM. It is secured by ICP threshold signatures and on-chain light-client proofs:
- A canister on the Internet Computer verifies Dash block headers, ChainLocks and transaction proofs, and DashEVM headers and receipt proofs, itself. Relayers only carry data; they cannot mint or release anything.
- The canister's key is a threshold ECDSA key held by an ICP subnet. It signs mint batches for the DashEVM gateway and Dash payout transactions.
- The DashEVM gateway accepts only signatures of that key.
Deposit
The page asks the relayers to watch your personal deposit address (no gas needed; registering it on chain is an optional alternative), then you send DASH to it. Once the Dash transaction is in a ChainLocked block, a relayer proves it to the canister, the canister puts it into a signed mint batch, and the batch is posted to the gateway. Large deposits can wait an extra delay on the gateway (once governance enables the large deposit queue). Deposits below the minimum are not credited.
Withdraw
Burning sends your coins plus the burn fee to the gateway. The canister waits for the burn to be final on DashEVM, then a release delay (30 minutes, or 24 hours above the large-release threshold), signs and broadcasts the Dash payout, and reports it back. A rolling 24 hour release cap applies; burns beyond it wait in order. If a payout cannot be made, the burn is refunded on DashEVM.
What the bridge does not do
- It is not private. Deposit addresses, burns and payouts are public on both chains and linkable to your DashEVM account.
- The Dash explorer this page polls and the relayers it asks see your IP address together with your deposit address or account.
- It is not fast by design: every step waits for finality, and payouts wait a delay.
- It is experimental and unaudited. Bugs, pauses and long delays are possible.
- During the beta the operators can upgrade and pause the bridge. Treat it as operator trusted until the audit and the hand over of upgrade control.
Deposit address checks
The browser cannot make an update call to the canister (only allowlisted relayers can), so the deposit address comes from query calls. To reduce the trust in any single server, this page:
- asks two ICP boundary hostnames and requires identical answers;
- verifies the replica node signature on each query answer (the agent checks it against subnet keys from a certificate signed by the IC root key);
- verifies the subnet certificate returned with the vault key: it must be signed under the IC root key, be fresh, and certify the hash of the vault key as the canister's certified data;
- recomputes the address in your browser from the canister's vault key;
- derives the gateway attester address from the same vault key and compares it with the attester stored in the DashEVM gateway, so the key is anchored to the contract that mints your coins.
The vault key is certified by the whole subnet, so one replica cannot forge it. The address is also withheld while the bridge cannot credit deposits (frozen, severed, attester disabled, winding down, key not ready). Send only small test amounts.