Key Highlights:
- The Arbitrum DAO is weighing a new governance proposal to resume Stylus activations on Arbitrum One via an audit-and-signature verification process.
- Activations were halted on October 2 after the Security Council identified risks where custom WebAssembly (WASM) programs could harm chain performance and operational continuity.
- Under the proposed framework, audited code can be deployed using a newly designed Stylus Activation Contract without requiring a full ArbOS network upgrade.
Arbitrum Community Proposes Controlled Path to Re-Enable Stylus Activations
The Arbitrum community is evaluating a new Arbitrum Improvement Proposal (AIP) aimed at ending the freeze on Arbitrum Stylus program deployments. The Security Council paused new activations on Oct. 2 after determining that unverified code posed stability risks to the ecosystem. According to the council’s emergency findings, hand-crafted WebAssembly (WASM) programs could degrade chain performance, and known Stylus bugs primarily threatened the network’s ability to keep operating rather than directly putting user funds at risk.
To safely restore functionality, the new proposal introduces a structured audit-and-signature pipeline. Under the proposal, an Arbitrum Security Program auditor would review submitted code, rebuild it with the standard Stylus toolchain and check that it matches the deployed code. Following the evaluation, the auditor would post a pass or fail result directly on the official governance forum. If the submission earns a passing result and satisfies the proposal’s conditions, the Arbitrum Foundation would issue a cryptographic signature, allowing the developer to finalize deployment through a dedicated Stylus Activation Contract.
Audit Boundaries and the Activation Mechanism
The review protocol is strictly constrained in its technical scope. The limited audit would focus on threats to the Arbitrum network, not the application’s business logic. Furthermore, the Arbitrum Foundation would rely on the auditor’s result rather than perform its own security assessment, maintaining clear boundaries between administrative execution and technical verification.
To execute the activation smoothly, the activation contract would temporarily lower the gas requirement that enforces the freeze, activate approved code and restore the restriction within one transaction. By leveraging existing ArbOS 61 capabilities, the proposal eliminates the operational overhead of coordinating an ArbOS protocol upgrade. Programs deployed prior to the October freeze remain unaffected; already-active contracts would remain callable by anyone, and anyone could renew them through the existing keepalive mechanism. Conversely, new or upgraded code, alongside reactivations prompted by contract expiration or Stylus version updates, would be obligated to clear the audit-and-signature process.
Governance Structure and Next Steps
Administrative control under the proposed model maintains decentralization through DAO oversight. While the Foundation would manage its multisig signers, the DAO would remain the activation contract’s sole administrator and could change or revoke the delegation through a later constitutional vote. The signing mandate would carry no automatic expiration, and the proposal explicitly denies the Foundation the power to deactivate any previously activated contract.
The AIP applies specifically to Arbitrum One and excludes Arbitrum Nova. While Arbitrum Sepolia is formally outside the scope of the document, the testnet is expected to adhere to the same audit-and-signature process. Implementation will proceed through a Snapshot temperature check followed by a binding onchain vote. Key deliverables—including the multisig address, signer configuration, contract source code, governance payload, and a Trail of Bits audit report on the activation contract—must be submitted prior to the onchain ballot. Until governance execution is finalized and operational systems are ready, new contract activations will remain paused.
Why This Matters
Arbitrum Stylus represents a major architectural milestone for Ethereum Layer-2 scaling by enabling developers to deploy smart contracts written in popular programming languages like Rust, C, and C++ alongside standard EVM Solidity contracts. However, introducing WebAssembly runtimes expands the potential attack surface for network liveness and resource consumption. The October 2 pause underscored the challenges of maintaining chain stability while operating advanced multi-VM environments. If approved, this proposal provides an interim compromise: granting developers access to Stylus’s high-efficiency capabilities while shielding network performance through rigorous, independent bytecode validation.
Frequently Asked Questions
Why were Stylus activations originally frozen?
The Arbitrum Security Council instituted an emergency freeze on October 2 after reporting that hand-crafted WASM programs could degrade overall network performance. The council noted that existing bugs in Stylus primarily threatened chain liveness and network operations rather than user capital.
Does this proposal require a hard fork or an ArbOS upgrade?
No. The deployment process utilizes capabilities already present in ArbOS 61. The new Stylus Activation Contract manages the activation gas thresholds within a single transaction, bypassing the need for a chain-wide software upgrade.
Are existing Stylus contracts impacted by the ongoing pause?
No. Smart contracts that were active prior to the freeze remain fully functional and callable by users. They can also continue to be renewed through the existing keepalive mechanism without undergoing the new audit process, provided their code is not modified.
