Contributing to the decentralization of the #Ethereum network by providing ARM images. Staking on a $189 ARM board using ~10w. https://xitter.cf/t.co/HyeqBMjtnS

Spain
Joined January 2020
๐ŸŽ‰ 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
47
1,206
Ethereum on ARM (and RISC-V) ๐Ÿฆ‡๐Ÿ”Š๐Ÿผ๐Ÿ‘‰๐Ÿ‘ˆ๐Ÿผ retweeted
Charon v1.11.2 has been released! This is a patch release addressing the intermediate CA certificate compromise. Mainnet operators are encouraged strongly to update to this release ASAP. github.com/ObolNetwork/charoโ€ฆ Hoodi operators read below ๐Ÿ‘‡
4
2
1
20
2,182
Ethereum on ARM (and RISC-V) ๐Ÿฆ‡๐Ÿ”Š๐Ÿผ๐Ÿ‘‰๐Ÿ‘ˆ๐Ÿผ retweeted
No downtime, no rush, no issues. Run distributed validators.
Upgrading our @Obol_Collective #Ethereum staking cluster nodes from Noble to Resolute one by one. No downtime, no rush, no issues. If you are staking from home, build a DVT cluster.
1
2
12
1,492
Ethereum on ARM (and RISC-V) ๐Ÿฆ‡๐Ÿ”Š๐Ÿผ๐Ÿ‘‰๐Ÿ‘ˆ๐Ÿผ retweeted
Over the past few months, the @Nethermind Client team has been focusing on almost everything BUT performance - authoring, supporting and reviewing EIPs for Glamsterdam, championing Hegota headliner - Frame Transactions, researching state bloat, and much more. That's not changing - we are still being heavily involved in Ethereum roadmap. But AI has unlocked a whole new level of productivity for us, and we're now pushing hard on several fronts: 1. zk guest program - coming soon to @eth_proofs. Very promising, very performant. 2. RPC refresh - Geth compatibility, major performance improvements, and more. Few projects already got a feeling of what we are shipping - and it is looking very good. 3. Client hardening with AI - Node MCP for users and our custom CoreMCP for developers, helping us ship faster and build a much more stable client. 4. Innovative node optimizations and advanced plugins - unlocking capabilities that could be extremely useful for many projects across the ecosystem, including support for new chains. And that's just the beginning. As a "side effect," we've also significantly improved the node's performance at the tip of the chain - before even getting into the Glamsterdam hard fork, which should unlock a whole new level of throughput. Nethermind is the fastest #Ethereum execution client, and the only one pushing beyond 1.5 GGas/s in p50 block throughput at the tip of the chain. With the next fork, we expect that ceiling to go even higher - based on Sepolia data, potentially around 3x higher. And we're definitely not done. We want to change the rules of the game. The AI-powered tools we've built in-house are giving us enormous leverage, and we're confident this advantage will only grow over time. Performance is good. ๐Ÿš€
5
12
4
81
4,273
Ethereum on ARM (and RISC-V) ๐Ÿฆ‡๐Ÿ”Š๐Ÿผ๐Ÿ‘‰๐Ÿ‘ˆ๐Ÿผ retweeted
Margaret Hamilton, who led the team that wrote the code that put humans on the moon, has died at 90 ๐Ÿ•Š๏ธ
276
9,466
501
119,036
3,208,456
Ethereum on ARM (and RISC-V) ๐Ÿฆ‡๐Ÿ”Š๐Ÿผ๐Ÿ‘‰๐Ÿ‘ˆ๐Ÿผ retweeted
bunker.supplies Quick POC of a post-quantum Ethereum wallet. - Retains the same address* - Rotates key every transaction* - Uses Safe + Bip39 as rotation system - Works with any HD derived ECDSA wallets - No new cryptography xitter.cf/drakefjustin/status/21โ€ฆ
Today I call upon the blockchain industry to calmly begin planning for "bunker mode". My personal recommendation is to set in motion a controlled mass migration of assets to fresh addresses, i.e. addresses whose pubkeys remain hidden behind a hash. Holders, starting with large and sophisticated ones, should consider moving the bulk of their funds to addresses that have never signed a transaction. And when they do sign one, they should also move remaining funds to a new address (possibly generated from the same seed phrase). Don't rush. While I believe there is cause for action a rushed migration would do more harm than good. Don't panic either. Moving assets to protected addresses is a simple, preventative step which does not require new cryptography or new wallets. IMO it is now reasonable to brace for the possibility that ECDSA breaks before qday, in the worst case in months not years. By "break" I mean fast private key recovery (e.g. in one week) on available hardware (e.g. a large GPU cluster). Recent days have been humbling for human mathematical intuition. Long-held, unquestioned hypotheses have fallen. This includes the n log(n) bound for integer multiplication and the 3SUM conjecture. In hindsight, May's unexpected disproof of the Erdล‘s unit distance conjecture was our warning shot. Yesterday's OpenAI drop made it clear that mathematical superintelligence is upon us. They say there are weeks where decades happen. We are about to live through weeks where centuries of mathematical progress happen. Could our magic 64-byte ECDSA signatures be too good to be true? Was it just security through obscurity all this time? Elliptic curves feel especially vulnerable to superintelligence. Curves carry rich structure, with room for fancy tricks like Schoof, Frobenius, pairings. (By contrast, hashes are designed to minimise algebraic structure.) Separately, as Ewin Tang can attest, an efficient quantum algorithm sometimes foreshadows an efficient classical one. We should be open to the possibility of a classical counterpart to Shor that breaks elliptic curves and RSA at once. Also noteworthy is the striking under-representation of cryptographic breakthroughs among the 722 mathematical results OpenAI published. I've witnessed first-hand the US government censoring academic quantum cryptanalysis results. Backroom interventionism is my base case. I urge large, sophisticated actors to lead by example. Project11's "risq list" (bitcoin-risq-list.projecteleven[.]com) is a great tracker of exposed BTC pubkeys. Binance, Bitbank, Robinhood, Bitfinex, and Tether have an opportunity to harden their cold storage. Next month I'll address institutions in London in a live Q&A (forum.ethereuminstitutional[.]org/london-2026). Again, please do not rush. Wallets holding under 50 BTC enjoy partial cover from "Satoshi's shield", i.e. his 20K exposed addresses that hold 50 BTC each. Load-bearing signers like oracles and L2 security councils should consider rotating ECDSA pubkeys with every signed message and/or multi-signing with a hash-based schemes like SPHINCS. Exiting bunker mode safely will require post-AI cryptography. My inclination is to go all-in on hash-based cryptography and avoid structured mathematical assumptions entirely, whether from curves, lattices, or isogenies. A single battle-tested hash (e.g. from the SHA or BLAKE families) yields plausible post-AI security. The Ethereum roadmap on strawmap[.]org fully embraces hash-based cryptography with end-to-end formal verification as a response to the quantum threat. Those timelines must now be revisited and accelerated in light of mathematical superintelligence. I'll be pushing for maximum defensive acceleration.
19
13
7
150
14,893
Upgrading our @Obol_Collective #Ethereum staking cluster nodes from Noble to Resolute one by one. No downtime, no rush, no issues. If you are staking from home, build a DVT cluster.
1
1
1
5
1,336
Ethereum on ARM (and RISC-V) ๐Ÿฆ‡๐Ÿ”Š๐Ÿผ๐Ÿ‘‰๐Ÿ‘ˆ๐Ÿผ retweeted
Atomic synchronous composability is no longer a promise. History made on mainnet: the first atomic cross-chain L1->L2 transaction ever ๐Ÿ”ฅ And this is only the beginning for EEZ ... ๐Ÿš€ @etheconomiczone
83
132
49
736
123,082
Ethereum on ARM (and RISC-V) ๐Ÿฆ‡๐Ÿ”Š๐Ÿผ๐Ÿ‘‰๐Ÿ‘ˆ๐Ÿผ retweeted
1/ How I infiltrated a Chinese organized crime syndicate that has laundered $1B+ across multiple exploits for Lazarus Group. Posing as a client, I gathered intel that helped action freezes for the Feb 2025 Bybit exploit and attribute illicit activity onchain.
1,941
4,198
1,300
30,401
4,843,311
Ethereum on ARM (and RISC-V) ๐Ÿฆ‡๐Ÿ”Š๐Ÿผ๐Ÿ‘‰๐Ÿ‘ˆ๐Ÿผ retweeted
Replying to @jdetychey @arlery
Thank you for engaging in good faith with a smile on your face through a long onslaught, itโ€™s not easy :) If I take the moment to tl;dr some of the key places the proposal fell down imo, (that more or less fit your categories) - protecting ETHโ€™s security and resistance to capture is more dictated by the Nakamoto (and withdrawal cred gini) than the ratio. The strawman to exemplify that is a validator set with a Nakamoto of 20, good gini, and staking ratio of 80% is more secure and capture resistant than one with a 47% ratio and Nakamoto of 3. We need to start measuring these numbers, and building rough consensus on where they should be, to enable agreed upon change. Would love your help here, whatโ€™s your minimum tolerable Nakamoto for eth? - we need to take a zk-L1 seriously, and model the economics of it, and how we reach the social consensus (๐Ÿ‘†) builder diversity numbers. We donโ€™t get many changes of economics while retaining moneyness (your second objective), so letโ€™s make sure proving and aggregating make economic sense and are not winner takes all. - I donโ€™t think any curve that goes to zero at a reachable point is wise, it allows for a lowest cost wins game. This proposal in particular meant that weak validators in high ratio environments would be extra screwed in reward nvm economies of scale, it would have been ruinous for the indie stakers. Tails at 0.5% ->1.5% issuance are fine imo. - we need community alignment on if CROPS > hard money or not. IMO Ethereum is not bitcoin and shouldnโ€™t try to be. Hard money/increasing the burn is in contention with extra marginal scaling, we should pick it. Tbh a 1% dilution on eth makes it a better normal money, versus a store of value asset (hard/ultrasound). You can avoid this dilution by taking a risk and staking your eth. - letโ€™s fix the tax treatment on solo staking in proactive jurisdictions - we can make Ethereum staking more decentralised (and likely impede higher staking ratios) with other EIPs such as 7716, or by making a price to exit stake. Would love your support on that one for Hegota as a compromise win. :) - lastly, a good cost model for staking would help understand what a marginal change to economics would do to the chain health metrics, including whether theyโ€™re likely to surpass our social consensus decentralisation thresholds Many things here, some you already mentioned, some not, but you have my continued support and engagement in trying to get Ethereum into a more healthy secure and decentralised state. Bonne chance. :)
2
20
513
Ethereum on ARM (and RISC-V) ๐Ÿฆ‡๐Ÿ”Š๐Ÿผ๐Ÿ‘‰๐Ÿ‘ˆ๐Ÿผ retweeted
๐Ÿ“‹Withdrawing EIP-8363 from consideration for Hegotรก. EIP-8363 rapidly became one of the most commented-on EIPs in the history of the Ethereum-Magicians forum, with 200+ comments in a few weeks. As we progressed through the Hegotร  CFI (Consideration For Inclusion) process, several parties in the industry as well as core protocol and client contributors voiced that a fork scoping exercise was not the right venue to settle an issuance policy change. We agree and we'd rather acknowledge this now than carry on towards Hegotร  in this context. The topic is too important and raised too many concerns that it deserves its own process. We commit to giving issuance its own process and we thank the entities such as @LidoFinance who offered to help steer such an initiative. We stand by the motivation of this EIP, in particular: โ€œa very high staking ratio is undesirable for two distinct reasons (...), preserving Ethereumโ€™s security, neutrality and resistance to capture, and protecting ETHโ€™s role as money.โ€ Not everybody immediately relates to both reasons and for others recognizing just one of these reasons is enough to justify a change. Nevertheless, we will all benefit from improving our understanding of the issue and what is at stake. The questions we have faced since we published EIP-8363 can be boiled down to 5 categories: โžก๏ธSecurity: What does a lower ratio actually secure versus a higher ratio? โžก๏ธIndustry impact: What else is built on the yield and what will be the impact ? โžก๏ธCurve specs and alternate tools: Is this curve even the right instrument? โžก๏ธComposition: Who is left staking (the effect on the composition of the validator set) ? โžก๏ธDecentralization: How will solo stakers be impacted by the reduction? We already argued a lot, conceded some and adjusted a few points in the very long Ethereum-Magicians thread mentioned supra. For a broader consensus to emerge and a better issuance policy for Ethereum to be designed and adopted, we need a dedicated process. We call for all willing hands to help and contribute to this, please do reach out. Hereโ€™s our start at what a multi-node process would look like (table attached). Onward and forward, letโ€™s improve Ethereum.
๐Ÿšจ New EIP: Tapered Issuance Burn We just submitted an EIP to ethereum/EIPs: a minimal, market-driven fix to Ethereum's issuance policy removing the incentive for stake growth beyond 50% of ETH supply. EIP-8361 by @pintail_xyz, @jdetychey, @dapplion, @pa7x1, @ladislaus0x & @drakefjustin ๐Ÿงต
33
36
20
204
46,723
Ethereum on ARM (and RISC-V) ๐Ÿฆ‡๐Ÿ”Š๐Ÿผ๐Ÿ‘‰๐Ÿ‘ˆ๐Ÿผ retweeted
I've been working in Ethereum for nearly 10 years and it still feels great to send a transaction to your own self-hosted node. Reading and writing from the chain without any intermediary. No other chain comes close to how easy it is with Ethereum.
32
43
6
493
14,509
If you are home staker running a solo node, switch to DVT. Now.
2
1
12
1,579
Ethereum on ARM (and RISC-V) ๐Ÿฆ‡๐Ÿ”Š๐Ÿผ๐Ÿ‘‰๐Ÿ‘ˆ๐Ÿผ retweeted
Ethereum should be anti-fragile; failures should strengthen it. A correlated downtime should hurt more than an uncorrelated one. EIP-7716 would encourage more client diversity, and would make Ethereum resilient to black swan failures. Short term pain, long term gain.
Ethereum is considering correlated downtime penalties for stakers, an idea by @VitalikButerin. The aim is to disincentivise centralised points of failure before they cause a mass slashing event I made a website to understand the EIP and why we should adopt it ๐Ÿ”— below, tl;dr๐Ÿ‘‡
3
6
1
29
2,979
Ethereum on ARM (and RISC-V) ๐Ÿฆ‡๐Ÿ”Š๐Ÿผ๐Ÿ‘‰๐Ÿ‘ˆ๐Ÿผ retweeted
Syncing an Ethereum node is the first step towards freedom.
Replying to @blockrotator
Syncing an Ethereum node is the first step towards freedom.
3
2
18
1,253
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
46
9
255
68,867
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
85
3,592
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,828
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
480
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
573