我是一个长期的 riscv 爱好者。我有 4 个 riscv 设备，我用它们做一些实验，有些作为家庭服务器，有些作为编译目标以检查工作，并作为我在 zkvms 上工作的测试平台在 r55 创建建建时在现场，我帮了帮助建且我想出了这个名字（我不会告诉你它的来源，这是个愚蠢的双关语）。
免责声明尽管它与当前关于 EOF 与 riscv 的争论相邻，但这主要是关于这个。这是对目前是否值得投入精力到 riscv 的的诚实评估。
在我看来，有几个理由不应该用 riscv 替换 EVM，更不用说在短期时内
- 不仅�一�个 riscv，有很多种类型。。在 32 字节和 64 字节之间有选择。有指令集架架构（ISA）的扩展以支持内存管理、浮点等……模块化很好，所有这这些扩译扩展可能令人感困惑。编�器通常只支持一个或两个目标，而且往往不是所需的那个。例如，go编 只编译到 riscv64gc，但大而大多数 zkvms 针对 riscv32imc。我们可能会花一年时间来决定我们想要哪些扩展。
- riscv 硬件本身仍然非常非常慢：在快速的 amd64 处理器上模拟 evm 比在 riscv 处理器上运行本机代码要快得多[*]
- 我听说一些说zkv始正在远离 riscv，要么使用 WASM（例如 powdr），要么开发自己的 ISA。据我所知，riscv 对 zk 也不太友好。它确实比 EVM 好，因为字大小更小，但可以做得更好。如果 zkvms 是最终目标，现在固定 riscv 可能是个坏主意。
总tldr
我确实喜欢 riscv 并希望有一个支持 riscv 的以太坊。我认为更好的路线是执行引擎。我的观点是，riscv 应该作为为生 Rollup 路线图的一部分，作为次要执行引擎，而不是 是 EVM VM 的替。这将使过渡更更更顺畅，因为引擎可以独立维护。
[*] 我知道存在一些中国主板性能更好，但目前无法购买，而且标价荒�<>到，保保留不��>内其一要�简文。只给我翻译结果，不要要要对内内容进行分析或，不要添加额外的说明明。: <
I have been a long-term riscv enthusiast. I have 4 riscv devices, that I toy with and use some as home servers, some as compilation targets to check that work, work a mykvwas when Disclaimer even though it's adjacent to the current debate on EOF v. riscv, this is not primarily about this. It's a honest evaluation of the relevance of investingiscenergyiscpoint.
In my my are a reasons not to to replace the EVM with riscv, let than alone term:
- One>is obvious when tinkering,, is that theiscthe ecosystem-ready: linkers lindeadly slow, library support is dre,arily wanting so very few things compile, and there is no network effect since very few projects even bother building riscv releases.
- There isn't only one riscv, there's many flavors many flavtheors. There's the choice the choice between 32 bytes and 64 bytes. set architecture (ISA) to support memory management management, floating etc points, modularity is great, but all these extensions these confusing.>
- The riscv hardware itself still is very very,, very slow: it's much faster to ememulate the evm on a fast aa 64 bit processor than a than native r[*><]
- I hear some zkvms are moving away from riscv and either using WASM (e.g. powdr) or developing their own ISA. From what I gather, riscv isn't that zk-friendly either li. It's definitely better than EVM because the word size is smaller, but it's possible to do much better. If If zkvms are the endgame, enshrining riscv now is probably a bad idea.
TLDR I don't think it's a good idea to rush into making such a big change at this moment.
I do love riscv and I want aiscwant a riscv-enabled Ethereum. I believe the better route, that would be engine that engine. My opinion is that riscv should come as part of the native rollthe roada, a replacement for the EVM. This would p This wouldmmakeother engine be maintained independently.
[*] I'm aware that there exist some Chinese boards that have much better performance, but they currently're for purchase, and the listed price is bonkers.
