NC retweeted
Lodestar's state transition just got a whole lot faster.
We recently hot-swapped our state transition in Lodestar. It was originally written in TypeScript, and now runs with Zig. On a mainnet replay of about 16 epochs (492 blocks, epoch boundary blocks excluded), state transition is now 4.6x faster than before:
NC retweeted
It’s not a question coz the answer’s YES
on.soundcloud.com/SlcqdoFqg9…
NC retweeted
Our next chapter: Transitioning from a pure JS client focused on browser compatibility to a performance-first, hybrid @JavaScript + @ziglang architecture.
TL;DR: We're rewriting core modules in Zig and switching to @bunjavascript as our primary runtime:
blog.chainsafe.io/lodestar-z…
NC retweeted
the eth core devs don’t tweet a lot about just how hard the work that they do is so let’s talk about it:
1. every line of code they merge can move more money than most banks process in a quarter. there is no staging server for that.
2. they swap consensus logic for a 400B + dollar economy without scheduling downtime. ever.
3. they coordinate hundreds of researchers, auditors, and client teams across time zones, cultures, and philosophies, yet ship like a single mind.
4. they do it all in public, with every decision dissected by the loudest peanut gallery on the internet, and still keep the vibe collaborative.
5. they design for attackers who have nine figure incentives and infinite patience. then they sleep anyway.
6. they keep six independent clients in perfect sync so the same block lives at the same height for every node in the world.
7. they turn bleeding edge research into production code while preserving backwards compatibility for machines that went online before defi even had a name.
8. they debug issues that only happen once a year on a single archive node because someone somewhere will rely on that edge case.
9. they write cryptography that must stay unbroken for decades while the math itself evolves beneath their feet.
10.when the upgrade lands smooth the outside world shrugs. inside ethereum we know it was a minor miracle. every successful fork proves that decentralized coordination can outperform the world’s best hierarchies and shows that open internet capital markets are now the default.
thank you, truly.
we owe you everything.
NC retweeted
Let there be Prysm <> Lodestar FOCIL interop.
Kudos for @terencechain @ensi321 @nicoflaig @parithosh_j @_pk910_ 🎉🎉🎉
NC retweeted
We all know the risks of developing web3 using web2 tooling. Although we seemingly aren't ready to just start developing web3 on web3 yet, we expose ourselves to these kinds of risks. Any devs, including core devs, are still privy to the ToS of an US company, who can cancel you.
Does anyone know someone at @github ?
One of our engineers got their account suspended for an unknown reason. It removed all outstanding PRs and issues which create a considerable setback for the team.
Simply looking for the reason for the ban as a starting point 🙏
NC retweeted
🔧Exciting news, I've undergone an upgrade!
Big thanks to @mikeneuder, @icebearhww, and the @EthResearch team for providing me with a new integration path.
Moving forward, I'll exclusively share recently created posts and won't repost older topics with new comments. 🔗
NC retweeted
Staking with geth carries SIGNIFICANTLY higher risks than running any other execution client! Not just for the network but for YOUR STAKE: 🧵
I'm glad to see this post from @dankrad getting attention again:
dankradfeist.de/ethereum/202…
but every time I have this discussion I get the same response from geth stakers that must be addressed:
(0/9)
NC retweeted
Here's an overview of everything that's been proposed (so far) for Prague/Electra 👀
See the full thread on @EthMagicians 🧙♀️
ethereum-magicians.org/t/pra…
NC retweeted
I've always admired @0xdoug's passion for DeFi and his thoughtful remarks about our industry. But I must say that his recent take is off the mark.
Shorter block time is not simple. It inherently involves a tradeoff between network synchrony assumptions and protocol security [1,2].
Given the same synchrony assumption, you lose security when you have a shorter block time. If you decrease block time, you must also increase network synchrony requirements to maintain the same security. If not, various types of balancing attacks could occur on the base layer [3,4].
Moreover, important elements such as ePBS (in protocol builders), inclusion list (for censorship resistance), single slot finality (improving UIUX and security), and secret leader election (enhancing security) typically require extended block time for implementation. This is due to the need for an additional round of observation and communication.
Lastly, desirable features, such as making Ethereum provably secure (Goldfish [5,6]), also need an extra round of communication.
This goes into the next point which is why not just make Ethereum mainnet more application friendly? It is becoming more friendly, just look at the upcoming upgrade here:
Now what about increasing the gas limit? I think it would be great for mainnet dApps and maybe also L2s, but once again making blocks bigger -> increases the network synchrony assumptions and also increases the mainnet state bloat problem - two problems that are at the heart of any distributed system design.
Even from a practical standpoint: what good does it do to increase gas from 30 million to 300 million / block today? Does it make Ethereum more long-term competitive against other layers? I do not see how that's the case. 120 TPS is still too small.
Lastly, the vision for Ethereum has always been rollup-centric. As @hasufl pointed out, the primary purpose of the base layer is to ensure security. Additionally, the base layer will offer the asset $ETH itself. Maybe there are some great arguments against this direction but I have not heard a nuanced case against it.
On a personal note, for most of my conversations with EF and EF-adjacent folks, block time has always been a discussion topic, especially around MEV. I do not know where this refusal to discuss comes from.
Ultimately, this might be how a functioning decentralized protocol works. We see the same situation from various perspectives and eventually strive to find mutual ground to continue forward❤️
Happy holidays🥰
Notes:
1: Everything is a Race and Nakamoto Always Wins arxiv.org/pdf/2005.10484.pdf
2: Chapter 7: ee374.stanford.edu/blockchai…
3:Two Attacks On Proof-of-Stake arxiv.org/pdf/2203.01315.pdf
4: Three Attacks on Proof-of-Stake Ethereum arxiv.org/pdf/2110.10086.pdf
5: Goldfish: No More Attacks on Proof-of-Stake Ethereum arxiv.org/pdf/2209.03255.pdf
6: Goldfish: A Provably Secure Replacement for LMD GHOST in PoS Ethereum paradigm.xyz/2022/09/goldfis…
NC retweeted
a small christmas present 🎁 for cryptotwitter – we are ecstatic to share "Execution Tickets," an idea from @drakefjustin on a reimagined blockspace market!
dive into the design + implications here↓
👽🎟️ ethresear.ch/t/execution-tic…
thanks for reading, and see you next year🎄🪩🎉
As a CL client contributor, I often need to refer to eth2book by Ben Edgington for details of the Ethereum protocol.
I have built a chatGPT on top of Ben's book and now it can answer CL related questions half-decently. See below for its responses.
chat.openai.com/g/g-vVXIlaDY…
1/
1
1
82
For something that is more ambiguous, or not on its knowledge source (eth2book), it either guesses or fall back to its default knowledge source. Notice it doesn't know EIP-6914 but 4844. Maybe the former is too new?
3/
1
50
NC retweeted
We love hearing that users enjoy using Lodestar 🌟 It's all about creating a user-friendly and efficient experience!
#StakeFromHome. Support client diversity. Run Lodestar 🤝

























