Ethereum On ARM pfp

Ethereum On ARM

@ethereumonarm

376 Following
226 Followers


Marius van der Wijden pfp
Marius van der Wijden
@vdwijden
I recently wrote down some ideas on how to built a high throughput L2. Some of the design decisions that I would take (and that I suspect other rollups take as well) and why they can't be done on mainnet Ethereum. Check it out! https://mariusvanderwijden.github.io/blog/2024/07/12/L2s/
2 replies
9 recasts
42 reactions

Matthew pfp
Matthew
@mpryor.eth
I appreciate the @ethereumonarm community for how they educate on all things Ethereum nodes.
2 replies
1 recast
4 reactions

chun pfp
chun
@zkchun.eth
Using my boost to encourage more people to run a node. It's a cheap side project and made straightforward with @ethereumonarm Doesn't have to be crazy, you don't need to be a validator. Just a great way to learn about the tech we all love and believe in.
11 replies
55 recasts
214 reactions

Ethereum On ARM pfp
Ethereum On ARM
@ethereumonarm
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
0 reply
0 recast
0 reaction

Ethereum On ARM pfp
Ethereum On ARM
@ethereumonarm
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).
1 reply
0 recast
0 reaction

Ethereum On ARM pfp
Ethereum On ARM
@ethereumonarm
- 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
1 reply
0 recast
0 reaction

Ethereum On ARM pfp
Ethereum On ARM
@ethereumonarm
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
1 reply
0 recast
0 reaction

Ethereum On ARM pfp
Ethereum On ARM
@ethereumonarm
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.
1 reply
0 recast
0 reaction

Ethereum On ARM pfp
Ethereum On ARM
@ethereumonarm
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 👇
1 reply
0 recast
3 reactions

Péter Szilágyi pfp
Péter Szilágyi
@karalabe.eth
Fresh off the press, my proposal (and code) for execution layer cross validation (i.e. no more consensus faults, slashing or double spends™). Also supports stateless validators via MEV builders if you have a fat enough pipe for an MPT witness. https://gist.github.com/karalabe/47c906f0ab4fdc5b8b791b74f084e5f9
4 replies
127 recasts
667 reactions

Ethereum On ARM pfp
Ethereum On ARM
@ethereumonarm
6/ We will be releasing step-by-step guides to run Supernodes with several L2s, starting with Optimism and Base along with new OS images, particularly for 32 GB devices: Orange Pi 5 Plus and Rock 5B. Stay tuned and Stake at Home
0 reply
0 recast
0 reaction

Ethereum On ARM pfp
Ethereum On ARM
@ethereumonarm
5/ Some data: Board: Rock 5B 32 GB RAM Blue Edition Board price: $225 SSD: Silicon Power 4TB XS70 DB size: 2.3 TB Mode: Archive Geth: 1.14.5 Prysm: 5.0.3 Op-geth: 1.101315.1 Op-node: 1.7.6
1 reply
0 recast
0 reaction

Ethereum On ARM pfp
Ethereum On ARM
@ethereumonarm
4/ The Supernode (L1+L2) runs Geth + Prysm and Optimism op-geth+op-node. Note that this node needs a 32 GB RAM board and a 4 TB SSD disk to work properly. Both layers sync through Snap sync, so the node is up and running in about 1-2 days.
0 reply
0 recast
0 reaction

Ethereum On ARM pfp
Ethereum On ARM
@ethereumonarm
3/ Some data: Board: NanoPC-T6 16 GB RAM Board price: $189 SSD: Crucial P3 Plus 2TB Reth: 0.2.0-beta9 Prysm: 5.0.3 DB size: 2.3 TB Mode: Archive Snapshot: https://snapshots.merkle.io
2 replies
0 recast
0 reaction

Ethereum On ARM pfp
Ethereum On ARM
@ethereumonarm
2/ The archive node is running Reth and Prysm + 1 Validator. It was synced using a snapshot from Merkle (decompressing it from an NFS mount point). It took ~10h to sync. As seen on our Discord channel, it is possible to sync Erigon as well (takes around 2-3 weeks).
1 reply
0 recast
0 reaction

Ethereum On ARM pfp
Ethereum On ARM
@ethereumonarm
1/ From the very first day, we were promised that an /ethereum node could run on any consumer device. In 2024, you can run on a $200 ARM64 board using ~10w: - 1 Archive node + a validator client - A Supernode (L1+L2 on the same device) This is called decentralization. +info👇
3 replies
0 recast
8 reactions

Sassal.eth 🎩⛽ pfp
Sassal.eth 🎩⛽
@sassal.eth
Ethereum is not just a single network - it is a network of networks; a chain of chains; a root of trust. Ethereum is the infinite garden.
8 replies
14 recasts
195 reactions

Marius van der Wijden pfp
Marius van der Wijden
@vdwijden
On Feb. 6th @nero_eth and @parithosh_j sent a transaction on Sepolia which uncovered a bug that could've happened on mainnet. The bug was quickly fixed in the clients and now, after all nodes updated to Dencun, we can finally disclose the issue: https://blog.ethereum.org/2024/03/21/sepolia-incident
0 reply
2 recasts
8 reactions

autocrat 🎩 pfp
autocrat 🎩
@autocrat.eth
so unimaginably, unthinkably based. The moment I land in my new city for my job, this is the first thing on the agenda. Setting up ethereum super nodes.
0 reply
1 recast
1 reaction

Ethereum On ARM pfp
Ethereum On ARM
@ethereumonarm
Hardware info: Board: Rock 5B 32GB RAM Blue Edition Disk: Silicon Power 4TB XS70 Software: L1: Geth+Lighthouse L2: Optimism op-geth + op-node (snap sync)
0 reply
0 recast
0 reaction