Long-term L1 execution layer proposal: replace the EVM with RISC-V

The post proposes replacing the EVM with RISC-V as the virtual machine that smart contracts are written for, arguing this would greatly improve Ethereum execution-layer efficiency and simplicity. It says accounts, cross-contract calls and storage would stay the same, with opcodes like SLOAD, SSTORE and CALL becoming RISC-V syscalls, and that Solidity and Vyper could add RISC-V as a backend. The author argues that replacing the ZK-EVM with RISC-V addresses bottlenecks in statelessness-related data availability and ZK-EVM proving, noting that block_execution makes up roughly half of prover cycles today. The post outlines three implementation routes: supporting two VMs, converting EVM contracts into calls to a RISC-V EVM interpreter, or enshrining a protocol-level VM interpreter, with the Nervos CKB VM cited as a precedent.