Bridging Tokens

Sovereign bridges operate using an asynchronous model, enabling seamless communication and interaction between sovereign chains and the main chain. This innovative approach enhances interoperability and facilitates swift and secure transactions across the entire network, ensuring a seamless user experience and unlocking new possibilities for users and developers alike. With bridging between sovereign chains taking only 2 rounds, equivalent to a mere 6-12 seconds.

Bridge from MultiversX to CyberNetwork

• User deposits token in safe contract which he wants to bridge

• Validators in CyberNetwork follow the mainchain headers and will push to CyberNetwork the header, the bridge txs and the proof for it.

• Leaders include proofs of execution from mainchain, right now in terms of adding mainchain header hashes in CyberNetwork header, validators verify it and sign CyberNetwork block only if all steps are correct. The notifier/proof system provides an abstracted interface through which CNET nodes can verify and validate the authenticity of data.

• Incoming Txs are processed by Incoming Txs processor after verifying the proofs. User receives tokens on CyberNetwork.

Bridge from CyberNetwork to MultiversX

• User sends token to bridgeSC on CyberNetwork

• The validators create a proof on CyberNetwork, for a batch of transfers, that will be sent to the mainchain bridgeSC.

• Validators add this information to the sovereignChainBlockBody. Otherwise the block is not signed.

• Leader will push the created txData to the mainchain

• BridgeSC on the mainchain verifies the proof and executes the transfers.

• CyberNetwork validators will notarize the event of finishing transfer on the following sovereign block. By receiving the attestation logEvent directly from the mainchain.