Ethereum

This is a synced @go_etherereum node running on the Banana Pi BPI-F3 #RISCV board.

A lot of work ahead but so much potential for running #Ethereum nodes on Open Hardware.

+Detailed info 👇

Contributing to the Ethereum decentralisation by providing OS images that turn ARM64 boards into full Ethereum nodes.

Both Lighthouse en Nimbus don't go above 0.10 slots per second during the sync so they are unable to finish it (they only use one core for this task).

According to Nimbus docs, crypto hardware optimizations come from SHA256 and BLST.

Both Lighthouse en Nimbus don't go above 0.10 slots per second during the sync so they are unable to finish it (they only use one core for this task).

According to Nimbus docs, crypto hardware optimizations come from SHA256 and BLST.

https://t.co/Kd0uJb6hLQ

- SHA256 crypto extension are not available for the processor (at least for 6.6 kernel according to /proc/crypto)

- BLST use assembly code which seems only available for X86 and ARM64 only:

- SHA256 crypto extension are not available for the processor (at least for 6.6 kernel according to /proc/crypto)

- BLST use assembly code which seems only available for X86 and ARM64 only:

https://github.com/supranational/blst/?tab=readme-ov-file#performance

So, CPU and RAM doesn't seem to be the problem for running an #Ethereum node on #RISCV anymore. Most probably is a combination of enabling Crypto hardware extensions and developing specific software implementations on clients side (particularly the assembly code part).

If you are interested on running a node on RISCV or want to stay updated about it, jump in to our RISCV channel:

https://discord.com/channels/822548812472123404/1265978364397617222

First of all, we managed to sync only an execution client on the same board. As of today, Consensus clients struggle to run and they can't sync (even using Checkpoint sync).

We were able to compile Lighthouse and Nimbus.