I’m reviving this proposals for the consideration of the assembly.
The bridge works by validators signing the block headers of both fuse + other evm network
The signed blocks are saved only on fuse (so no gas required from validators)
From the block header you can prove that any TX/storage is valid.
That’s it. On top of that everyone can build an innovate with their own smart contract that acts as a bridge.
How does that work?
Anyone that wants to prove to the custom bridge smart contract that he did something on the “other” network submits the signed block + the tx/storage proof
The smart contracts verify that the signed block was actually signed by enough validators and if so verifies the tx/storage proof and executes its custom logic.
That’s basically it. Another thing that needs to be handled is updating the validators, that can be solved by validators also signing the set of current validators.
This bridge has the same security guarantee as the Fuse consensus.
In the future it is possible to add a new op code so the fuse network can actually validate the proof of work consensus of ethereum and have the same security guarantee of ethereum on validating tx/storage proofs on fuse