Arbitrum activates ArbOS 61 Elara with opt-in compliance filters for Orbit L3 chains

Arbitrum's ArbOS 61 Elara upgrade went live at 08:42 UTC on August 21, shipping an opt-in compliance filter module that lets any Orbit L3 chain screen transactions against sanctions lists and jurisdictional rule sets at the sequencer layer. The module is disabled by default; chain operators must explicitly enable it and supply their own policy configuration. The filter runs inside the sequencer before a transaction enters the execution pipeline. If a transaction matches a denied address, jurisdiction tag, or custom predicate, the sequencer drops it and returns a deterministic rejection code. Because the logic lives in the rollup node rather than the EVM, it adds no gas overhead and cannot be bypassed by contract-level tricks. Orbit chains targeting enterprise customers, payments networks, tokenized asset platforms, regulated DeFi venues, can now launch with a compliance layer that satisfies know-your-transaction obligations without forking the Nitro client. The same chain can run unfiltered for retail users on a separate RPC endpoint, keeping the two traffic classes isolated. CoinGecko data shows aRB traded at $0.091 on CoinGecko at 14:00 UTC, up 1.4% in the last 24 hours and 19.8% over the trailing week. Volume printed $104.5 million against a $610 million market cap, ranking the token 92nd by capitalization. The seven-day close series, 0.07, 0.07, 0.07, 0.07, 0.08, 0.08, 0.09, shows a steady stair-step since the governance proposal passed on August 14.

per CoinGecko, circulating supply sits at 6.68 billion ARB against the 10 billion hard cap, leaving roughly one-third of tokens unissued for future incentive programs and DAO treasury operations. Total crypto market cap is $2.49 trillion with 24-hour volume of $128.6 billion, per CoinGecko aggregates. The compliance filter does not touch Arbitrum One or Nova. Those chains remain permissionless. Only Orbit deployments that opt in, and fund the sequencer infrastructure, inherit the screening logic. This keeps the base layer neutral while giving regulated venues a supported path to launch on Arbitrum tech. Governance parameter `compliance.filter.enabled` defaults to false. Operators flip it via a privileged transaction signed by the chain's admin key. Rule sets are stored in a separate JSON manifest that the sequencer loads at startup; updates require a sequencer restart but no protocol upgrade. Watchpoints for the next 30 days: first Orbit chain to publish a live filter manifest, any MEV searcher behavior shifts on filtered vs. unfiltered endpoints, and whether the DAO proposes a standardized rule-set template for common jurisdictions.