upgrade-stylus-contracts

Upgrade Stylus WASM contracts on Arbitrum by deploying implementations behind ERC-1967 proxies and executing UUPS or Beacon pattern upgrades with strict access control and initialization sequencing. This ensures safe contract reactivation and storage compatibility.

UUPS and Beacon proxy patterns work with Stylus contract upgrades. Both OpenZeppelin patterns integrate with Stylus WASM to manage implementation migrations while preserving storage layout and enforcing proxiable UUID validation during contract reactivation.

Yes, you can use OpenZeppelin proxies with Arbitrum Stylus contracts. The integration supports ERC-1967 proxy deployment, allowing Stylus WASM implementations to coexist with EVM proxies and perform auditable upgrades using standard safety checks.

Preserve storage layout when upgrading Stylus implementations by using compatible proxy patterns and following correct initialization sequencing. This approach maintains data integrity across contract migrations and prevents storage collisions during reactivation.

Required safety checks for Stylus proxy upgrades include access control enforcement, proxy context checks, and proxiable UUID validation. These checks ensure only authorized callers perform upgrades and that implementation contracts validate their proxy context correctly.

Use a Beacon proxy for Stylus upgrades when managing multiple proxy instances sharing one implementation, and UUPS for single-contract upgrades with built-in upgrade logic. Both patterns maintain storage compatibility and support safe reactivation on Arbitrum.