Alex Breen (effortem)

recast:farcaster://casts/0x927f40eac4e7265f0778816bd9e065b78dc16e5d6de61b2021155dd51ea6e180

• 0 replies
• 0 recasts
• 0 reactions

recast:farcaster://casts/0x4f1b1e3196679d7e54fe409c104448d82f9c03ab7ca7468a0288f35933eb47d3

• 0 replies
• 0 recasts
• 0 reactions

We often hear that chains like @base.base.eth , @zora , and others are “built on the OP Stack” But what is the OP Stack exactly? And why do so many projects choose it? The OP Stack is a modular toolkit for building Layer2s that run on top of @ethereum like templates or engines that chains can use to run their own L2 with ease But why do projects use it and not build their own? Because OP Stack offers: ->Scalability: Ultra-low fees & fast transactions ->Ethereum-grade security: All data posted back to L1 for verification ->Modularity: Swap out execution, data availability, settlement layers as needed ->Ecosystem interoperability: Chains can talk to each other (via the upcoming Superchain) And most importantly: You don’t need to reinvent the wheel. How does it work(in simple terms)? 1. Users send txs→executed instantly on the L2 (e.g., Base) 2. Sequencer bundles & compresses the txs 3. Batch is posted to Ethereum as calldata

• 0 replies
• 0 recasts
• 0 reactions

recast:farcaster://casts/0x88efd06fea39c4561761898b09aee17e5f09c6c86d55a719ee7f69803be507d8

• 0 replies
• 0 recasts
• 0 reactions