OP Stack Development for Teams Running or Building on OP Chains
After launch, an OP chain keeps receiving hardforks and L1 contract upgrades, and apps on it inherit its finality and pause rules. Protofire rehearses upgrades with your chain's team and builds the checks apps need. In December 2023 the Optimism Foundation selected Protofire to deliver its Superchain Safe mission.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
What the OP Stack asks of a chain after launch
OP Stack development continues after launch, because each hardfork activates at a set L2 block timestamp. Optimism's docs say that failing to upgrade before that timestamp "causes a chain divergence, and you will need to resync the chain" (Optimism). Protofire rehearses hardforks and L1 contract upgrades with the chain's team. We also build the checks that exchanges, issuers and apps on those chains need.
Who executes an L1 contract upgrade depends on whether Optimism governs the chain. Optimism's notice for Upgrade 21 says that chains governed by the Optimism Security Council "are upgraded through Optimism Governance" (Optimism). The notice gives OP Enterprise chains their own path. All other chains must already be on Upgrade 20, and their teams upgrade the L1 contracts with OPCM.
An exchange or issuer on an OP chain chooses which block tag it trusts before it credits a deposit. Optimism's guidance is to credit low-value incoming transfers on safe blocks and high-value ones on finalized blocks (Optimism). The same page tells exchanges and bridges to stop off-chain actions while withdrawals are paused.
Who decides, signs and builds on an OP Stack chain
Optimism's bodies approve releases and enact L1 upgrades on the chains Optimism governs. Your team holds the roles the stack leaves to the chain.
Hardfork releases
L1 upgrades on governed chains
Admin roles and fee settings
Sequencer, batcher and proposer
Deposit and withdrawal policy
Upgrade transactions and rehearsals
Monitors and runbooks
What OP Stack development covers after launch
Nodes on a supported release before a hardfork
Your nodes run a release that supports the next hardfork before its activation time, so they follow the chain through the fork. Protofire rehearses the hardfork on your testnet, and our node infrastructure service covers the node upgrades.
L1 contract upgrades that your signers can read before they sign
On a chain your team governs, your signers execute each L1 contract upgrade with OPCM and see what each transaction changes. Protofire prepares the upgrade transactions, including a switch to permissionless proofs, and rehearses them on your testnet before your Safe signs.
Pause and balance monitors that follow a contract release
Your alerts keep firing after a release moves the address they watch. Optimism's provisional notice says Upgrade 21 makes the ETHLockbox "the custody and pause identifier for every chain" (Optimism). So after that upgrade, monitors that filter Paused events by the portal address, or watch the portal balance, need a change. Protofire rewrites those monitors through our managed onchain operations service.
A Standard status check before the Optimism Foundation's review
Your team learns which settings would block Standard status before the Optimism Foundation runs its off-chain checks. The Standard Rollup Charter requires a governance-approved release, standard bytecode and a chain that has "authorized the Optimism Security Council to perform upgrades" (Charter). Optimism's docs page on the Charter answers "No" for modified system contracts and for alt-DA chains (Optimism). Protofire compares your chain's release, bytecode, data availability and fee settings with those criteria.
Deposit, pause and withdrawal checks for firms on an OP chain
Your exchange, custody or issuing service knows when a deposit's block is safe or finalized. It also knows when withdrawals are paused. Protofire builds the monitors that report safe and finalized heads, the Guardian pause and each pending withdrawal to your systems.
Upgrade rights on chains Optimism governs and chains your team governs
The Superchain Registry records whether Optimism governs each chain.In its chain list of November 2026, Optimism governs OP Mainnet, Ink, Soneium and Unichain.
L1 ProxyAdmin owner
Chain governed by Optimism: The owner "is a 2-of-2 multisig" of an Optimism Foundation 5/7 multisig and the Security Council multisig (Optimism).
Chain your team governs: Your team holds the ProxyAdmin, SystemConfig owner and Guardian roles, plus the batcher and proposer keys.
Protocol upgrades
Chain governed by Optimism: Anyone can propose an upgrade, the Token House has a one-week veto period, and "The Security Council will enact officially approved Upgrades" (Operating Manual).
Chain your team governs: Your team sets when the chain activates each hardfork. A registered chain that sets superchain_time follows the Superchain-wide activation times.
Fee settings
Chain governed by Optimism: The chain's SystemConfig owner calls the fee setters, and the Charter says ultimate control of that role "should belong to the Chain Governor" (Charter).
Chain your team governs: Your SystemConfig owner calls the fee setters. A non-zero operator fee "makes the chain configuration non-standard" (Optimism).
Fault proofs
Chain governed by Optimism: The registry lists permissionless fault proofs on OP Mainnet, Ink and Unichain, and permissioned proofs on Soneium.
Chain your team governs: Chains deployed with op-deployer start on the permissioned dispute game. Moving to permissionless proofs "is a switch your team schedules after launch" (Optimism).
Finality, pause and interop rules for apps on an OP chain
An app on an OP chain waits longer for each stronger block tag, and the chain's batch posting sets how long safe takes.On OP Mainnet, Optimism's docs give about 2 seconds for latest, a few minutes for safe and about 15 to 30 minutes for finalized (Optimism). Optimism's docs say a firm acting on unsafe (latest) blocks is "fully trusting the chain operator's Sequencer and batcher key for that value" (Optimism). The standard sequencing window is 12 hours, and nodes drop a transaction whose data the batcher does not post within that window.
The Guardian can pause withdrawals, and a pause expires after about three months unless it is extended (Optimism). A pause blocks proving and finalizing withdrawals. Deposits from L1 still arrive, and the L2 keeps producing blocks. Your monitor reads paused() on the OptimismPortal, which reports both the global pause and the chain's own pause.
Once Lagoon interop is active on a chain, an app that sends a message to another chain has to plan for expiry. A message "must be referenced within 7 days (604,800 seconds)" (Optimism). Expiry "does not return any assets", and Optimism's docs say "The application that sent the message must undo the send itself."
OP Stack releases and governance texts in November 2026
- Latest active hardfork
- Karst (Upgrade 19) activated on mainnet on 8 July 2026 and on Sepolia on 17 June 2026, the Superchain-wide default times (Optimism). It added the L2 Contract Manager and a subset of Osaka EIPs on L2.
- L1 contract releases
- Upgrade 20 (op-contracts v8.0.0, super-root dispute games) took effect on 24 September 2026. Optimism's provisional notice set 16 November 2026 as the mainnet target for Upgrade 21 (op-contracts v9.0.0), pending governance approval.
- Next hardfork
- Lagoon adds interop. Optimism's interop notice set 10 December 2026 as the target for OP Sepolia and Unichain Sepolia, pending governance approval. It set 11 January 2027 for OP Mainnet and Unichain, also pending governance approval.
- Governing text
- Operating Manual v2.0.0, committed on 25 June 2026, states that the Token House governs the Optimism Collective.
- Batch posting on Standard chains
- The Standard Rollup Charter expects sequencers to submit batches at least every 6 hours.
Checked 17 November 2026 against Optimism's documentation and upgrade notices, the Operating Manual and the Standard Rollup Charter.
Our record: Safe infrastructure and DEX contract deployments
The Optimism Foundation and the Uniswap contracts repository each recorded Protofire's work on OP chains.Both records are public on GitHub.
Optimism Foundation, Superchain Safe mission
In December 2023 the Optimism Foundation selected Protofire to deliver its Superchain Safe mission, the Safe interface and backend for OP Chains. The Foundation closed the mission as completed in January 2025 (GitHub issue 116). Our Safe multisig deployment service deploys Safe's contracts and interface on a new network for the signers of a chain's admin roles.
Uniswap contracts registry, Ink deployment
Protofire deployed the Uniswap v2 and v3 contracts on Ink in December 2024. In June and July 2026, the deployment registry in the Uniswap contracts repository recorded those contracts as adopted (pull request 153). Our Uniswap v3 deployments case gives the status of each network.
How Protofire takes an OP chain through a release
- Step 1
A list of the releases the chain has not applied
Protofire compares the chain's node releases and op-contracts version with Optimism's hardfork list and upgrade notices. For each gap, the list names the change, who executes it and Optimism's activation time or stated target. - Step 2
A rehearsal on your testnet
Each node release and each L1 upgrade transaction runs on your testnet first. Protofire records which contract addresses, versions and monitors each change affects. - Step 3
Execution by the holder of each role
On a chain your team governs, your Safe signs the OPCM upgrade transactions. On a chain Optimism governs, the Security Council enacts approved upgrades. Your nodes and monitors are updated before activation. - Step 4
Monitors and runbooks in your repository
Protofire commits the monitors, alert rules and runbooks to your repository. A release record lists what each node and contract ran before and after the change.
How OP Stack work with Protofire starts
Your team sends the chain's deploy state, its current op-contracts version and the node layout, with private keys removed.After launch, Protofire holds no sequencer key, upgrade key, signer or admin role. Protofire prepares transactions for the roles your team holds, and your signers sign them.
- Proposal
- In writing, one business day after the discovery call: findings, a plan in phases and the first step we recommend.
- Price
- Fixed per phase when you commission it, against written acceptance criteria. Overruns inside them are ours to absorb, invoices follow delivered milestones, and you can stop at any phase boundary. Anything we operate after launch is priced in the proposal as its own recurring line, with the notice to end it.
- Ownership
- Code we write for you, contracts, the keys and credentials this work creates and the accounts your infrastructure runs in are yours by contract, within the license of any third-party software involved. Keys that a custody platform or a staking provider holds under its own key model stay with it under your contract; every other custody key stays with you or the custodian you appoint. Where the scope places something on servers we rent, it says what moves to you and when. An NDA is available from your first message, and we sign a data processing agreement (DPA) together with it.
- After launch
- Delivery closes with a hypercare window and a defect warranty, with their terms written into the proposal. A service we operate continues under its written scope until that scope ends.
- Access
- Read-only by default. A role that can start requests only if your written scope names one; never a signer, approver, administrator, key holder or recovery role on your contracts, wallets or custody platform. Services we build call each platform on credentials your staff issue and keep in your vault. Anything that approves or moves funds runs in your environment, and a scope under which we operate a service lists every write call it makes. Where the scope has us operate nodes, validators, monitors, explorers or indexers, it names the role and any key we hold on those servers, and in your own cloud account you can remove it.
- Licenses
- Protofire is an engineering firm and holds no financial or crypto-asset license; licensed activity stays with you and your providers.
How we work shows a worked proposal.
Requests outside Protofire's OP Stack work
- You want one firm to run the sequencer, batcher, proposer and challenger and to answer incidents. Protofire does not run these services for a chain. Optimism's launch paths page lists OP Enterprise, its managed offering, under "Have it operated for you".
- Your team is still choosing a rollup stack. Our rollup development service covers the stack choice and the first deployment, and our rollup stacks guide compares the stacks.
- You want Standard status or a stage rating promised. The Charter's onchain criteria and the Optimism Foundation's checks decide Standard status, and L2Beat's framework assigns stages. Protofire builds to the published criteria and cannot promise the result.
- A single institution needs a permissioned ledger. Our enterprise blockchain service covers that choice.
FAQ
What is OP Stack development?
Who can prepare an OP chain for its next hardfork?
Our chain still runs op-geth. What now?
How long does a withdrawal from an OP chain to Ethereum take?
What does Lagoon interop change for an OP chain's nodes?
Get a proposal
Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.
