Institutional-Grade Security. Chapter 3: Cross-chain Management
How do you ensure that the same system behaves identically across every chain?
– Governance decisions are made once on mainnet and enforced everywhere
– Deterministic batches form a chain of ordered decisions
– New networks replay full history and reach the same state in minutes
– No per-network deployment scripts, no manual coordination
3 min read
How do you ensure that the same system behaves identically across every chain?
Before the permissionless system, deploying Gearbox to a new network was a fragile and repetitive process. Each expansion required running deployment scripts, verifying contracts, and reapplying the same decisions across chains. As the number of networks grew, so did the coordination overhead — and the risk of inconsistencies.
This is what led to the permissionless architecture.
This is the third chapter in the series. If you missed Chapter 2 ("Onchain Github for bytecode"), you can read it here: Institutional-Grade Security. Chapter 2: Onchain Github for bytecode
At its core are two components that work together. The bytecode repository defines what is allowed to exist in the system — a constrained set of verified components. But defining what is allowed is not enough. The harder problem is making sure that every network ends up in the same state.
This is where the Cross-Chain Multisig (CCM) comes in.
All governance decisions now originate on mainnet. After a DAO vote, they are packaged into deterministic batches, signed once, and committed on-chain. From that point on, the system takes over: the same decisions are replicated across all supported networks.
What makes this work is strict ordering. Every batch references the previous one, forming a continuous chain of decisions. This guarantees that execution happens in exactly the same sequence everywhere.
When a new network is added, nothing needs to be re-created manually. The entire history of decisions is replayed, bringing the new deployment to the same state as the existing ones within minutes.
As a result, deployment is no longer something you do per network. It becomes a coordinated system where decisions are made once on mainnet and then enforced everywhere.
CCM is the layer that makes this possible — synchronizing all Gearbox deployments across chains and turning what used to be operational work into a deterministic process.
Github: https://github.com/Gearbox-protocol/permissionless
Docs: https://docs.gearbox.fi/gearbox-permissionless-doc
Permissionless interface: https://permissionless.gearbox.finance