Arbitrum DAO proposes gated Stylus activation requiring security audit
The Arbitrum DAO has published a constitutional proposal to restart Stylus contract activations on Arbitrum One, paused by the Security Council on October 2, 2026, by requiring each new contract to pass a limited security audit before the Arbitrum Foundation can sign it for activation. The mechanism preserves the DAO’s power to revoke the delegation at any time and does not affect existing active Stylus contracts or their renewal.
- Security Council paused Stylus activations Oct. 2 over AI-assisted attack vector risks to network stability.
- New contracts must pass limited audit by Arbitrum Security Program auditor before Foundation signature.
- Foundation gains signing authority but cannot deactivate contracts; DAO retains override via governance vote.
The Constitutional AIP delegates to the Arbitrum Foundation the authority to issue activation signatures for new Stylus smart contracts, code written in languages like Rust and compiled to WebAssembly, that have cleared a focused security review. Stylus lets developers build non-EVM applications on Arbitrum One and chain owners customize protocol-level contracts; the pause left this development path blocked. The proposal explicitly states that “all existing and activated Stylus smart contracts are not impacted” and that users can continue to renew them through the existing keepalive mechanism without interruption.
Limited scope: Protocol safety, not business logic
The audit required by the proposal is not a full smart contract security review. According to the document, it “assesses whether a Stylus contract could harm the Arbitrum protocol” and will confirm at minimum that the deployed bytecode matches code compiled from the submitted source with the standard Stylus toolchain, a check designed to catch hand-crafted or malicious WebAssembly.
The Arbitrum Foundation does not perform the audit itself; it relies on a third-party firm from the Arbitrum Security Program to post the pass-or-fail result on the governance forum, then issues an activation signature based solely on that posted result.
The Foundation “does not conduct or verify the business logic of the audit and shall rely on the security auditor’s posted result,” the proposal states. This means auditors will not review whether a contract’s economic mechanisms, token logic or user-facing features work as intended. The audit covers chain-stability risk, not user-fund risk.
Activation workflow and developer friction
Developers submit source code and build configuration to [email protected]. A security auditor then rebuilds the contract locally to verify the deployed code matches, posts the result publicly, and if it passes, the Foundation provides an activation signature. The developer then calls the Stylus Activation Contract with that signature to activate the code onchain.
Turnaround is “reasonable efforts” rather than a fixed schedule, meaning delays are possible if audit capacity or submission volume spikes.
The proposal does not specify audit costs, timelines or appeal procedures if an auditor rejects a submission. Developers cannot activate new code or updated versions without a fresh audit and signature, creating a dependency on Foundation availability that did not exist before the pause.
The document notes this as a “Activation dependency” risk: “Audit or signing delays, refusals, or loss of access to the signer could delay launches and updates.”
Governance safeguards and open questions
The DAO retains sole administrative authority over the Stylus Activation Contract and can change or revoke the Foundation’s signing right at any time via a new constitutional vote. The proposal does not grant the Foundation power to deactivate contracts after they are live.
However, the document leaves several details to be disclosed later: the multisig address and signer configuration, the final contract source code, deployment addresses, and the Stylus Activation Contract Terms of Use.
The DAO can change or revoke the delegation through governance.
Constitutional AIP: Stylus Activation Contract
The proposal also does not add protocol-level deactivation controls; a later ArbOS proposal is planned for those. And it explicitly states that if the DAO votes against this proposal, the Security Council’s parameter change that enforced the pause “would not itself [be] reverse[d],” meaning rejection would not automatically lift the freeze, a separate governance action would be required.
Implementation timeline and what changes in practice
The process moves through a temperature check on Snapshot, followed by a third-party security audit of the Stylus Activation Contract itself by Trail of Bits, publication of audit results and source code, and then an onchain constitutional vote. Activations cannot resume until governance execution and operational readiness.
The proposal uses capabilities already available in ArbOS 61 and does not require a protocol upgrade.
Solidity EVM contracts remain unaffected. Arbitrum Nova, which is minimized, is out of scope; Arbitrum Sepolia testnet will follow the same process. The change applies only to Arbitrum One for now.
The CCS read. This model trades speed for gatekeeping. Developers lose the ability to activate Stylus contracts unilaterally but gain assurance that deployed code has been checked for network-destabilizing bugs. The audit gate is narrow enough to avoid delay-critical reviews of business logic, but it still creates a new dependency on Foundation operational capacity and discretion. The real question is audit throughput: if the Arbitrum Security Program auditors become a bottleneck, the pause could become a persistent choke point on Stylus adoption, defeating the purpose of reopening the pathway.
The next event is the temperature check on Snapshot, timing not yet announced. Before the onchain vote, the Arbitrum Foundation must publish the Stylus Activation Contract source code, deployment addresses, multisig configuration, and the Trail of Bits audit report. The DAO will vote on whether to delegate signing authority; rejection does not automatically lift the Security Council’s October 2 pause.