Butta.eth
1.4K posts
Native UTXOs on Ethereum. Payments should be one-shot objects, not permanent state. Bitcoin got this right. Ethereum can bring the same idea to payments: prove existence from history, keep only a spent bit in state, and reduce permanent state by ~99.8%. Check out the blog post for details. ethresear.ch/t/native-utxos…
Today, the EF is changing shape, concluding a months-long process of reorganization as part of the implementation of the Mandate and the Treasury Management Policy. We come out of this process with the structure, activities, and people necessary for execution on the critical tasks ahead of us, but also with 54 fewer colleagues, roughly 20% of the EF, many of whom will be finding ways to contribute to Ethereum from outside the EF in the coming weeks. Find a brief introduction to the new structure, and learn more about how we are supporting the people who are leaving in the full post below:
awesome dashboard from @Butta_eth! after a slow start in 2025, usage of MaxEB / 0x02 withdrawal / "accumulating validators" is over 20% dune.com/butta_ethereum…
Stackin' layers on top.
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: 🔗 …m-on-arm-documentation.readthedocs.io/en/latest/stak… Source Code github.com/EOA-Blockchain…
