我是一個長期的 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.
