Deep Tide TechFlow News, February 19 — According to The Block, Coinbase incubated Ethereum Layer 2 network Base announced it is splitting from Optimism’s Superchain ecosystem to shift towards a unified tech stack operated by Base, abandoning external dependencies on OP Stack, Flashbots, and Paradigm. This change aims to reduce coordination overhead for multi-team code maintenance, simplify the system through optimizations based on open-source components like Reth, while maintaining the “Stage 1” rollup state. It is also planned to be temporarily compatible with OP Stack, but future hard forks will require migration to a new Base client. Upcoming hard forks include Base V1 (supporting Fusaka and switching to TEE/ZK proofs), with subsequent versions synchronized with Ethereum Glamsterdam upgrades. The blog emphasizes protocol openness and welcomes alternative implementations.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
Base will detach from the Optimism ecosystem and transition to an independent, unified technology stack.
Deep Tide TechFlow News, February 19 — According to The Block, Coinbase incubated Ethereum Layer 2 network Base announced it is splitting from Optimism’s Superchain ecosystem to shift towards a unified tech stack operated by Base, abandoning external dependencies on OP Stack, Flashbots, and Paradigm. This change aims to reduce coordination overhead for multi-team code maintenance, simplify the system through optimizations based on open-source components like Reth, while maintaining the “Stage 1” rollup state. It is also planned to be temporarily compatible with OP Stack, but future hard forks will require migration to a new Base client. Upcoming hard forks include Base V1 (supporting Fusaka and switching to TEE/ZK proofs), with subsequent versions synchronized with Ethereum Glamsterdam upgrades. The blog emphasizes protocol openness and welcomes alternative implementations.