Optimism says OP Stack predeploys have been hard to upgrade because each chain’s L2ProxyAdmin is controlled by L1 multisigs, and some contracts need changes live in the first hardfork block. Its new L2ContractManager flow injects Network Upgrade Transactions at activation, with Karst using a 31-transaction NUT bundle to deploy implementations, upgrade L2ProxyAdmin, and move all 27 maintained predeploys in one L2 block. The point is operational safety: no per-chain multisig signing, no hardcoded implementation bytecode in consensus clients, and less reason to avoid protocol features that touch predeploys.

TLDR by @Benthic

Explore the topic

More on $OP

Comments