arbitrum-stylus

Deploy WASM-based Stylus contracts on Arbitrum with Solidity interoperability.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/labsaistudio/AABC-Labs --skill arbitrum-stylus-labsaistudio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arbitrum-stylus
Source: https://github.com/labsaistudio/AABC-Labs/tree/main/backend/agent/skills/catalog/arbitrum-stylus
Command: npx skills add https://github.com/labsaistudio/AABC-Labs --skill arbitrum-stylus-labsaistudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Arbitrum Stylus development enables developers to write smart contracts in Rust, C, and C++, compile to WASM, and deploy them on Arbitrum while sharing state with Solidity for unified tooling and deployment.

Core Features & Use Cases

  • Cross-VM interoperability: ABI export and Solidity interop for on-chain contracts.
  • End-to-end Stylus development workflow: writing, compiling, deploying, testing, and activating Stylus contracts on Arbitrum.
  • Shared storage and tooling benefits: same storage layout allows seamless upgrades and cross-language calls.

Quick Start

Install Rust and cargo-stylus, scaffold a Stylus project, and run cargo stylus check and deploy to Arbitrum.

Frequently Asked Questions about arbitrum-stylus

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy WASM smart contracts on Arbitrum using Rust?▼

To deploy WASM smart contracts on Arbitrum using Rust, you need to install Rust and cargo-stylus, scaffold a Stylus project, and run the cargo stylus check and deploy commands to activate the contract on-chain.

Can Solidity contracts call WASM contracts deployed on Arbitrum?▼

Solidity contracts can call WASM contracts deployed on Arbitrum through cross-VM interoperability. Stylus contracts export an ABI and share the same storage layout, enabling seamless on-chain calls between Solidity and Rust.

What is the Arbitrum Stylus development workflow for compiling contracts?▼

The Arbitrum Stylus development workflow involves writing contracts in Rust, C, or C++, compiling them to WASM using cargo-stylus, testing, and activating the WASM contracts on the Arbitrum network with shared Solidity state.

Do I need cargo-stylus to activate high-compute DeFi contracts on Arbitrum?▼

You need cargo-stylus to compile, deploy, and activate high-compute DeFi contracts on Arbitrum. It scaffolds the project and manages the WASM compilation and activation process for ABI-compatible contracts.

Why use WASM contracts instead of Solidity for dApps on Arbitrum?▼

WASM contracts compiled from Rust or C++ provide high-compute execution capabilities for dApps on Arbitrum while maintaining Solidity interoperability. This allows unified tooling and shared storage without sacrificing performance.

What are the limitations of cross-VM calls between Rust and Solidity contracts?▼

Cross-VM calls between Rust and Solidity contracts require ABI compatibility and shared storage layout synchronization. Developers must ensure the compiled WASM contracts export the correct ABI to maintain interoperability with existing Solidity state.