Smartprogrammer's profile picture. Ethereum Core Developer @nethermindeth
Building https://surge.wtf/
Opinions are my own.
believe in somETHing.

smartprogrammer.eth ๐Ÿฆ‡๐Ÿ”Š

@Smartprogrammer

Ethereum Core Developer @nethermindeth Building https://surge.wtf/ Opinions are my own. believe in somETHing.

smartprogrammer.eth ๐Ÿฆ‡๐Ÿ”Š ๋‹˜์ด ์žฌ๊ฒŒ์‹œํ•จ

Benchmarking #Ethereum like thereโ€™s no tomorrow๐Ÿ“ˆ 277 trillion gas blocks, 130 GGas/s throughput! Nethermind: gimme MOAR! MGas๐Ÿค” GGas๐Ÿ”ฅ TGas๐Ÿ”œ A joint effort by @NethermindEth, @StatelessEth, @ethPandaOps & EF STEEL - pushing EL clients to the edge for fast, safe L1 scaling.

ChodoKamil's tweet image. Benchmarking #Ethereum like thereโ€™s no tomorrow๐Ÿ“ˆ

277 trillion gas blocks, 130 GGas/s throughput! Nethermind: gimme MOAR!
MGas๐Ÿค”
GGas๐Ÿ”ฅ
TGas๐Ÿ”œ

A joint effort by @NethermindEth, @StatelessEth, @ethPandaOps & EF STEEL - pushing EL clients to the edge for fast, safe L1 scaling.
ChodoKamil's tweet image. Benchmarking #Ethereum like thereโ€™s no tomorrow๐Ÿ“ˆ

277 trillion gas blocks, 130 GGas/s throughput! Nethermind: gimme MOAR!
MGas๐Ÿค”
GGas๐Ÿ”ฅ
TGas๐Ÿ”œ

A joint effort by @NethermindEth, @StatelessEth, @ethPandaOps & EF STEEL - pushing EL clients to the edge for fast, safe L1 scaling.

It looks like Ethereum client defaults will be set to a 60 million gas limit *before* Fusaka goes live in early December. This would be a ~33% increase from the current 45 million gas limit. Bullish Ethereum L1 scaling!

sassal0x's tweet image. It looks like Ethereum client defaults will be set to a 60 million gas limit *before* Fusaka goes live in early December.

This would be a ~33% increase from the current 45 million gas limit.

Bullish Ethereum L1 scaling!


smartprogrammer.eth ๐Ÿฆ‡๐Ÿ”Š ๋‹˜์ด ์žฌ๊ฒŒ์‹œํ•จ

EIP Spotlight: EIP-7642 (eth/69) โ€“ history expiry and simpler receipts. Co-authored by Nethermind Core developer Ahmad Bitar (@smartprogrammer), this EIP simplifies Ethereumโ€™s networking protocol and removes 530 GB of redundant sync data, making nodes faster and lighter ahead ofโ€ฆ

NethermindEth's tweet image. EIP Spotlight: EIP-7642 (eth/69) โ€“ history expiry and simpler receipts.

Co-authored by Nethermind Core developer Ahmad Bitar (@smartprogrammer), this EIP simplifies Ethereumโ€™s networking protocol and removes 530 GB of redundant sync data, making nodes faster and lighter ahead ofโ€ฆ

smartprogrammer.eth ๐Ÿฆ‡๐Ÿ”Š ๋‹˜์ด ์žฌ๊ฒŒ์‹œํ•จ

With some recent controversies around different entities I did some reflecting and have to say that throughout the years @NethermindEth as a company have stayed extremely aligned with @ethereum and I'm confident it will not change in the future.


smartprogrammer.eth ๐Ÿฆ‡๐Ÿ”Š ๋‹˜์ด ์žฌ๊ฒŒ์‹œํ•จ

My thoughts about the @RelayProtocol, one of the most used (and - IMO - bad) protocols for interop and why I think the Ethereum community should make a strong stance against such designs โš ๏ธโš ๏ธโš ๏ธ ๐Ÿงต


smartprogrammer.eth ๐Ÿฆ‡๐Ÿ”Š ๋‹˜์ด ์žฌ๊ฒŒ์‹œํ•จ

Yooo this is such a cool EIP by @Smartprogrammer and @marchhill1 bringing conditional transactions based on a (slot,index) pair Big plus for encrypted mempools and good mev

Varunx10's tweet image. Yooo this is such a cool EIP by @Smartprogrammer and @marchhill1 bringing conditional transactions based on a (slot,index) pair 

Big plus for encrypted mempools and good mev

smartprogrammer.eth ๐Ÿฆ‡๐Ÿ”Š ๋‹˜์ด ์žฌ๊ฒŒ์‹œํ•จ

Ethereumโ€™s December upgrade expands L1 throughput, improves proposer logic, and stabilizes blob economics. The team at @NethermindEth implemented and co-authored several execution-layer EIPs that define it, from gas accounting to block size limits. โฌ‡๏ธ x.com/ben_a_adams/stโ€ฆ


smartprogrammer.eth ๐Ÿฆ‡๐Ÿ”Š ๋‹˜์ด ์žฌ๊ฒŒ์‹œํ•จ

The Preconfirmation SoK is ready! Everything you needed to know about preconfs, but you were too afraid to ask. The SoK provides a formality & taxonomy to a crucial blockchain subject Edits & additions are encouraged through PRs - we'll check Github regularly Link below๐Ÿ‘‡


smartprogrammer.eth ๐Ÿฆ‡๐Ÿ”Š ๋‹˜์ด ์žฌ๊ฒŒ์‹œํ•จ

The Nethermind Client is on the path to ZK-readiness. ๐Ÿš€ Weโ€™ve already shipped execution witness, stateless replay, minimal binaries, and RISC-V64 compilation. ๐Ÿ“Blog: nethermind.io/blog/road-to-zโ€ฆ

NethermindEth's tweet image. The Nethermind Client is on the path to ZK-readiness. ๐Ÿš€

Weโ€™ve already shipped execution witness, stateless replay, minimal binaries, and RISC-V64 compilation. 

๐Ÿ“Blog: nethermind.io/blog/road-to-zโ€ฆ

The @NethermindEth UI is just ๐Ÿ˜ #ethereum

Smartprogrammer's tweet image. The @NethermindEth  UI is just ๐Ÿ˜ #ethereum

The anticipated Nethermind UI is here. ๐ŸŽ‰ With Nethermind v1.33.1, you can finally try the new dashboard experience for your node. Itโ€™s the initial release, but ready for you to explore and share feedback. Hereโ€™s how to get started ๐Ÿ‘‡ 1/

NethermindEth's tweet image. The anticipated Nethermind UI is here. ๐ŸŽ‰

With Nethermind v1.33.1, you can finally try the new dashboard experience for your node. 

Itโ€™s the initial release, but ready for you to explore and share feedback.

Hereโ€™s how to get started ๐Ÿ‘‡

1/


smartprogrammer.eth ๐Ÿฆ‡๐Ÿ”Š ๋‹˜์ด ์žฌ๊ฒŒ์‹œํ•จ

EIP-2780 eips.ethereum.org/EIPS/eip-2780 with 1.5sec slots and 450MGas blocks (300MGas/s) would take Ethereum to 50k tps for ETH transfers; while staying within block size limit (10MiB/8MiB EL) Using 54Mbit/s bandwidth (only for blocks, not including blobs and tx gossip etc)

ben_a_adams's tweet image. EIP-2780 eips.ethereum.org/EIPS/eip-2780 with 1.5sec slots and 450MGas blocks (300MGas/s) would take Ethereum to 50k tps for ETH transfers; while staying within block size limit (10MiB/8MiB EL)

Using 54Mbit/s bandwidth (only for blocks, not including blobs and tx gossip etc)

The version of "preconfs" (more like mini-blocks at that point) that bypasses this is where a small selection of attesters has to timestamp each one. Though this increases the minimum safe latency somewhat, maybe to 1s. (Yay, slots and epochs are back! sort of)



smartprogrammer.eth ๐Ÿฆ‡๐Ÿ”Š ๋‹˜์ด ์žฌ๊ฒŒ์‹œํ•จ

Meet @ben_a_adams , the third most prolific contributor to the @NethermindEth codebase. This is his story about how he became an #Ethereum core developer.


Based #ethereum

The Based Rollup Market Map: A map of 50+ projects leading Ethereum's based future.

therollupco's tweet image. The Based Rollup Market Map:

A map of 50+ projects leading Ethereum's based future.


Few realize this. #ethereum will become ulta sound money MAX :p jokes aside, fusaka fork also increases the burn by increasing the blob basefee that gets fully burnt ๐Ÿ”ฅ

When fitting twice as many transaction into a block, the burn can stay constant at half the fees, or the burn can double at constant fees. By scaling Ethereum's gas limit by, e.g., 10x, fees can go down significantly while the fee burn actually goes up.



smartprogrammer.eth ๐Ÿฆ‡๐Ÿ”Š ๋‹˜์ด ์žฌ๊ฒŒ์‹œํ•จ

Blocks are big & monolithic: they must be fully downloaded + decompressed before execution, making validation sequential & latency-heavy. My latest post explores Payload Chunking - splitting blocks into parallelizable chunks for streaming validation. ๐Ÿ”— ethresear.ch/t/23008


smartprogrammer.eth ๐Ÿฆ‡๐Ÿ”Š ๋‹˜์ด ์žฌ๊ฒŒ์‹œํ•จ

The most robust Ethereum client just got faster and easier to use. Whatโ€™s inside v1.33.0: ยท New UI for real-time visibility ยท Experimental pruning for disk growth ยท Stronger OP Stack peering ยท Major performance gains ๐Ÿ“– Blog: nethermind.io/blog/netherminโ€ฆ ๐Ÿ’ปRelease notes:โ€ฆ

NethermindEth's tweet image. The most robust Ethereum client just got faster and easier to use.

Whatโ€™s inside v1.33.0:

ยท New UI for real-time visibility
ยท Experimental pruning for disk growth
ยท Stronger OP Stack peering
ยท Major performance gains

๐Ÿ“– Blog: nethermind.io/blog/netherminโ€ฆ
๐Ÿ’ปRelease notes:โ€ฆ

smartprogrammer.eth ๐Ÿฆ‡๐Ÿ”Š ๋‹˜์ด ์žฌ๊ฒŒ์‹œํ•จ

1/ This is a @base node running on an ARM64 board. - 1 op @nethermindeth client - 1 op node client Snap synced, it runs the @Optimism stack on 1 node connected to an external L1 node (Rock 5B). - HW: OrangePi 5 32 GB RAM+CTP3 4TB - Sync time: 14h (1st phase) - DB size: 2 TB

EthereumOnARM's tweet image. 1/ This is a @base node running on an ARM64 board.

- 1 op @nethermindeth client
- 1 op node client

Snap synced, it runs the @Optimism stack on 1 node connected to an external L1 node (Rock 5B).

- HW: OrangePi 5 32 GB RAM+CTP3 4TB
- Sync time: 14h (1st phase)
- DB size: 2 TB

smartprogrammer.eth ๐Ÿฆ‡๐Ÿ”Š ๋‹˜์ด ์žฌ๊ฒŒ์‹œํ•จ

clearly the ethereum commmunity has voted ethereum dont need r1 and the refund process will begin in 4 days.

ethereumR1's tweet image. clearly the ethereum commmunity has voted

ethereum dont need r1 and the refund process will begin in 4 days.

smartprogrammer.eth ๐Ÿฆ‡๐Ÿ”Š ๋‹˜์ด ์žฌ๊ฒŒ์‹œํ•จ

We drop pre-merge history, which saves ~320 GB on the Ethereum node. With live historical pruning, you no longer need to resync the node to achieve this. Dropping post-merge history is next. Thereโ€™s still around 500 GB of history on your node.

Nethermind client v1.33.0 Release Candidate is out and ready for testing ๐Ÿš€ Highlights: ยท New UI (initial release) ยท Live pruning for historical data ยท OP Stack peering improvements ยท Performance upgrades ยท Non-blocking state pruning ๐Ÿ”— github.com/NethermindEth/โ€ฆ

NethermindEth's tweet image. Nethermind client v1.33.0 Release Candidate is out and ready for testing ๐Ÿš€

Highlights:
ยท New UI (initial release)
ยท Live pruning for historical data
ยท OP Stack peering improvements
ยท Performance upgrades
ยท Non-blocking state pruning

๐Ÿ”— github.com/NethermindEth/โ€ฆ


smartprogrammer.eth ๐Ÿฆ‡๐Ÿ”Š ๋‹˜์ด ์žฌ๊ฒŒ์‹œํ•จ

I put together an amendment to EIP-7732 which removes optionality but preserves the pipelining benefits of the original 7732 design. Article link explaining the amendment below ๐Ÿ‘‡

ConorMcMenamin9's tweet image. I put together an amendment to EIP-7732 which removes optionality but preserves the pipelining benefits of the original 7732 design. 

Article link explaining the amendment below ๐Ÿ‘‡

Loading...

Something went wrong.


Something went wrong.