We are announcing a major upgrade to xDai bridge operations which will significantly impact the way users interact with the bridge. Changes will be applied starting from the 8th of October.
The main goal of these changes is to provide additional decentralization and control for bridge users – users no longer need to rely on bridge oracles to relay confirmations on the xDai chain side to the Ethereum Mainnet. Instead, users will take responsibility for relaying the confirmations to the Mainnet themselves. This operation is safe since the contract on the Ethereum side will check the relayed message and signatures and it is not possible for a user to provide malicious data. It also provides users with more control, transparency, and the ability to expedite transactions by paying their own gas fees.
We are updating the Bridge UI to allow users to execute the bridge transaction with collected signatures. Other applications (e.g. BurnerWallet) that provide similar functionality will be impacted and will need to make changes related to these updates.
The logic for applications that would like to relay signatures to the Ethereum Mainnet to finalize withdrawals on behalf of the user should be the following:
- Wait while a user transaction initiating the xDai withdrawals is verified and included in a block.
- Wait until the bridge oracles collect the signatures in the bridge contract on the xDai side.
- Gather the message and the signatures from the bridge contract on the xDai chain.
- Send the gathered data to the bridge contract on the Ethereum Mainnet.
Please note that the xDai bridge oracles will still provide the ability to relay collected confirmations automatically for the senders/recipients from the allowance list. If such behavior is important for your application please contact to us by writing a message in this thread.
We hope that suggested changes will allow the xDai bridge to be more transparent and provide better service since users will get more control on the withdrawal operations.