OP Stack

The cross-chain transfer of value, such as ETH from Ethereum(L1) to an OP Stack chains like OP Mainnet(L2), is facilitated by validating bridges, which bear significant requirements + processes to ensure security.

What if these bridges were leaner and more secure? 🧵

1/n

The cross-chain transfer of value, such as ETH from Ethereum(L1) to an OP Stack chains like OP Mainnet(L2), is facilitated by validating bridges, which bear significant requirements + processes to ensure security.

What if these bridges were leaner and more secure? 🧵

1/n

https://warpcast.com/emmanuel/0xabc70ecd

prev. EY-Parthenon | JPMorganChase&Co ||
































Probably doing stuff and things at fastlane.xyz to accelerate the EVM with Monad 🟣

Today, validating bridges for OP Stack chains involve a few dependencies:

- The necessity to create wrapped versions of Ether on L2.
- The requirement for bridge orchestrators to custody L1 value while it is being bridged, via bridge contracts.
- High dependency on the bridge contracts to enter/exit systems

2/n

This bridging system ideally leverages certain basic cryptographic primitives, such as public key cryptography and zero-knowledge cryptography.

Particularly, this should allow end-users to independently move their funds between L1-L2 systems with only the data published and consensus work on the L1.

5/n

I'd like to propose a bridging system for the OP Stack that does NOT require:
- bridge contracts to custody L1 user funds
- the wrapping of ETH in order to utilise on the L2

While still being able to deeply inherit security from the Ethereum core protocol, especially its Consensus and Ledger rules.

4/n

These result in complex bridge designs, laden with numerous third-party processes.

Plus, they don't harness the full security potential of the Ethereum core protocol, relying instead on app-level mechanisms such as fault proofs.(Note:This isn't a knock on fault proofs; they're still valuable for various purposes)

3/n