Arbitrary Message Bridge (AMB)
xDai Bridge
ETH-XDAI AMB
BSC-xDai AMB
RINKEBY-XDAI AMB
Kovan-Sokol AMB
ETH-BSC AMB
ETH-POA AMB
ETH-ETC AMB
Submit confirmations manually
Instructions how to manually submit the oracles' confirmation to the POA Network side
The Arbitrary Message Bridge between the POA Network and the xDai chain requires a request-and-claim scheme to transfer data from the xDai chain. This scheme requires at least two transactions to pass the message from the xDai chain: one transaction to initiate the message transfer and a second to forward collected oracles' confirmations for the message transfer request to the contracts on the POA Network.
Some users and applications may want to use a manual process to gather the oracles confirmations and send them to the AMB contracts on the POA Network side.
This approach is the equivalent of the set of actions performing by the AMB Live Monitoring app after pressing the "Execute" button.
Below is the list of actions that can be executed in the BlockScout, or, if you are familiar with the contract interaction through a Web3 provider, it can be done by importing the contract's ABI to your application.
1. Find a transaction in the BlockScout application which initiated message passing through the AMB bridge and go to the logs generated during the transaction execution. The
encodedData argument emitted with the UserRequestForSignature event will be used in the next steps. 
2. Go to the AMB helper contract and call
getSignatures there with the encoded data from the UserRequestForSignature event. It will produce a blob with signatures.
3. Pass the encoded data and the signatures to the method
safeExecuteSignaturesWithAutoGasLimit of the Arbitrary Message Bridge contract (0xB2218bdEbe8e90f80D04286772B0968ead666942) on the POA Network and press the "Write" button to send the transaction. 
MetaMask will show a high gas estimate for this transaction. In most cases the final gas consumption will be significantly lower.
Last modified 7mo ago
Export as PDF
Copy link