Contributing to the decentralization of the #Ethereum network by providing ARM images. Staking on a $189 ARM board using ~10w. discord.gg/ve2Z8fxz5N

Spain
This is our @LidoFinance Community Staking Module HOME cluster protected by the @Obol_Collective DVT stack. Don't get fooled by the devices' fragile appearance. These are very powerful and rock-solid machines capable of running hundreds of validators flawlessly with a local #Ethereum node using just 10W of power. 3 different locations | 3 different ISPs | client diversity | HA | monitoring Decentralization at its best. βš™οΈ Setup consists of: βœ… 3 Obol nodes (@RadxaComputer 3x Rock 5B+, 24GB RAM) βœ… 2 Control nodes (1 Rock 5B 32 GB RAM + 1 NanoPC T6 ) βœ… 3 different locations (ISPs) βœ… Tailscale VPN connection Obol nodes run different Consensus and Execution clients locally to provide client diversity: @go_ethereum + @lodestar_eth @Nethermind + @grandineio @ethrex_client + @ethnimbus The Obol cluster is monitored by an in-house solution installed on all nodes (including the 2 control nodes in active/passive mode). It reports to a Telegram channel in case any issue/event arises: πŸ”΄ Missed attestations/blocks by each validator or a massive missed alert 🟒 A block is proposed by one of our validators πŸ“Š Obol cluster status: Charon state, network latency, validator clients... πŸ–₯️ Obol nodes status: Running services, CPU load, memory, disk usage... πŸ”„ Client updates availability Control nodes fulfill additional tasks to contribute to cluster health, HA, and monitoring: πŸ” Backup nodes: If the cluster goes down, a control node is ready to take over all validators through a synced local node, as it has all configs and keys available πŸ”— Obol relay: Both control nodes run a local Obol relay that allows the nodes to get a direct connection between them and minimize latency 🚨 Charon beacon fallback: All Charon nodes are configured with the Control nodes' beacon as fallback in case a local Obol node goes down Performance We are hitting 98.5-99.5% on the beaconcha.in score with client diversity. Best results come with Nimbus and Grandine as Consensus Clients, with a consistent β‰₯99.5%. Total cost (estimation)πŸ”² Boards (5 Γ— $270): $1,350 SSDs (5 Γ— $270): $1,350 MicroSD (5 Γ— $9): $45 Cases + cooling (5 Γ— $38): $190 Ethernet cables (5 Γ— $5): $25 Power supplies (5 Γ— $16): $80 ➑️ Grand total: ~$3,040 Documentation We released all the code and documentation for anyone to replicate the cluster. If you are a home staker and want to try a reliable solution to harden your setup, this is your chance: πŸ”— ethereum-on-arm-documentatio… Source Code github.com/EOA-Blockchain-La…
5
10
35
5,397
Ethereum on ARM (and RISC-V) πŸ¦‡πŸ”ŠπŸΌπŸ‘‰πŸ‘ˆπŸΌ retweeted
HABEMUS TESTNET β€” DAISUGI v0.1 A post-quantum Ethereum testnet using hash-based SPHINCS signatures with non-native account abstraction. Big thanks to @riva_labs and @GiulioRebuffo. Coming next: β€’ Frame Transactions β€’ Signature aggregation via LeanSPHINCS Believe in somETHing. Link ⬇️
27
44
249
61,357
Ethereum on ARM (and RISC-V) πŸ¦‡πŸ”ŠπŸΌπŸ‘‰πŸ‘ˆπŸΌ retweeted
We paved the way for client diversity, and then showed that Ethereum doesn’t have to be stuck at a 30M gas limit. Our mission is not complete yet. Next priorities: 1. Help bring post-quantum cryptography to Ethereum 2. Support Gnosis @etheconomiczone - the future of the L2 space 3. Participate in the ZK-Guests program 4. Leverage our top-tier formal verification and client teams under one company to build a formally verified client 5. Accelerate Ethereum strawmap and node development with AI and adapt to all challenges related to the new speed of development 6. Make the RPC layer more trustless, performant, and robust 7. Keep pushing Ethereum toward a stronger performance culture.
Nethermind Client 2.0.0 is out. It changes how the node stores Ethereum's state: archive nodes drop from ~30 TB to ~2 TB, you choose the history you keep, and blocks process 2–3Γ— faster than the previous release on a fresh node. Nine years since the first commit. The fastest execution software we've ever built. Breaking changes; read the notes before upgrading. Release: github.com/NethermindEth/net…
4
16
79
3,391
What an incredible work, congrats to all team and thank you for this amazing client. Updated. Run: sudo apt update && sudo apt install nethermind
Nethermind Client 2.0.0 is out. It changes how the node stores Ethereum's state: archive nodes drop from ~30 TB to ~2 TB, you choose the history you keep, and blocks process 2–3Γ— faster than the previous release on a fresh node. Nine years since the first commit. The fastest execution software we've ever built. Breaking changes; read the notes before upgrading. Release: github.com/NethermindEth/net…
4
24
1,781
Ethereum on ARM (and RISC-V) πŸ¦‡πŸ”ŠπŸΌπŸ‘‰πŸ‘ˆπŸΌ retweeted
We’re introducing new visualizations for the CSM module. You can now compare the module’s overall performance against the broader network, while also tracking validator decentralization within Lido’s Community Staking Module. We’re also introducing the Gini coefficient, a metric that helps quantify how concentrated stake is across validators; making it easier to monitor and understand the level of decentralization within the module. Take a look and let us know what you think. Which other metrics or insights would you like to see?
6
17
471
Ethereum on ARM (and RISC-V) πŸ¦‡πŸ”ŠπŸΌπŸ‘‰πŸ‘ˆπŸΌ retweeted
1. Nethermind 2.0 will have ~ 2TB mainnet archive with super fast eth_call. And if you want historical proofs it goes to 4.3 TB currently. The best part - you can really configure it based on your needs!
2
5
24
564
πŸŽ‰ 10 years ago today, we released our first image for running an #Ethereum node on a Raspberry Pi 3. 10 years later, the principles remain the same. We're living proof that decentralization doesn't need expensive hardware, just a $200 ARM board. Here's to 10 more years. πŸ₯‚
4
9
46
1,185
Ethereum on ARM (and RISC-V) πŸ¦‡πŸ”ŠπŸΌπŸ‘‰πŸ‘ˆπŸΌ retweeted
I would say I'm surprised, but really I'm just disappointed with the EF Protocol's continued presumption of decentralisation as a given. Let me be clear: FOCIL doesn't work if the attester set doesn't want it to. The protocol priorities post focuses on post-quantum as a goal, fine, and pays lip service to CROPS; "FOCIL is HegotΓ‘'s consensus-layer centerpiece. Our appetite beyond it is close to zero unless an addition directly supports post-quantum readiness." The elephant in the room the EF continues to ignore is that the chain is centralising at a rapid pace, and there is a lack of interest in either acknowledging the problems, or prioritising fixing any of them. For example, correlation penalties (7716) they describe as: "Adds slashing-logic surface for validator correlation with no CROPS or PQ contribution. Not a priority in a fork, we are trying to keep the CL scope light." This is inaccurate to start, 7716 has no slashing logic, and its misguided at best to assert that it doesn't contribute to CROPS. 7716 is the best EIP on the table to improve client diversity and penalise centralisation. It's not a panacea, but its what we have, it should not be DFI'd. Spending a year on H-star to ship FOCIL without addressing the validator set's underlying issues risks the big few centralised staking entities saying 'actually nah' and refusing to attest to slots with ILs they don't like. This costs them no rewards, thinking we'll socially slash them for it is wishful thinking, and now Ethereum is compromised and you need permission to use the chain. Preventing this outcome is not a matter of one EIP on the margin, it needs a cultural shift within the EF to realise they don't have a divine right from God to a decentralised chain, and that they can't just focus on academic challenges like PQ while ignoring real challenges like the ongoing acceleration in chain centralisation. We need quarterly reporting on the state of the chain, to make it harder for people to keep their head in the sand as to the severity of the situation. We need at least one EIP per fork focused on improving the nakamoto, staking gini, or other aspect of the validator set, and we need pragmatic, action-oriented leadership who care about Ethereum being CROPS beyond just a purity test. (I'm hoping that's @pcaversaccio). There are some people in the EF that care about the chain being CROPS for real, but unless we the community are outspoken and steadfast in our demands, they won't be listened to. Please show them why we're supporters of Ethereum and not any another centralised chain, please advocate for decentralisation and CROPS in H-star and beyond. Thank you.
The Protocol Cluster has published two new posts: HegotΓ‘ EIP Opinion Post and Tier List evaluates and grades all 62 EIPs proposed for HegotΓ‘, providing the cluster’s first unified tier list for a network upgrade Current and Emerging Priorities covers commitments and research arcs, anchored on a quantum-resistant Ethereum L1 by Dec. 2029 Offered as one input to HegotΓ‘ scoping, roughly 60 researchers, engineers, and individual domain experts across all 9 teams in the Protocol Cluster contributed to the HegotΓ‘ tier list, providing 397 tier grades before discussing contested items live. The plan, commitments, and shared set of cluster-wide priorities covered in the companion post provide the context behind the final tier grades. The Protocol cluster will host a Reddit AMA on r/ethereum on September 16 at 2pm UTC to talk through these priorities, the HegotΓ‘ tier list, and anything else on your mind. β†’ Submit questions ahead of time here: pad.ethereum.org/form/#/2/fo… Read the articles here: β†’ EF Protocol - Current and Emerging Priorities: blog.ethereum.org/2026/09/07… β†’ EF Protocol - The HegotΓ‘ EIP Opinion Post and Tier List: blog.ethereum.org/2026/09/07…
8
11
60
9,329
Updated. Run: sudo apt update && sudo apt install nimbus
πŸ“’ Nimbus consensus client `v26.3.0` is out now. The Nimbus consensus client `v26.3.0` is a `low-urgency` release which improves blob and column-handling performance. github.com/status-im/nimbus-…
2
458
Updated and tested in our cluster. Run: sudo apt update && sudo apt install dvt-obol
Charon v1.11.0 is live! This release includes: ⚑ Sync-committee contribution fix ⚑ Native NAT hole punching ⚑ Consensus, DKG, and p2p hardening Dig into the full release πŸ”½πŸ§΅
1
401
Ethereum on ARM (and RISC-V) πŸ¦‡πŸ”ŠπŸΌπŸ‘‰πŸ‘ˆπŸΌ retweeted
ethrex passing all frame transactions Hive tests now 🫑 hive.ethpandaops.io/#/group/…
ethrex is now the first client running the initial Frame Transactions Hive tests suite! We are currently working on fixing the current failing tests and also making the test suite more robust. More news on the frames front πŸ”œ
6
23
1,497
Ethereum on ARM (and RISC-V) πŸ¦‡πŸ”ŠπŸΌπŸ‘‰πŸ‘ˆπŸΌ retweeted
Two production distributed validator clients will introduce a whole new level of resilience and security for Ethereum Staking setups. If you do a distributed key generation with half Charon clients and half Pluto clients; not only will no operator see the full private key, there's not even one software implementation helping you create them that interacts with all of the private key shares. This idea of not having one single piece of software (or hardware or human) that can cause the compromise of a validator's private keys is where the ecosystem is maturing towards. I call this a stage 1 validator setup. Stage 2 is when a single point of failure doesn't even take the validator offline. Tens of billions of dollars in companies and funds are staking their investors' ETH for them. One developer getting phished or one software supply chain being compromised is not an acceptable risk for what could be a double digit % loss from the slashing penalty or worse, and operator failure is not necessarily covered in all staking insurance fine print. This is why institutions will stake their ETH with professional operators running collectively as part of a Stage 1+ distributed validator rather than individually. Two clients brings us another step closer to achieving that vision.
Two clients. One cluster. Pluto and Charon are validating side by side on the Hoodi testnet. πŸ§΅β¬‡οΈ
1
2
23
3,017
Ethereum on ARM (and RISC-V) πŸ¦‡πŸ”ŠπŸΌπŸ‘‰πŸ‘ˆπŸΌ retweeted
Community Staking Module keeps growing. Home Staking is the key for @ethereum decentralization and censorship resistance!
Replying to @LidoFinance
More than 90k ETH was allocated to Community Staking Module validators this quarter, increasing Lido’s permissionless module share to 8.2%. Ahead of the CSMv3 upgrade, 23 operators qualified for Identified Community Staker (ICS) status and 16 ICS operators obtained the newly introduced Identified DVT Clusters type, designed to accelerate DVT adoption across Lido's community operator set.
5
7
33
2,055
Outstanding client. We run it on our @Obol_Collective cluster. Light and rock solid. Looking forward to @ethlambda_lean release, btw.
Since reaching production readiness, ethrex has doubled as a playground for prototyping the future of Ethereum. Over the last few months, alongside hardening the client and preparing the next fork, we've been working with EF researchers and EIP authors to turn their proposals into running code: - zkEVM: EIP-8025 (Optional Execution Proofs) - Account Abstraction: EIP-8141 (Frame Transactions) - Privacy: EIP-8250 (Keyed Nonces), EIP-8272 (Recent Roots) - Censorship resistance: EIP-7805 (FOCIL) - Security: EIP-7906 (Transaction Assertions), the foundation for Trustless Clear Signing - Payments: Native UTXOs The post below covers the whole arc, from ethrex's beginnings to what we're building now. Deep dives on each feature are coming.
3
13
1,353
Ethereum on ARM (and RISC-V) πŸ¦‡πŸ”ŠπŸΌπŸ‘‰πŸ‘ˆπŸΌ retweeted
Two years ago, @LidoFinance committed to distributed validators to strengthen Ethereum's decentralization without compromising performance. Simple DVT delivered by beating the network average with zero correlated failures. Obol now recommends expanding DVT across the entire Lido protocol. Read the report: blog.obol.org/simple-dvt/
4
7
39
5,316
Ethereum on ARM (and RISC-V) πŸ¦‡πŸ”ŠπŸΌπŸ‘‰πŸ‘ˆπŸΌ retweeted
Enter: EthCoordinate. tl;dr: EthCoordinate is a crypto-native organization born inside the EthStaker community, bringing together separate efforts under one umbrella to help with Ethereum governance coordination, support Forkcast, increase stakeholder engagement on proposed or upcoming EIPs and, of course, continue providing software, tooling, and technical support for home stakers. EthStaker started in 2020 when a loosely connected group of Ethereum enthusiasts joined efforts to speed up the development of the beacon chain. The organization steadily evolved, incorporating as a 501(c)4 nonprofit and taking up initiatives around independent participants of Ethereum's consensus mechanism, aka home stakers. Throughout the years, it has played a decisive role in coordinating the launch and operation of devnets, testnets, and mainnet hard fork upgrades; facilitating information flows and generally connecting dots that needed connecting. This year's tectonic organizational changes in the ecosystem have opened up functional gaps in Ethereum coordination. To close these gaps and continue supporting the network, EthStaker's core members are joined by mission-aligned fresh blood to aggregate efforts under one name to produce greater results than operating independently. EthCoordinate is a natural evolution of EthStaker; as Ethereum mainnet heads to its third radical consensus protocol change at a steady pace, it’s time for EthStaker to recalibrate around what Ethereum’s evolving community needs. Our mission is to facilitate interaction between stakeholders of the ecosystem to accelerate the adoption of the Ethereum network and to provide continuity for governance operations. We believe that the Ethereum mainnet is an unparalleled bedrock for the augmentation of humanity's productivity output and that ETH, the asset, is the token that aligns the incentives of all actors involved. We stand up for our values, combining technical rigor with pragmatism for Ethereum to continue being the most accessible and credibly neutral global blockchain. The team is 10 long-tenured Ethereum professionals and currently our main work streams are: β‡₯ Maintain a high-quality venue for independent stakers to remain engaged and informed β‡₯ Facilitate coordination around core protocol development and adjacencies β‡₯ Develop and steward Forkcast, the most popular platform to track the research and engineering initiatives around Ethereum's core protocol β‡₯ Facilitate research, discussion, and coordination around protocol economics in support of Ethereum's long-term economic health β‡₯ Maintain open source tools and documentation used by participants of the consensus set We're energized for this chapter in Ethereum coordination & our role in it.
27
61
294
50,713