Skip to main content

config-other-language-support

Arbitrum Stylus represents the mechanism through which Arbitrum chains support programming languages beyond those native to the Ethereum Virtual Machine (EVM), such as Rust. Specifically, Stylus introduces a coequal WebAssembly (WASM)-based virtual machine alongside the EVM, allowing developers to write, compile, and deploy smart contracts in Rust (or other WASM-compatible languages like C and C++) directly on an Arbitrum chain. These WASM contracts are fully interoperable with traditional EVM/Solidity contracts, meaning a Rust program can call a Solidity function and vice versa, without disrupting Ethereum equivalence. Code interoperability opens expansion possibilities of Arbitrum's ecosystem by bridging Web2 and Web3 development paradigms, leveraging Rust's SDK for seamless integration and enabling access to its vast library ecosystem (e.g., crates for cryptography).

Pros of Other Language Support (e.g., Rust) on Arbitrum Chains​

  • Broader Developer Accessibility: Opens the door to millions of Web2 developers proficient in Rust (over 3.5 million) or C/C++ (13 million), reducing the barrier to entry for blockchain development without requiring Solidity expertise and accelerating ecosystem growth.
  • Enhanced Performance and Efficiency: Rust-compiled WASM contracts execute faster with significantly lower gas fees (e.g., 4- 10x cost savings in AMMs, 100-500x cheaper memory), making compute-intensive applications like onchain AI, generative art, high-frequency DeFi, or games feasible on L2 chains.
  • Improved Security and Safety: Rust's inherent features, like memory safety and default-disabled reentrancy in the Stylus SDK, reduce common vulnerabilities (e.g., cheaper detection of reentrancy attacks), leading to more robust contracts compared to Solidity.
  • Full Interoperability and Flexibility: Allows mixing Rust/WASM and Solidity code in the same project, enabling optimizations (e.g., rewriting performance-critical parts in Rust) while maintaining access to Ethereum's liquidity and tools.
  • Innovation and Use Case Expansion: Unlocks advanced features via Rust libraries (e.g., ZK-proof verification, MPC schemes) for applications like privacy-preserving DEXs, DePIN integrations, or tokenization, which are resource-heavy or impractical on pure EVM setups.

Cons of Other Language Support (e.g., Rust) on Arbitrum Chains​

  • Learning Curve for Integration: Developers familiar with EVM/Solidity may face adjustments when handling MultiVM setups, intentional overrides (e.g., for reentrancy), or mixing languages, potentially increasing development time initially.
  • Variable Language Maturity: While Rust has strong SDK support, other WASM languages (e.g., those with custom runtimes like Python or JavaScript) are more complex to implement and may lack equally mature tooling or libraries for smart contracts.
  • Potential Interoperability Subtleties: Although fully compatible, differences in execution models between WASM and EVM could introduce edge cases or require additional testing for seamless cross-contract calls.
  • Newer Ecosystem Risks: As a relatively recent upgrade, Stylus and Rust support might have less battle-tested tools, audits, or community resources compared to the established EVM ecosystem, potentially exposing early adopters to undiscovered issues.
  • Dependency on WASM Limitations: Relies on WASM's ecosystem, which, while efficient, may impose constraints on certain features or require developers to adapt Web2 code for blockchain constraints like deterministic execution.