Skip to content

P3 Stylus 96 KB fragment + WASM multi-value removal (TW-738)#3237

Draft
anegg0 wants to merge 10 commits into
Arbos60from
tw-738-p3-stylus-96-kb-fragment-deployment-wasm-multi-value-removal
Draft

P3 Stylus 96 KB fragment + WASM multi-value removal (TW-738)#3237
anegg0 wants to merge 10 commits into
Arbos60from
tw-738-p3-stylus-96-kb-fragment-deployment-wasm-multi-value-removal

Conversation

@anegg0
Copy link
Copy Markdown
Contributor

@anegg0 anegg0 commented Apr 24, 2026

Description

Tracking branch for ArbOS 60 Stylus changes. Unlike P2/P4/P5 (new-article stubs), this item edits existing Stylus pages, so there's nothing to stub up-front — the branch is open so SME (@srinjoyc ) can push file edits when ready.

Scope (from Notion drafting page):

  1. 96 KB contract size limit — document the fragment-based deployment model raising Stylus contracts from 24 KB to 96 KB (4×). Transparent to developers (`cargo-stylus` auto-bisects WASM); chain owners get a new `MaxWasmFragments` param in `StylusParams`.
  2. WebAssembly multi-value removal — breaking-change notice for contracts that rely on the extension. They cannot activate or re-activate post-upgrade.

Document type

  • Gentle introduction
  • Quickstart
  • How-to
  • Concept
  • FAQ
  • Troubleshooting
  • Reference
  • Third-party content
  • Not applicable

Checklist

  • I have read the CONTRIBUTE.md guidelines
  • My changes follow the style conventions outlined in CONTRIBUTE.md — pending SME content
  • I have used sentence-case for titles and headers — pending SME content
  • I have used descriptive link text (not "here" or "this") — pending SME content
  • I have separated procedural from conceptual content where appropriate — pending SME content
  • I have tested my changes locally — Vercel preview will verify
  • My code follows the existing code style and conventions — pending SME content
  • I have added/updated frontmatter for new documents — N/A (edits-existing)
  • I have checked for broken links — pending SME content
  • I have verified that my changes don't break the build — pending Vercel preview
  • Third-party docs only:
    • Yes
    • Not applicable

Additional Notes

  • DRAFT — tracking branch only, awaiting SME edits.
  • Targets `Arbos60` staging branch, not `master`.
  • Expected file touchpoints (TBD by SME): `cargo-stylus` deployment docs, `StylusParams` reference, Stylus breaking-changes / upgrade notes.

… (ArbOS 60)

Placeholder tracking branch for edits-existing content. Rory Neithinger
will push changes to existing Stylus pages here once scope is defined
(see Notion page for acceptance criteria).
@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 24, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
arbitrum-docs Error Error May 5, 2026 10:44pm

Request Review

Added section on deploying contracts larger than 24 KB, detailing fragmentation process and activation.
Add information about fragmented contracts and their activation costs.
srinjoyc added 2 commits May 5, 2026 15:25
Added information about contract size limits and reactivation requirements for Stylus contracts.
Added note about contract size limits and deployment behavior.
srinjoyc added 2 commits May 5, 2026 15:31
Added detailed information about breaking changes in ArbOS 60, specifically regarding the removal of WASM multi-value support and its implications for Stylus contracts.
Clarified the impact of ArbOS 60 on multi-value contracts and updated instructions for recompilation.
srinjoyc added 2 commits May 5, 2026 15:40
Clarify the breaking change regarding WASM multi-value support in ArbOS 60.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants