Studying Geth? Let’s go🚀✈️✈️ #Ethereum #Geth #Blockchain NeverSettle🧐

There are a thousand ways to tell the story of Devcon. We want to see yours 🤳 Introducing the Devcon 8 Creator Fellowship: 10 creators will join us in the lead-up to Mumbai to make stories that spark curiosity, explain big ideas, and bring new people into the Devcon experience. No single format. No single style. Just your creative lens. Selected Fellows receive one free Devcon ticket, exclusive perks, recognition across Devcon channels, and more. Applications are open now through September 20 ↓

To the winners, the glory 🏆 These 5 built on [ ARKIV ] and won Let's explore their use cases 👀 📅 Sept 17 - Thurs · 4pm CET 🎙️ Link in comments 👇 Join @lawesbio @neromtoobad @MR_DY0R_Of_Web3 @0xkiddok @IamHarrie with @defi_hera

UHI10 Hookathon results are in! Congratulations to these devs for winning the @UniswapFND theme prize 👏 UHI10: • Hindsight: @_OoJae • Assay: @RattiPrazwal • IRF: @raymondintell • QUEUE: @0xmishoko • Walras: @Debielily • Lachesis: @0xmaues • ILAL: @ronny_hz727 Alumni: • HYDRA: @jmakwana_0x1 • Poincaré: @Prakhar_3010 • Markout: @0xshreyaas • Wick: @Big14teru And congrats to these devs for winning the general prize 👏 • AML Hook • Orbital: @0xkai_1 • BondMeBro: @Zeroknowledge_0, @pran40798

🔥 🔥 congratulations brother. We move

And just... Like... That... Try it out: book.pyde.network/otigen/ins…

The most expensive bug in AI infra isn't a crash it's the GPU that keeps running after the crash. Shared Compute Lease Board: leases that die when the agent dies. Now shipping it Built on @arkivnetwork @SantiagoDevRel

One positive consequence of all the recent detailed thinking about transaction formats - not just 8141, also "future of state" discussions eg. UTXOs, PBT, keyed nonces, and also recursive STARK mempool - is that we have a much more explicit understanding of how transactions have "actions" and "dependencies", and we can engineer around optimizing the two separately. An action is an effect that a transaction has. A dependency is a fact about the transaction and/or the state that must be true for the transaction to be valid. eg. a signature is a dependency, a Merkle proof of a UTXO is a dependency, a ZK-SNARK (or STARK) is a dependency, a call that sends ETH is an action Dependencies can be processed in parallel. Dependencies that involve state can be reasoned about by a mempool, especially if the specific state accessed is statically declared. Dependencies that are pure (no state calling allowed) can be processed once at the mempool layer and never need to be processed again - and potentially even replaced with a STARK verifying them, allowing not just execution but also data to be elided. In principle, dependencies and actions can all be expressed as calls (if needed, calls to precompiles). This would make the transaction format itself very bare-bones and minimalist (a list of calls, flags for the type of each call eg. dependencies would be static or pure calls, and origin, nonce, etc) and allows maximum cross-compatibility even if different EVM chains have different features. In 2015-era Ethereum, thinking explicitly about these differences was not very important: execution was execution, there were few enough transactions that we could process them all serially, and single-key ECDSA accounts were good enough for everyone. Ethereum's current scaling strategy, however, requires moving beyond that paradigm. Ethereum is beloved by many developers because the execution and state model is so dynamic and flexible. But dynamic and flexible is not friendly to scaling. Fortunately, >90% of Ethereum's activity by volume does not require anything dynamic and flexible. So, we require contracts, accounts and transactions to more explicitly specify what is dynamic and flexible and what is more statically-analyzable but more restrictive, and more statically-analyzable things get the lowest gas cost and thus scale the most. Effectively, learning from the best of both the 2015-era Ethereum model and a more Bitcoin-like model (reminder: Bitcoin has had what I call account abstraction since the beginning), and making a mixture of both (really, the full spectrum between both) available, with gas costs appropriate for the level of scale involved. New state types, the recursive STARK mempool, keyed nonces, etc all go in this direction. This all relates to transaction types, because a general-purpose transaction type is a very natural interface layer on top of which all of this can be implemented, and the current thinking around the EIP-8141 transaction type is going in this exact direction that is friendly to these kinds of future generalizations. So in that sense, 8141 done well is not just a culmination of 10 years of account abstraction work, it's also preparation for the next few years of responsible decentralization-friendly hyper-scaling.

FairRail has officially been submitted. my take on Sustainable Liquidity & MEV Protection on Uniswap v4: ⚡ Match compatible intents before they hit the AMM ⚡ Auction residual MEV competitively Match privately. Auction MEV. Reward LPs. @Uniswap @AtriumAcademy Fingers crossed 🤞

Building web3 communities since 2022… Thank you guys for showing up🧡

From an idea to a win 🏆 Shared Compute Lease Board @arkivnetwork's Ideathon. This one means a lot Now, we build. Shared Compute Lease Board, chapter two starts now @arkivnetwork @SantiagoDevRel

NeverSettl @blockfuselabs ✈️ ✨️

This toast goes to the engineers and mentors of Blockfuse Labs. 🥂 The builders who generously share their knowledge, challenge us to grow, and turn curiosity into competence. In just two years, your time, patience, and commitment have shaped not only developers but the culture of this community. Thank you for showing up, pouring into others, and helping Blockfuse Labs become what it is today. We see you. We appreciate you. 🤍

Some of the world’s most important blockchain infrastructure is being built by Africans. It’s time we talked about it. We’re thrilled to welcome @devlongs_ Ethereum Protocol Engineer at Gean Labs, to the #W3LC5 stage. This isn’t just another Ethereum talk. It’s a conversation about building the technology that powers the ecosystem, from Africa, for the world. 📍August 28th–29th Glover Memorial Hall, CMS Lagos 🎟️ event.web3bridge.com #W3LC5 #Ethereum #Web3Lagos #Conversations

SHA256 arithmetization just merged in Plonky3 👇 github.com/Plonky3/Plonky3/p…

RT @go_ethereum: 🚀 Geth v1.17.5 has been released! This release brings Pebble v2 support, performance improvements, and continued progress…

With Flock and the recent progress around binary fields, development of Binius64 is moving quickly. If you haven't looked at it yet, it's definitely worth checking out. github.com/binius-zk/binius6…