The Arbitrum Foundation named Offchain Labs the first member of its Developer Guild on October 23, recognizing the company's role as the Arbitrum protocol's primary architect and maintainer. The announcement landed the same day Offchain posted a constitutional proposal to restart Stylus contract activations under a Foundation-controlled signing key. Both measures hand the Foundation new levers: one over how the protocol's core developers get paid, the other over how new Stylus code can go live.

How the Guild Is Funded

The Developer Guild was introduced in January 2024 alongside the Arbitrum Expansion Program, which allows projects to launch their own Arbitrum chains. As the Guild's sole member for now, Offchain will receive the funds the Guild has already collected plus 100% of its revenue for as long as it remains the only participant. That gives the protocol's primary developer a direct stake in the revenue generated by every chain that launches through the program. The Foundation describes the Guild's funding as "relatively nascent" and has not disclosed the balance.

Under the Guild specification, chains launched through the program contribute 10% of their net protocol revenue to the ecosystem: eight percentage points go to the DAO treasury and two points to the Guild. A chain with $1 million in qualifying revenue would therefore send $80,000 to the treasury and $20,000 to the Guild. More than 30 chains already contribute, according to the Foundation.

The Foundation expects the arrangement to push Offchain to concentrate more of its work on growing the DAO's revenue, now that it shares in those cash flows. It also anticipates the Guild becoming one of Offchain's funding sources, reducing the amount the company asks from the DAO in the future.

Membership Criteria and Foundation Control

Guild membership is by invitation and subject to several conditions. A member's business model must rely substantially on Arbitrum, its core components must have been in production for 12 to 18 months, and its code must sit in public repositories under approved licenses. Members must also pass identity checks, sign an agreement with the Foundation, and publish yearly updates.

The specification gives the Foundation authority to approve members, decide each one's share of the funding, and suspend or remove them at its sole discretion. Trivial activity such as typo fixes or dependency bumps does not count as meaningful work, and member names and allocations are to be published periodically on the governance forum. Notably, every example of qualifying work cited in the document is an Offchain Labs repository, from the Nitro node software to the cargo-stylus toolchain.

A Foundation Key for Stylus Activations

Stylus lets developers write Arbitrum contracts in languages such as Rust that compile to WebAssembly. On October 2, the Security Council paused new Stylus activations on Arbitrum One and Nova, citing a growing number of AI-assisted attacks using hand-crafted WebAssembly programs that skip the Stylus toolchain and can degrade chain performance. Known bugs affect chain availability, the Council said, but no attack allowing the theft of user funds has been found.

Under Offchain's proposal, a developer would submit source code to an auditor from the Arbitrum Security Program. The auditor would rebuild the contract with cargo-stylus—the same toolchain named in the Guild specification—confirm that it matches the deployed code and contains no hand-crafted WebAssembly, and post a pass or fail result on the forum. After a pass, a Foundation-controlled multisig would issue a signature, and the developer would activate the contract through a new activation contract. The audit does not review a contract's business logic, and the Foundation would rely on the auditor's result without making its own assessment. The rebuild-and-compare step is aimed at the same vector the Security Council flagged on October 2: hand-crafted WebAssembly assembled outside the standard toolchain.

For most builders, the change is narrower than the pause suggests:

• Unchanged: Solidity contracts deploy and run as normal. Active Stylus contracts stay callable and renewable. ArbOS 61 renewed all active contracts on Arbitrum One, so none expires before August 20, 2027.
• Through the new gate: New Stylus code, including new versions of existing apps, and the reactivation of expired contracts or contracts affected by a Stylus version change. The gate applies to Arbitrum One only; Nova, which is being scaled back, is excluded.

The proposal itself lists several trade-offs. The signing right has no automatic expiry, although the DAO can change or revoke it. Requests would be handled on a reasonable-efforts basis with no fixed turnaround. A compromised signer could approve harmful code, and the proposal adds no way to deactivate a contract.

The proposal goes next to a Snapshot temperature check. Trail of Bits will audit the activation contract, and the report, source code, and multisig configuration are due before the on-chain vote. A vote against would not lift the pause, and the proposal asks the DAO for no new funding.

Where That Leaves ARB Holders

The Guild pays its members, and the 8% share flows to the DAO treasury. Neither arrangement pays ARB holders directly. The token's documented role is governance, which in this context means voting on the Stylus proposal and on any later change to the signing right, while Guild membership decisions rest with the Foundation. As an earlier Coindoo analysis of why ecosystem revenue does not automatically become ARB-holder income explained, a bigger funding pool does not give holders a claim on it.

What to watch:

• The Snapshot result on the Stylus proposal
• The Trail of Bits report and the published multisig signers
• The first published Guild allocation and the size of the pool
• A second Guild member, and how much of the revenue Offchain keeps

This article is provided for informational purposes only and does not constitute financial or investment advice. Governance proposals can change before approval and implementation.