# Risc-v

**URL:** https://collective.flashbots.net/t/risc-v/4793
**Category:** References
**Tags:** hardware, software
**Created:** [March 21, 2025, 2:56pm UTC](https://collective.flashbots.net/t/risc-v/4793 "2025-03-21T14:56:46Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![guayabyte](https://collective.flashbots.net/user_avatar/collective.flashbots.net/guayabyte/32/4_2.png) [@guayabyte](https://collective.flashbots.net/u/guayabyte)
#### Post date: [March 21, 2025, 2:56pm UTC](https://collective.flashbots.net/t/risc-v/4793/1 "2025-03-21T14:56:46Z")

</div>

Decentralization requires open, traceable and repairable hardware. Currently almost all of Ethereum nodes are running in corporate clouds that are privative, opaque, and planned for obsolescence.

The RISC-V instruction set architecture has a free license. This opens space for many of the explorations needed in a decentralized economy, otherwise blocked by the corporations that dominate technology.

Share your links here 🕸 .

[course] [Introduction to RISC-V](https://collective.flashbots.net/t/introduction-to-risc-v/3811)  
[course] [Building a RISC-V CPU core](https://collective.flashbots.net/t/building-a-risc-v-cpu-core/4023)  
[course] [Computer architecture with an industrial RISC-V core](https://collective.flashbots.net/t/computer-architecture-with-an-industrial-risc-v-core/4160)  
[course] [Foundations of RISC-V assembly programming](https://collective.flashbots.net/t/foundations-of-risc-v-assembly-programming/4788)  
[notes] [RISC-V cheat sheet](https://collective.flashbots.net/t/risc-v-cheat-sheet/3820)  
[article] [RISC-V - Debian Wiki](https://wiki.debian.org/RISC-V)  
[notes] [LicheePi 4A board](https://collective.flashbots.net/t/licheepi-4a-risc-v-board/4086)  
[video, 2023] [Self-Hosting (Almost) All The Way Down](https://collective.flashbots.net/t/self-hosting-almost-all-the-way-down/4165)

# Ethereum execution clients

- [Geth](https://collective.flashbots.net/t/geth/4873#p-10032-risc-v-support-1)

# Ethereum consensus clients

- [Grandine](https://collective.flashbots.net/t/grandine/4872#p-10031-risc-v-support-1)
- [Lighthouse](https://collective.flashbots.net/t/lighthouse/4857#p-10012-risc-v-support-1)
- [Lodestar](https://collective.flashbots.net/t/lodestar/4869#p-10028-risc-v-support-1)
- [Nimbus](https://collective.flashbots.net/t/nimbus/4870#p-10029-risc-v-support-1)
- [Prysm](https://collective.flashbots.net/t/prysm/4792#p-9884-risc-v-support-1)
- [Teku](https://collective.flashbots.net/t/teku/4871)

---

<div class="post-metadata">

### Author: ![guayabyte](https://collective.flashbots.net/user_avatar/collective.flashbots.net/guayabyte/32/4_2.png) [@guayabyte](https://collective.flashbots.net/u/guayabyte)
#### Post date: [September 1, 2024, 1:06pm UTC](https://collective.flashbots.net/t/risc-v/4793/2 "2024-09-01T13:06:48Z")

</div>

> **[Is RISC-V Ready For Supercomputing?](https://semiengineering.com/is-risc-v-ready-for-supercomputing/)**
>
> The industry seems to think it is a real goal for the open instruction set architecture.

---

<div class="post-metadata">

### Author: ![guayabyte](https://collective.flashbots.net/user_avatar/collective.flashbots.net/guayabyte/32/4_2.png) [@guayabyte](https://collective.flashbots.net/u/guayabyte)
#### Post date: [November 2, 2024, 2:51am UTC](https://collective.flashbots.net/t/risc-v/4793/3 "2024-11-02T02:51:15Z")

</div>

> **[RISC-V extensions: what’s available and how to find them - Red Hat Research](https://research.redhat.com/blog/article/risc-v-extensions-whats-available-and-how-to-find-it/)**
>
> Extensions available in RISC-V enable the customizations that make it ideal as a basis for open innovation. Here’s the extension situation as it stands today. RISC-V is a new Instruction Set Architecture (ISA) that, over the next decade, will compete...

---

<div class="post-metadata">

### Author: ![guayabyte](https://collective.flashbots.net/user_avatar/collective.flashbots.net/guayabyte/32/4_2.png) [@guayabyte](https://collective.flashbots.net/u/guayabyte)
#### Post date: [November 7, 2024, 11:58pm UTC](https://collective.flashbots.net/t/risc-v/4793/4 "2024-11-07T23:58:10Z")

</div>

> **[RV32I Base Integer Instruction Set](https://varshaaks.wordpress.com/2021/07/19/rv32i-base-integer-instruction-set/)**
>
> RV32I is sufficient for use in a modern operating system. It is designed specifically to reduce hardware complexity. It has 47 instructions in total. RV32I hardware can emulate any other extension …

---

<div class="post-metadata">

### Author: ![guayabyte](https://collective.flashbots.net/user_avatar/collective.flashbots.net/guayabyte/32/4_2.png) [@guayabyte](https://collective.flashbots.net/u/guayabyte)
#### Post date: [November 23, 2024, 12:49am UTC](https://collective.flashbots.net/t/risc-v/4793/5 "2024-11-23T00:49:43Z")

</div>

[https://lowrisc.org/news/sonata-v1-0-release/](https://lowrisc.org/news/sonata-v1-0-release/)  
Sonata is a platform that puts CHERIoT hardware in the hands of embedded systems engineers.  
The [CHERIoT technology](https://www.microsoft.com/en-us/research/publication/cheriot-rethinking-security-for-low-cost-embedded-systems/) was initially created by Microsoft using lowRISC’s RISC-V [Ibex](https://github.com/lowRISC/ibex)® core and based on the [CHERI](https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/) research at the University of Cambridge and SRI International. CHERI mitigates memory safety vulnerabilities such as buffer overflows and use after free. On top of this, CHERIoT capabilities allow for scalable and efficient compartmentalisation, which is essential if you want to run untrusted software on your embedded systems.

---

<div class="post-metadata">

### Author: ![guayabyte](https://collective.flashbots.net/user_avatar/collective.flashbots.net/guayabyte/32/4_2.png) [@guayabyte](https://collective.flashbots.net/u/guayabyte)
#### Post date: [March 29, 2025, 2:01am UTC](https://collective.flashbots.net/t/risc-v/4793/6 "2025-03-29T02:01:53Z")

</div>

> **[RISC-V Vector Register Groups](https://fprox.substack.com/p/risc-v-vector-register-groups)**
>
> extending vector register size through register grouping

---

<div class="post-metadata">

### Author: ![guayabyte](https://collective.flashbots.net/user_avatar/collective.flashbots.net/guayabyte/32/4_2.png) [@guayabyte](https://collective.flashbots.net/u/guayabyte)
#### Post date: [April 14, 2025, 1:59pm UTC](https://collective.flashbots.net/t/risc-v/4793/7 "2025-04-14T13:59:06Z")

</div>

> **[Ethereum Full Node on RISC-V. Breakthrough by Web3 Pi](https://www.web3pi.io/blog/ethereum-node-on-risc-v)**
>
> We’ve successfully run a fully synced Ethereum node on RISC-V—possibly for the first time in blockchain history. Web3 Pi proves it's possible, though still experimental, by splitting the Execution and Consensus clients across two open-source RISC-V...

---

<div class="post-metadata">

### Author: ![guayabyte](https://collective.flashbots.net/user_avatar/collective.flashbots.net/guayabyte/32/4_2.png) [@guayabyte](https://collective.flashbots.net/u/guayabyte)
#### Post date: [April 21, 2025, 7:31pm UTC](https://collective.flashbots.net/t/risc-v/4793/8 "2025-04-21T19:31:53Z")

</div>

> **[Long-term L1 execution layer proposal: replace the EVM with RISC-V](https://ethereum-magicians.org/t/long-term-l1-execution-layer-proposal-replace-the-evm-with-risc-v/23617)**
>
> This post proposes a radical idea for the future of the Ethereum execution layer, one that is equally as ambitious as the beam chain effort is for the consensus layer. It aims to greatly improve the efficiency of the Ethereum execution layer,...
