The Ledger
Arbitrum Proposes Audited Route to Resume Stylus Activations
An ArbitrumDAO proposal would let new Stylus contracts activate on Arbitrum One after a limited security audit and Foundation approval. New activations would remain paused until governance approves and implements the plan.

Arbitrum’s proposed route back to new Stylus activations would reopen access for developers, but only after an independent audit and an approval signature from an Arbitrum Foundation multisig. The tradeoff is explicit: the DAO would retain authority to revoke the delegation, while developers would depend on auditors and the Foundation for each new activation, with no promised turnaround time.
A conditional route past the pause
The constitutional proposal, posted to the ArbitrumDAO forum on October 23, would apply to Arbitrum One. It follows the Security Council’s October 2 pause on new Stylus activations on Arbitrum One and Nova. The proposal does not itself lift that pause: new activations would remain blocked until the governance process is complete and the new mechanism is operational.
Under the plan, developers could still deploy Stylus code, but deployed code would not become callable until it passed the activation process. An auditor participating in the Arbitrum Security Program would review whether the code could harm the protocol and rebuild it with the standard Stylus toolchain, checking that the resulting bytecode matches the deployed codehash. The auditor would post a pass or fail result on the governance forum.
The Foundation signs; developers activate
After a passing result and satisfaction of the proposal’s submission conditions, the Foundation would issue an offchain activation signature. The developer would then submit the activation transaction through a new Stylus Activation Contract. Its proposed onchain sequence verifies authorization, temporarily lowers the activation gas requirement, activates the approved code and restores the restriction before the transaction ends.
The Foundation would rely on the auditor’s posted result; it would not conduct or verify the business-logic review itself. “It is not a comprehensive application audit or an assurance that a contract’s business logic is free of bugs,” the proposal states. The review is intended to reduce exposure to malicious hand-crafted WASM, not to certify that an application is free of defects.
Existing contracts keep running
Already-active Stylus contracts would remain usable by anyone and could continue to be renewed through the existing keepalive mechanism. On Arbitrum One, the proposal says an activation lasts 365 days after the last activation or renewal. Solidity and EVM contract deployment and execution would not change.
The new process would cover new Stylus code, new versions of existing contracts, and reactivation after expiry or a Stylus version change. Arbitrum Sepolia is outside the proposal’s scope but is expected to use the same audit-and-signature process. Nova is also excluded; the proposal describes it as minimized.
DAO control comes with operational dependencies
The Foundation’s signing mandate would continue until the DAO changes or revokes it; it has no automatic expiry. The DAO would be the activation contract’s sole administrator, with authority to change its configuration or reassign the signing right. The proposal does not give the Foundation power to deactivate a contract after activation.
That governance control does not remove the operational risks the proposal identifies. Audit capacity, submission volume, code complexity, a refusal to sign or loss of access to the multisig could delay launches and updates. A compromised signer could also approve harmful code, and the plan adds no deactivation mechanism.
Before an onchain vote, the proposal calls for a Snapshot temperature check, publication of the contract code and deployment details, and a third-party audit of the activation contract by Trail of Bits. The audit report and governance payload are also due before that vote. The proposal says no new ArbitrumDAO funding is required; activations can begin only after the vote, governance execution and operational readiness.
Sources
- Original source ArbitrumDAO Forum forum.arbitrum.foundation
Other pages read
- Arbitrum Developer Documentation developer.arbitrum.io