English
Barnabé Monnot | barnabé.eth
Report

Barnabé Monnot | barnabé.eth✓

@barnabemonnot

Growing @ethereum and ETH @ethlabs_org | Former co-lead Protocol @ethereumfndn

2K Following13.8K Followers6.4K Posts
  1. Barnabé Monnot | barnabé.eth✓@barnabemonnot
    Update: One step closer to a faster Ethereum L1. Quick slots just moved to Considered for Inclusion (CFI) in today's All Core Devs call! This is a new milestone for our proposal to make Ethereum blocks faster 🎉 Btw.. Faster blocks => - Better UX - Better markets - Faster finality and fast confirmation rule - And improved censorship-resistance too! TLDR: More value for the network, its users, and ETH, without compromising on the core values and properties of Ethereum. Hear this from 20 top Ethereum teams in our ecosystem survey: --- Ok, what does CFI mean? This does not mean that the EIP is for sure included in Hegotá. This means that now it will be considered more seriously, including testing, towards inclusion in future devnets once headliners (FOCIL and frame transactions) are stable. In particular, the call today revealed the appetite for a phased approach, installing the plumbing which allows us to reduce the slot time in Ethereum clients, and deciding to pull the trigger based on further testing. Ultimately, this is how EIP-8198 is designed, so CFI'ing today allows us to move forward with more of the plumbing work, and start looking into testing towards an actual slot reduction from 12 to 10 seconds. This is a first reduction, as EIP-8198 opens the door for progressively lower slot times, as they get sufficiently safe to ship. In parallel, as discussed on the call too, we are continuing our ecosystem survey and outreach of deployed smart contracts with a slot time dependency. We have reached out to more teams on this. --- Faster slots are one important dimension of our Faster Ethereum body of work. A more responsive network helps cement its role as a liquidity hub and as the heartbeat of the network as a whole. Along with our work on fast finality, fast confirmation rule and fast interop, it all combines for a seamless and secure flow of assets everywhere on the network. Thank you to the many builders who are taking us there!
    214825422.4K
  2. Barnabé Monnot | barnabé.eth✓@barnabemonnot
    "Ethereum lists" is one of these key pieces of infrastructure that is not well-known but deserves more attention, more so in the multi-chain world with Ethereum at the centre. We'll discuss upgrading the repo to an onchain registry and streamlining its operations. Join us!
    Download
    ligi 🎶🚲🧉🫖☮️🌍🌳🍵🌶🔥🖖 @mr_ligi
    I want to have a conversation about moving @EthereumLists away (likely on chain) from github at @EFDevcon Tentative to happen 4.11. 18:00 Already have a couple of people in mind who should be on the table - please drop here who you think would be beneficial for this conversation
    35411.5K
  4. Barnabé Monnot | barnabé.eth✓@barnabemonnot
    fwiw, and despite having been warmer on the idea in the past, I also oppose a dev tax all public Ethereum orgs, including ours, should have high accountability, and loosening the budget constraint doesn’t help make hard choices this is a key moment in Ethereum’s existence, with AI capabilities increasing by the day, and a serious shot at making ETH the best programmable store of value for the world everything will change around us, let’s embrace it and see what the future holds, before subscribing to a costly, course-altering insurance
    gabriel shapiro @lex_node
    @lightclients @BlockEnthusiast @wmougayar sorry but I will die on this hill, quite simply if Ethereum "needs" a dev tax to me that means ETH is dead as an investable asset, I sell all my ETH and move on might keep using Ethereum but ETH could probably go to $10 or something and it works fine
    481033.8K
  5. gabriel shapiro✓@lex_node
    Posts @lightclients
    @lightclients @BlockEnthusiast @wmougayar sorry but I will die on this hill, quite simply if Ethereum "needs" a dev tax to me that means ETH is dead as an investable asset, I sell all my ETH and move on might keep using Ethereum but ETH could probably go to $10 or something and it works fine
    113718.1K
  6. Barnabé Monnot | barnabé.eth✓@barnabemonnot
    Barnabé Monnot | barnabé.eth
    RT @fradamt: What a week (and not over yet)! Currently taking an unscheduled break from decoupled consensus to help get some clarity on the app layer impact of 8037/8038. In the process, we are learning how to summon agent swarms and point them towards our problems.
    Derek Chiang | Ethlabs @decentrek
    060132
  9. Barnabé Monnot | barnabé.eth✓@barnabemonnot
    Busy weekend letting loose our agents on gas repricings and mechanism changes. Read on for more colour on what's going on!
    Derek Chiang | Ethlabs @decentrek
    64571.9K
  10. Barnabé Monnot | barnabé.eth✓@barnabemonnot
    You’ve already seen a couple formally-verified products of Ethereum protocol development, including the Fast Confirmation Rule and fast finality by @fradamt This library should support more of these projects and act as a registry of mathematically known properties of Ethereum
    Thomas Coratger @tcoratger
    This weekend we launched EthLib, a Lean4 library for Ethereum! The goal is to bring Ethereum's primitives, specifications and theorems into one place, building a shared foundation for formally specifying and proving things about Ethereum.
    45421.7K
  11. Thomas Coratger@tcoratger
    This weekend we launched EthLib, a Lean4 library for Ethereum! The goal is to bring Ethereum's primitives, specifications and theorems into one place, building a shared foundation for formally specifying and proving things about Ethereum.
    155530712.7K
  13. Barnabé Monnot | barnabé.eth✓@barnabemonnot
    Another day, another bridge 🫨 From my perspective these developments are mostly good, the market is pushing latency and costs down, and this is the result of clear demand for crosschain operations. The multi-chain world is undeniable. On us to ensure that Ethereum's security and liquidity are the easiest, cheapest and fastest to export, so Ethereum users and assets reap the benefits of broader use cases and distribution.
    Download
    fomo @fomo
    Introducing the fastest crosschain swaps on the market. Crosschain transactions on @fomo now land in <1s. A week ago, we rolled out our own internal bridge to a small % of users. Public rollout of fomo bridge begins now.
    144702.7K
  14. fomo@fomo
    Introducing the fastest crosschain swaps on the market. Crosschain transactions on @fomo now land in <1s. A week ago, we rolled out our own internal bridge to a small % of users. Public rollout of fomo bridge begins now.
    Download
    4283862K356K
  16. Barnabé Monnot | barnabé.eth✓@barnabemonnot
    Barnabé Monnot | barnabé.eth
    RT @ox_shaman: Next year will be such a breakthrough for Ethereum UX and security that it's hard to put into a single tweet all the benefits we'll get. Key rotation, native multisigs, huge security advances via transaction assertions, native post quantum signing schemes, ...
    0290152
  17. Barnabé Monnot | barnabé.eth✓@barnabemonnot
    It's not happening (yet) :( This is the price of securely scaling: issues must be fixed before we can move forward. Another bump in the long road to Glamsterdam. But boy when it'll hit..
    nixo.eth @nixorokish
    if you run a hoodi validator, you'll want to roll back your version: the glamsterdam hoodi fork has been delayed due to some issues that require investigation
    101672.3K
  18. nixo.eth✓@nixorokish
    if you run a hoodi validator, you'll want to roll back your version: the glamsterdam hoodi fork has been delayed due to some issues that require investigation
    616657.7K
  21. Barnabé Monnot | barnabé.eth✓@barnabemonnot
    Very cool to see the deployment of @aeroxyz across seven networks including Ethereum L1 and major L2s. I was lucky to chat with the team a couple times over the last year, and it's clear their instinct is to build the right way, leveraging onchain capabilities to remove dependencies. Hoping to continue this discussion to inform our own work on making crosschain a secure and delightful {developer, user} experience!
    Aero @aeroxyz
    Aero is here 🌤️ Get on board at
    512873.4K
  22. Aero✓@aeroxyz
    Aero is here 🌤️ Get on board at
    Download
    10699859153K
  23. Barnabé Monnot | barnabé.eth✓@barnabemonnot
    I’m in favour of this change. Locking on the highest bid is myopically rational for the validator, but using the latest bid induces the better market. There are many pieces of code in the validator client that are there not because the validator benefits (in fact, it may cost them) but because client code is the best approximation we have to enforce norms that are not observable by the protocol. This is one of them. (Yes this is a nod to an old piece ;)
    Blockspace Forum @blockspaceforum
    As part of Gloas, clients are considering adding the option to select the highest bid per builder per slot instead of last. We strongly advocate for not providing this option & encourage proposers & responsible builders to also advocate for this position.
    46411.6K
  24. Blockspace Forum✓@blockspaceforum
    As part of Gloas, clients are considering adding the option to select the highest bid per builder per slot instead of last. We strongly advocate for not providing this option & encourage proposers & responsible builders to also advocate for this position.
    14223.8K
  25. Barnabé Monnot | barnabé.eth✓@barnabemonnot
    Can you feel the acceleration anon? Just to give a sense of what's going on: - The drafts of two key EIPs for I* were published in the last 24h: a new consensus mechanism, and the ability for validators to switch their signatures to post-quantum-secure ones. - H*/Hegotá scoping and early devnets progressing well too. - Research for fully quantum-resistant consensus by J* also moving at a good clip, looking into pulling forward timelines even more. Challenges along the way for sure, but I don't think I've seen stronger multi-fork planning and pipelining until this.
    Barnabé Monnot | barnabé.eth @barnabemonnot
    712985K
  26. Barnabé Monnot | barnabé.eth✓@barnabemonnot
    Download
    Thomas Coratger @tcoratger
    We published the first draft of EIP-8450 this week, introducing a post-quantum public key registry for Ethereum consensus validators! Highly work in progress! Discussion is now open, and we'd love your feedback!
    23303.6K
  27. Barnabé Monnot | barnabé.eth✓@barnabemonnot
    Posts @barnabemonnot
    oh s*** there's more!!
    CPerezz.(gwei/eth) ⟠ 🦀 @CPerezz19
    It's happening!🚨🚨🚨 The next @ethereum's tree Partitioned Binary Tree is finally here! And we're migrating to it! We are doing the first tree & DB migration in the Glamsterdam-devnet-8 with @go_ethereum @Nethermind @Besu_eth @ErigonEth This is gonna be huge! Ready for I*🎉
    008424
  29. Barnabé Monnot | barnabé.eth✓@barnabemonnot
    Would love more technical details on the bridge, any docs published yet?
    alon @a1lon9
    12181.5K
  30. alon✓@a1lon9
    4631351.4K298K
  32. Barnabé Monnot | barnabé.eth✓@barnabemonnot
    Download
    ethresearchbot @ethresearchbot
    New EIP! Decoupled Consensus 🔗 Highlights: - Validators would send two different message types: head votes for the available chain and finality attestations for the finality gadget, with separate propagation and inclusion rules. - Fork choice for the available chain uses only recent head votes (with cutoffs) plus expiring lock mechanisms to protect recently confirmed blocks when participation drops or messages are missing. - Finality would move off epoch-coupled voting: the whole validator set participates in independently scheduled finality rounds, and blocks can be justified/finalized as soon as ≥2/3 stake attestations are included in blocks. - The two subsystems interact through a “frame” provided by the finality gadget that constrains which blocks the available chain may build on and vote for (viable tree/heads, fork-choice root, frontier height handling). - It requires a consensus-layer hard fork and leaves major parameters and analysis as TBD (committee selection/VRFs, timing/lock parameters, encoding/aggregation, incentives, slashing details, fork transition, and proving the targeted ~4× faster finality). ELI5: Today Ethereum uses the same kind of vote messages to both (1) pick which block is the “current head” and (2) decide when blocks are “final” and can’t be changed. This proposal splits those into two separate jobs: a smaller, fast group votes each slot to quickly pick and “confirm” the head (with safety locks if votes are missing), while the whole validator set votes in separate, independent rounds to finalize blocks much faster. Keeping these two voting systems separate is meant to make chain reorganizations harder and let finality happen sooner.
    32733.6K
  33. Thomas Coratger@tcoratger
    We published the first draft of EIP-8450 this week, introducing a post-quantum public key registry for Ethereum consensus validators! Highly work in progress! Discussion is now open, and we'd love your feedback!
    6271214.8K
  34. ethresearchbot✓@ethresearchbot
    New EIP! Decoupled Consensus 🔗 Highlights: - Validators would send two different message types: head votes for the available chain and finality attestations for the finality gadget, with separate propagation and inclusion rules. - Fork choice for the available chain uses only recent head votes (with cutoffs) plus expiring lock mechanisms to protect recently confirmed blocks when participation drops or messages are missing. - Finality would move off epoch-coupled voting: the whole validator set participates in independently scheduled finality rounds, and blocks can be justified/finalized as soon as ≥2/3 stake attestations are included in blocks. - The two subsystems interact through a “frame” provided by the finality gadget that constrains which blocks the available chain may build on and vote for (viable tree/heads, fork-choice root, frontier height handling). - It requires a consensus-layer hard fork and leaves major parameters and analysis as TBD (committee selection/VRFs, timing/lock parameters, encoding/aggregation, incentives, slashing details, fork transition, and proving the targeted ~4× faster finality). ELI5: Today Ethereum uses the same kind of vote messages to both (1) pick which block is the “current head” and (2) decide when blocks are “final” and can’t be changed. This proposal splits those into two separate jobs: a smaller, fast group votes each slot to quickly pick and “confirm” the head (with safety locks if votes are missing), while the whole validator set votes in separate, independent rounds to finalize blocks much faster. Keeping these two voting systems separate is meant to make chain reorganizations harder and let finality happen sooner.
    310544.5K
  35. Show more posts