Stylus and EVM aren’t competitors. They’re teammates. Here’s why the future of smart contracts isn’t about picking sides, it’s about having options.
Solidity dominates smart contract development. It’s familiar and works well.
But forcing every developer to learn Solidity limits who builds onchain. Rust developers stay away. C++ teams skip blockchain entirely.
The EVM also has performance limits. Memory and compute costs scale poorly for certain workloads. Some computations get too expensive to run onchain.
Stylus lets you write smart contracts in Rust, C, or C++ through WebAssembly.
These contracts run alongside Solidity contracts. They talk to each other. A Rust contract calls a Solidity contract. A Solidity contract calls back.
Same chain. Same security. Different languages. The performance gap is real.
What stands out in benchmarks:
🔹 Execution speed improves dramatically for compute heavy workloads 🔹 Memory usage becomes far more efficient for complex logic 🔹 Heavy math becomes economically viable onchain Benchmarks show order of magnitude gains for specific compute and memory intensive operations when compared to Solidity.
These results come from running equivalent logic in both environments on Arbitrum.
The interoperability model:
1️⃣ Your Solidity DEX calls a Rust pricing oracle 2️⃣ The Rust oracle handles heavy computation efficiently 3️⃣ Results flow back to Solidity without friction 4️⃣ Everything executes in the same transaction You’re not migrating from EVM to WASM.
You’re combining them. Use Solidity for standard DeFi logic. Use Stylus for intensive operations like cryptography, advanced math, or simulations.
In my opinion, this shifts how people build:
- Rust developers build onchain without learning Solidity - Existing Solidity projects optimize expensive functions - New use cases become viable, like onchain gaming, ZK verification, or ML related computation - You pick the right tool for each job
The EVM stays. Solidity stays. Now you have more tools. Smart contracts open up to developers who previously stayed out.
Who wins here:
1️⃣ Solidity devs. Keep your code. Optimize the bottlenecks 2️⃣ Rust and C++ devs. Build onchain with languages you already know 3️⃣ Users. Pay less gas for complex logic
Personally, I think Solidity will handle business logic while Stylus handles performance critical paths. The best contracts will use both.
Try the Stylus quickstart at and see how Rust contracts interact with Solidity.
The debate isn’t EVM vs Stylus. It’s what you’ll build when you have both.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
Stylus vs. EVM: The Great Debate That Isn’t
Everyone keeps asking me: "Is @arbitrum Stylus going to replace Solidity?" Wrong question.
Stylus and EVM aren’t competitors. They’re teammates. Here’s why the future of smart contracts isn’t about picking sides, it’s about having options.
Solidity dominates smart contract development. It’s familiar and works well.
But forcing every developer to learn Solidity limits who builds onchain. Rust developers stay away. C++ teams skip blockchain entirely.
The EVM also has performance limits. Memory and compute costs scale poorly for certain workloads. Some computations get too expensive to run onchain.
Stylus lets you write smart contracts in Rust, C, or C++ through WebAssembly.
These contracts run alongside Solidity contracts. They talk to each other. A Rust contract calls a Solidity contract. A Solidity contract calls back.
Same chain. Same security. Different languages. The performance gap is real.
What stands out in benchmarks:
🔹 Execution speed improves dramatically for compute heavy workloads
🔹 Memory usage becomes far more efficient for complex logic
🔹 Heavy math becomes economically viable onchain
Benchmarks show order of magnitude gains for specific compute and memory intensive operations when compared to Solidity.
These results come from running equivalent logic in both environments on Arbitrum.
The interoperability model:
1️⃣ Your Solidity DEX calls a Rust pricing oracle
2️⃣ The Rust oracle handles heavy computation efficiently
3️⃣ Results flow back to Solidity without friction
4️⃣ Everything executes in the same transaction
You’re not migrating from EVM to WASM.
You’re combining them. Use Solidity for standard DeFi logic. Use Stylus for intensive operations like cryptography, advanced math, or simulations.
In my opinion, this shifts how people build:
- Rust developers build onchain without learning Solidity
- Existing Solidity projects optimize expensive functions
- New use cases become viable, like onchain gaming, ZK verification, or ML related computation
- You pick the right tool for each job
The EVM stays. Solidity stays. Now you have more tools. Smart contracts open up to developers who previously stayed out.
Who wins here:
1️⃣ Solidity devs. Keep your code. Optimize the bottlenecks
2️⃣ Rust and C++ devs. Build onchain with languages you already know
3️⃣ Users. Pay less gas for complex logic
Personally, I think Solidity will handle business logic while Stylus handles performance critical paths. The best contracts will use both.
Try the Stylus quickstart at and see how Rust contracts interact with Solidity.
The debate isn’t EVM vs Stylus. It’s what you’ll build when you have both.