op-deployer alpha.2 wires in Karst fork activation. Not production, not yet.
Optimism's deployment tooling just absorbed Karst hard fork logic, DA config knobs, and op-validator v6 support. The alpha tag is load-bearing.
CryptoVibe Desk · optimism · op-stack · superchain
- →Optimism released op-deployer v0.7.0-alpha.2, per the GitHub release, adding Karst hard fork activation, op-validator v6.0.0 support, and on-chain DA footprint configuration via SystemConfig.
- →The release consolidates Superchain fork and upgrade machinery into op-deployer, but the alpha designation keeps this staging-ready tooling, not a confirmed Karst network activation on any live chain.
- →Watch for a stable op-deployer v0.7.0 without the alpha tag before Q3, which is the first clear signal that Karst is production-cleared for live Superchain deployments.
- op-deployer → The CLI tool Optimism uses to deploy and configure new chains on the Superchain, handling contract addresses, fork activation parameters, and upgrade logic.
- Karst hard fork → A scheduled protocol upgrade to the OP Stack that requires all chain nodes to update their software; the name follows Optimism's geological naming convention for releases.
- SystemConfig → An on-chain smart contract that stores per-chain configuration parameters, letting governance or automation read and update settings without redeploying the chain.
- op-validator → A tool that checks whether a deployed OP Stack chain's configuration matches the expected canonical values for a given release version.
op-deployer is Optimism's deployment and configuration tool for spinning up Superchain chains. Version v0.7.0-alpha.2, per the GitHub release, adds Karst hard fork activation logic, wires in op-validator v6.0.0 support, makes DA footprint configurable via SystemConfig, and removes both OptimismPortalInterop references and the older upgrade-controller and OPCMv1 migration code. That is a meaningful amount of surface area for a single alpha release.
The alpha label is not a formality. The preceding v0.7.0-alpha.1 release was explicit: development release, not intended for production environments, no binaries attached. Alpha.2 is the first release in this cycle with actual binaries, but the pre-release designation is still in place. This is tooling you can test in staging, not tooling you should run against a live Superchain chain. Karst is not confirmed live on OP Mainnet or any production chain.
The DA configurability change is the most architecturally interesting addition. SystemConfig already stores per-chain fee parameters and gas limits on-chain, making them readable and updatable by governance or automation without a redeployment. Extending it to DA footprint follows the same pattern: pull a hardcoded deploy-time parameter up into on-chain config. Fewer off-chain state assumptions, cleaner separation between deployment-time decisions and runtime-adjustable ones.
Deleting OPCMv1 migration code is not a footnote. It closes the backward-compatibility path for chains still running against the older upgrade mechanism. That may be zero live chains at this point, but the absence of a migration guide in the release notes is exactly the kind of gap that surprises operators after a stable release ships. Removing OptimismPortalInterop references from the deployer similarly signals that whatever interoperability surface those touched is either rerouted elsewhere or explicitly out of scope for this tool going forward.
The tradeoff is a simpler, more opinionated tool with a narrower migration window. Whether that is the right call depends on how many Superchain operators are still behind on upgrade paths.
Optimism is handing Superchain operators a silent breaking change. OPCMv1 migration code is deleted, the alpha.2 release notes include no migration guide, and the absence of a deprecation deadline means operators who have not tracked the alpha cycle will not know what they are losing until stable ships.
A stable op-deployer v0.7.0 release without the alpha designation appearing on the Optimism GitHub releases page before Q3, which is the first real indicator that Karst is cleared for production Superchain deployments.
Primary links and supporting reads used by the desk for this story.
Forward this.
