OP Labs
@OPLabsPBC
Followers
39K
Following
156
Media
31
Statuses
700
Scaling ethereum's technology & values with @Optimism.
Joined April 2022
Proud to support @boundless_xyz and their initiative to power the next wave of verifiable applications with ZK technology.
.@Optimism is a key supporter in helping Boundless power The Signal, an open-source ZK consensus client. Together, we are unlocking trustless ZK interoperability across Ethereum.
38
16
108
OP Stack core developers are working together to bring more blobs to Ethereum. Read more via @buildonbase 👇.
Fusaka is coming to Ethereum and bringing more blobs for @base users with it. Time for a technical deep dive 🧵. We'll go over why this work is important and what Base has been doing to accelerate Fusaka’s timeline in collaboration with @OPLabsPBC, @testinprod_io, and @soneium
0
6
17
Dive into how engineers at OP Labs are approaching interop security 👇.
It is often difficult to know if you have done enough security work for a project to be safe, or even if you have secured the right angles. In my first article for OP Labs, I describe how we answered those questions for our interop release, critical for our roadmap. 🧵
0
1
13
Immediate actions were taken and all funds are safe. The issue only affects OP Mainnet node operators running op-reth, who should update to at least op-reth version v1.4.7:
github.com
Summary CautionThis release contains a critical bug fix for the chain split event on OP Mainnet: OP Labs Incident Post Mortem. Besides, this release contains following changes since v1.4.3: RPC A...
2
0
11
The mismatch resulted in inconsistent gas accounting on OP Mainnet, causing a chain split between op-geth and op-reth.
1
0
12
Today OP Labs completed a post mortem on a mismatch in the gas refund logic of EIP-7702’s implementation between the geth and reth Ethereum client implementations.
4
20
131
The big picture:. This is how the Superchain scales Ethereum to meet global demand: by making it faster, cheaper, and more usable for everyone. Read the full breakdown here:
blog.oplabs.co
We recently ran PeerDAS through its paces on a modified peerdas-devnet-7 testnet (big thanks to EthPandaOps for leading the spec work!). This devnet was run by Sunnyside Labs, a core development team...
1
0
12
What’s next:. We’re close to hitting our initial target of 48–50 blobs per block. Now it’s time to tune performance, strengthen resilience, and make PeerDAS production-ready.
1
0
11
Why it matters:. Every improvement in blob throughput means:. - Lower gas fees.- Faster bridges.- Smoother app performance. This work directly improves the user experience across all OP Chains.
1
0
10
What broke (and why that’s good):. After 50 blobs, we saw expected signs of strain:. - Import delays.- Missed attestations.- A few supernodes falling behind. This is exactly what we needed to find so we can strengthen it before mainnet.
1
0
9
What we tested:. - 60 nodes (33 supernodes, 27 full nodes).- Continuous blob spam to simulate real load.- No resets or shortcuts. We hit ~50 blobs per block across a diverse set of execution and consensus clients which is a huge milestone for real-world scalability.
1
0
9
What is PeerDAS, and why does it matter?. Every transaction generates data. PeerDAS helps OP Chains store that data more efficiently. This unlocks cheaper, more reliable infrastructure for the entire Superchain.
1
0
9
We just ran our biggest PeerDAS test yet: and it reached 50 blobs per block. This is a major step toward faster apps, lower costs, and a more scalable experience for everyone. (h/t @testinprod_io for leading this effort).
1
3
18
Cheaper fees and next-level scalability will be coming to the Superchain. Here is what we are doing to get there ↓
10
10
121
RT @vex_0x: Agree. With the OP Stack's upcoming interop feature, cross-L2 message validity is an in-protocol concern, with enforcement in t….
hackmd.io
Special thanks to for feedback and review.
0
5
0
Today’s test of the Superchain incident response feature was successful. Withdrawals are fully operational again.
Reminder: Today at 14:30 UTC, we will be testing improved Superchain incident response features. For this exercise, we will pause mainnet withdrawals for Superchain networks for ~20 minutes. During this time, withdrawals will be halted. This will not impact any L1-to-L2.
2
0
27
Reminder: Starting now, we will be testing improved Superchain incident response features. For this exercise, we will pause mainnet withdrawals for Superchain networks for ~20 minutes. During this time, withdrawals will be halted. This will not impact any L1-to-L2 deposit.
Reminder: Today at 14:30 UTC, we will be testing improved Superchain incident response features. For this exercise, we will pause mainnet withdrawals for Superchain networks for ~20 minutes. During this time, withdrawals will be halted. This will not impact any L1-to-L2.
0
0
5
Reminder: Today at 14:30 UTC, we will be testing improved Superchain incident response features. For this exercise, we will pause mainnet withdrawals for Superchain networks for ~20 minutes. During this time, withdrawals will be halted. This will not impact any L1-to-L2.
0
4
41
Read the first post here:. And stay tuned. This series will go deep. If you care about Ethereum scaling, and are curious about the Superchain’s future, you’ll want to follow along.
blog.oplabs.co
This post kicks off a multi-part series on PeerDAS. Over the coming weeks we’ll publish performance deep dives for every major consensus layer /execution layer (el/cl) client pair, surfacing how each...
0
0
6