Arbitrum researchers argue that WebAssembly offers safer long-term flexibility for Ethereum’s execution layer than Vitalik Buterin’s preferred RISC-V architecture


A new technical debate has emerged within the Ethereum ecosystem after researchers from Offchain Labs, the core developers behind Arbitrum, challenged Vitalik Buterin’s proposal to shift Ethereum’s execution layer to the RISC-V instruction set architecture. Their analysis argues that WebAssembly (WASM) is a more reliable and future-proof choice for Ethereum’s Layer 1 smart contract format.


Offchain Labs Challenges RISC-V as Ethereum’s Smart Contract Foundation

In a detailed post published on Nov. 20, the researchers responded to Buterin’s earlier suggestion that adopting RISC-V could reduce zero-knowledge proving costs by up to 100x. While they agreed with the goal of improving proving efficiency, they emphasized that “one ISA cannot optimally serve both ZK-proving and smart contract delivery.”

The team — Mario Alvarez, Matteo Campanelli, Tsahi Zidenberg and Daniel Lumi — argued for a separation between two types of instruction formats:

  • a delivery ISA (dISA) used for uploading and storing contracts on-chain
  • a proving ISA (pISA) used by ZK-virtual machines

They underlined that these do not need to be the same, a distinction they say is crucial for Ethereum’s long-term adaptability.


Prototype Shows WASM Can Work With RISC-V Proving

Offchain Labs revealed that Arbitrum already uses a hybrid model. Stylus smart contracts are written in WASM, but the system still compiles WASM to RISC-V on the backend for ZK-proof generation.

The researchers wrote: “We can ZK-prove real-world blocks today in a blockchain that uses WASM as a dISA, by using a RISC-V-based ZK-VM as a backend.”
This demonstrates that Ethereum can benefit from RISC-V proving without locking its entire execution architecture to it.


Concerns About Lock-In and Rapidly Evolving Proving Technology

The team cautioned that selecting RISC-V for Layer 1 could lock Ethereum into a single hardware-oriented architecture at a time when ZK-VM innovation is accelerating. They noted that RISC-V itself is shifting quickly, moving from 32-bit to 64-bit implementations — a sign that the ecosystem is still in transition.

They also highlighted that ZK proving costs have already fallen to about $0.025 per Ethereum block, reducing the urgency to optimize exclusively for proving efficiency. For builders earning gas fees and MEV, they argue, the proving cost is “minimal”.


Why WASM May Be the Better Long-Term Choice

The researchers emphasized several advantages of WASM, including:

  • its structured and safe design, enabling code changes without breaking existing contracts
  • efficient execution on standard hardware, unlike RISC-V which most nodes must emulate
  • strong validation rules that prevent type errors and common vulnerabilities
  • a massive and mature tooling ecosystem proven across countless execution environments

They concluded that “WASM can be a sort of Internet Protocol for smart contracts,” serving as a universal layer between diverse programming languages and execution backends.


The debate over Ethereum’s future execution architecture is far from settled, but Offchain Labs’ argument strengthens the case for WASM’s flexibility, safety, and compatibility. As ZK-proof technology rapidly advances, Ethereum developers now face a critical question: whether to embrace a hardware-oriented ISA like RISC-V or rely on WASM as a more adaptable foundation for the coming decades.

Disclaimer

This content is for informational purposes only and does not constitute financial, investment, or legal advice. Cryptocurrency trading involves risk and may result in financial loss.

logo

blockto.io

info@blockto.io

Blockto.io Copyright © 2025, All rights reserved

News
Rates
Buy
More
We use cookies to personalize content and ads, provide social media features, and analyze our traffic. In accordance with GDPR/AVG and EU cookie regulations, data is processed only with your consent. We may share information about your use of our website with our social media, advertising, and analytics partners, and you can manage or withdraw your consent at any time. View more
Cookies settings
Accept
Privacy & Cookie policy
Privacy & Cookies policy
Cookie name Active

Privacy Policy

At BitxJournal.com, we respect your privacy and are committed to protecting your personal data. This Privacy Policy explains how we collect, process, store, and protect personal information in accordance with the General Data Protection Regulation (GDPR) and AVG (EU privacy legislation).

1. Data Controller

BitxJournal.com acts as the data controller for all personal data processed through this website.

2. Personal Data We Collect

We may collect and process the following categories of data:

Personal Data

  • Name and email address (when you subscribe to newsletters or contact us)

Technical & Usage Data

  • IP address, browser type, operating system

  • Device information

  • Pages visited, referral sources, and interaction data

This data is collected via cookies, log files, and analytics technologies.

3. Legal Basis for Processing

We process personal data only when a lawful basis exists, including:

  • Consent – when you explicitly agree (e.g., cookies, newsletter sign-up)

  • Legitimate interest – to operate, secure, and improve our website

  • Legal obligation – when required by applicable laws

You may withdraw your consent at any time.

4. Purpose of Data Processing

Your data is processed for the following purposes:

  • Operating and maintaining the website

  • Improving content, usability, and performance

  • Sending newsletters or updates (only with consent)

  • Analyzing traffic and user behavior

  • Responding to inquiries or support requests

5. Cookies & Consent Management

We use cookies and similar technologies in compliance with EU Cookie Law.

  • Non-essential cookies are placed only after explicit user consent

  • Users may accept, reject, or manage cookie preferences at any time

  • Consent can be withdrawn without affecting prior lawful processing

Detailed cookie information is available in our Cookie Settings panel.

6. Third-Party Data Processing

We may share limited data with trusted third-party service providers, including:

  • Analytics providers (e.g., Google Analytics)

  • Advertising partners (for personalized or non-personalized ads)

These third parties act as data processors and process data only under contractual obligations compliant with GDPR/AVG.

7. International Data Transfers

Where data is transferred outside the European Economic Area (EEA), we ensure appropriate safeguards are in place, such as Standard Contractual Clauses (SCCs) or equivalent legal mechanisms.

8. Data Retention

We retain personal data only for as long as necessary to fulfill the purposes outlined in this policy or as required by law.

9. Data Security

We implement appropriate technical and organizational security measures to protect personal data against unauthorized access, alteration, disclosure, or destruction.

10. Your GDPR Rights

Under GDPR/AVG, you have the right to:

  • Access your personal data

  • Rectify inaccurate or incomplete data

  • Request data erasure (“right to be forgotten”)

  • Restrict or object to processing

  • Data portability

  • Withdraw consent at any time

  • Lodge a complaint with a supervisory authority

11. Changes to This Privacy Policy

We reserve the right to update this Privacy Policy at any time. Any changes will be posted on this page with a revised effective date.

12. Contact Information

For privacy-related inquiries or GDPR requests, contact:

📧 Email: support@blockto.io
🌐 Website: https://blockto.io

Save settings
Cookies settings