Steps
- Choose both assets
Either side can be a native asset on a different chain, for example BTC into ETH.
- Enter an amount
The quote accounts for pool depth on both sides and states an expected confirmation time.
- Wait for source confirmation
Cross-chain needs enough blocks on the source chain before the target transfer is issued. Expect 10–20 minutes.
- Verify the destination address
A cross-chain transfer cannot be recalled. Check the address character by character.
- Track the stages
Follow the record through inbound, swap and outbound rather than assuming it is done.
Terms
- Cross-chain pool
- One pool per asset per chain. Swaps settle through pools, not through a custodian.
- Inbound confirmation
- The source transaction must reach a confirmation depth before funds count as received.
- Outbound
- The transfer on the target chain, signed collectively by the protocol nodes.
Common issues
Why is it slower than a centralised route
It waits for finality on two separate chains, which cannot be skipped.
What happens if it fails midway
Unfinished portions are returned under the protocol rules, after a wait.
Try the flow local math only
Sell0.4218
Buy1,182.40
Rate1 BTC = 0.0241 ETH
Slippage0.50%
NetworkCross-chain
Demo only. Typing converts locally and sends nothing anywhere.