Withdrawal Authorization Flow
Following a withdrawal from xDai to Dai
- 1.User sends a transaction to the bridge contract on xDai to initiate a withdrawal.
- 2.The requested xDai withdrawal amount is sent to an 0x address, and the
UserRequestForSignaturemethod is called. Example tx: https://blockscout.com/xdai/mainnet/tx/0x8e23cf0ab01476c2df5b71a72603f2c229d3d9a63ad6ca71ce164798f3733826/internal-transactions - 3.The request generates an event on the xDai side.
- 4.Bridge validator nodes catch this event and send confirmation (signatures) to the contract on the xDai side.
- 5.Once enough signatures are collected (currently 3 of 5), one of the bridge validators* sends the signatures and message to Ethereum. *This is not a centralized process, anyone can extract this information and send to Ethereum. If a transaction stalls due to congestion, this transaction can be re-submitted by any user with a higher gas price.
- 6.The bridge contract on Ethereum checks that the signatures are valid. If they are, the requested Dai is unlocked for the user. Note: This final step may be delayed if Ethereum mainnet is congested.
To track the relay we locate the originating transaction, find the corresponding transactions from confirmed validators, then find the transaction with signatures on Ethereum.
- Code that checks the signatures and unblocks funds on Ethereum (starting from
executeSignatures(line 752)) https://etherscan.io/address/0x7e7669bdff02f2ee75b68b91fb81c2b38f9228c2#code - Example transaction that makes this call: https://etherscan.io/tx/0x74efc3302beeaa14fda51e03cfedd03693961db41b1b9b6069c576431f844c91