Orbs has activated its V5 upgrade on Ethereum and Arbitrum, rolling out a Layer 3 hybrid architecture that pushes complex DeFi execution logic off-chain while anchoring verification on both networks. The upgrade, announced Thursday, introduces Committee Sync — a mechanism that propagates committee state across EVM chains using Guardian signatures, eliminating the need for separate verification contracts on every network.
How V5 changes execution
V5 splits the work. Execution nodes off-chain generate signed actions, the Guardian network verifies them, and Committee Sync shoots the verified state to destination chains. No user funds move during that sync, which removes custodial risk. Orbs says the setup targets automation tools — dTWAP, dLIMIT, Liquidity Hub, Perpetual Hub, dSLTP, and the newly branded Orbs Agentic.
Since V4, the protocol has processed over $14 billion in trading volume across more than 30 DEX integrations on over 10 blockchain networks. It's generated over $3.2 million in protocol revenue in that span.
What Committee Sync actually does
Committee Sync is the backbone of V5's cross-chain play. Instead of each chain running its own set of verification contracts — which eats gas and adds deployment overhead — the system uses Guardian signatures to broadcast committee state directly. The result: one set of logic, many chains. Orbs argues this makes expansion faster and cheaper.
The architecture also keeps user funds stationary. Synchronization only transfers state signatures, not tokens. That's a deliberate design choice to avoid bridge-style risk.
Where it launches and where it's headed
V5 goes live on Ethereum and Arbitrum first. Orbs has a laundry list of planned expansions: Base, Polygon, BNB Chain, Avalanche, Linea, Sonic, Berachain, and Monad. No timeline on those yet, but the protocol's integration pipeline suggests a steady rollout through the rest of 2026.
The upgrade arrives as Orbs pushes deeper into DeFi automation — a space that's drawn increasing attention from both retail and institutional users looking to reduce manual drift. Whether V5's multi-chain sync model gains traction will depend on how quickly the planned integrations land and whether developers actually adopt the new tooling.
