Episode Summary
Executive Summary: At Axelar Interoperability Summit, Arbitrum’s Stephen Goldfeder explained Stylus as “EVM Plus”: a way to keep full EVM compatibility while letting developers write smart contracts in Rust, C, and other languages compiled to WASM, potentially boosting performance and lowering costs. He also discussed cross-rollup interoperability, arguing L2s should collaborate on standards rather than impose isolated “superchain” visions.
Main Topics: Stylus as “EVM Plus” (Priority: 5/5): Stylus expands Arbitrum beyond Solidity by supporting additional languages while preserving EVM compatibility, aiming to attract more developers without forcing them to learn Solidity. WASM-based execution model (Priority: 5/5): Goldfeder explained that Nitro’s shift to WebAssembly underpins Stylus, making it possible for multiple languages to compile to Arbitrum’s underlying execution environment. Developer accessibility and cost efficiency (Priority: 4/5): He framed Stylus as a way to bring in “the next million developers” and to offer about a 10x cost benefit, especially for computationally heavy or custom logic. Prismatic Labs and Ethereum L1 work (Priority: 3/5): The discussion clarified that Arbitrum’s Prismatic Labs acquisition was not primarily about Stylus, but about strengthening Ethereum L1 work such as EIP-4844, while still contributing ideas across teams. Layer 2 competition and interoperability (Priority: 5/5): Goldfeder addressed the intensifying L2 “wars” and said Arbitrum will not unilaterally brand its own superchain; instead, it wants industry-wide cooperation on interoperability. Shared standards over branded ecosystems (Priority: 4/5): He argued that interoperability should serve users, not chain brands, and that rollup teams should work together on standards now to make future integration easier.
Key Arguments: Arbitrum Stylus preserves full EVM compatibility while adding support for more languages, so developers can choose the ecosystem they want without being constrained by language. Most developers already know languages like Rust or C, not Solidity; Stylus lowers the barrier to building on Arbitrum. The underlying technical enabler is Nitro’s WebAssembly-based architecture, which allows code compiled from many languages to run within Arbitrum’s proof system. Stylus can improve developer experience and potentially deliver major efficiency gains, including a cited 10x cost benefit for some workloads. Arbitrum sees L2s as a place for innovation that may later influence Ethereum L1 if features prove valuable and gain community support. Interoperability cannot be dictated by one team; even strong players like Arbitrum must collaborate on cross-rollup standards to avoid repeating ecosystem fragmentation at a higher layer.
Data Points: Users on Kraken: over 9 million - Sponsor segment describing Kraken’s scale and trustworthiness Kraken security record: not a cent lost - Sponsor segment highlighting Kraken’s safety claims Arbitrum transaction volume: already surpassing the ETH Layer 1 - Sponsor segment positioning Arbitrum as a high-throughput L2 Stylus efficiency claim: 10x cost benefit - Goldfeder described Stylus as offering a potentially large cost advantage in addition to developer benefits Arbitrum launch note: first layer-3 chain announcement in a week or two - Goldfeder said Arbitrum expects to announce the first L3 chain soon with better interoperability
Pivotal Quotes: "My thesis is to get the next billion users, we need the next million developers." — Stephen Goldfeder: Explaining why Stylus focuses on developer inclusivity and language flexibility "The language shouldn't be the determining factor." — Stephen Goldfeder: Describing Arbitrum’s goal of letting developers choose the ecosystem independently of programming language "How do we make one that integrates all of our technologies?" — Stephen Goldfeder: On the need for cross-rollup interoperability rather than siloed superchain branding
Implications: Stylus could make Arbitrum more attractive to mainstream developers and specialized teams, while the interoperability stance suggests L2s may need open standards and cooperation to avoid another layer of fragmentation.