Connecting Ethereum with Enterprise. 🌐 Check out this post by @poojaranjan19 sharing her experience in the room with @EntEthAlliance - bridging Ethereum’s protocol development with enterprise understanding and adoption.

Ethereum Matrix intelligence.entethalliance.… in the continuity of the great work of @EIPsInsight this is a tool to translate Ethereum technical changes into products impacts for financial institutions. Send that to product managers.

EIPs, network upgrades, and devnets move fast, but how do enterprises figure out what actually impacts their stack? I wrote about taking Ethereum’s protocol process into the enterprise room with @EntEthAlliance, shaped through discussions with @RedoudouM, and why bridging this communication gap matters for both developers and institutions. 📖 Read the full story on @ether_world: etherworld.co/taking-ethereu… #Ethereum #Enterprise #Blockchain #TechLeadership #EEA #EIP #ERC

Ethereum’s roadmap moved forward this week. Glamsterdam Sepolia is locked for Oct 6, Hegotá’s scope is narrowing, EIP 8363 heads toward wider community discussion & Ethereum’s enterprise story is expanding. Here’s what mattered this week 👇 #Ethereum #ETH #Web3 #Crypto

🔐 Who gets to hold the keys to Ethereum's encrypted mempool? Validators might soon vote on it. Encrypt The Mempool #10: → Validators may soon allowlist trusted key publishers by vote, through an execution-layer contract where an address needs 50% of total effective balance to be accepted (delegation included). → Top-of-block ordering would prioritize allowlisted publishers, lowering market-entry barriers while letting newcomers earn before they hit the 50% threshold. → Threshold encryption and post-quantum requirements are parked until the crypto matures - the focus is now Lucid's optionality problem, with a key publisher revealing keys after commit. → Cadence moves to monthly, and Jannik is opening a PR to EIP-8184 to fold in the allowlist mechanism. 🔗 eipsinsight.com/calls/etm/10 #Ethereum #EncryptTheMempool #Lucid #MEV @drakefjustin @weboftrees @encryptmempool

50 websites that feel like the internet’s hidden toolbox 🧰 1. unpaywall.org — Free research papers 2. openlibrary.org — Borrow books online 3. doaj.org — Free academic journals 4. alternativeto.net — App alternatives 5. justwatch.com — Find where to stream 6. archive.org — Internet archives 7. gutenberg.org — 70K+ free books 8. openstax.org — Free textbooks 9. openculture.com — Free courses 10. wolframalpha.com — Solve complex problems 11. photopea.com — Photoshop alternative 12. squoosh.app — Compress images 13. remove.bg — Remove backgrounds 14. cleanup.pictures — Remove objects 15. unscreen.com — Remove video backgrounds 16. carbon.now.sh — Beautiful code images 17. ray.so — Code screenshots 18. shots.so — Product mockups 19. smartmockups.com — Create mockups 20. haveibeenpwned.com — Check data breaches 21. virustotal.com — Scan files & URLs 22. privnote.com — Self-destructing notes 23. temp-mail.org — Temporary email 24. file.io — Temporary file sharing 25. archive.ph — Save webpages 26. similarsites.com — Find similar websites 27. radio.garden — Explore global radio 28. everynoise.com — Discover music genres 29. tunefind.com — Find songs from shows 30. musicforprogramming.net — Focus music 31. mynoise.net — Custom background sounds 32. coffitivity.com — Café ambience 33. elicit.org — Research assistant 34. consensus.app — Research-backed answers 35. connectedpapers.com — Research connections 36. semanticscholar.org — Academic search 37. scispace.com — Understand research papers 38. summarize.tech — YouTube summaries 39. phind.com — AI for developers 40. regex101.com — Test regex 41. codebeautify.org — Format code 42. jsonformatter.org — Format JSON 43. explainshell.com — Understand terminal commands 44. raindrop.io — Bookmark manager 45. downdetector.com — Check outages 46. tineye.com — Reverse image search 47. fast.com — Internet speed test 48. smallpdf.com — PDF tools 49. ilovepdf.com — Merge/split PDFs 50. 10minutemail.com — Temporary email Save this. You’ll definitely need some of these later. 🔖 Follow @nikola_mr64990 for more useful websites, AI tools & tech resources.

‼️ BREAKING: Revolut handed over customers’ passport copies, verification selfies and full transaction histories to a malicious actor. The actor sent lawful government information-demand emails using a genuine government domain that passed domain authentication. Revolut later concluded they were not authentic. Affected customers were notified on Friday. What may have been disclosed ranges from name, date of birth and home address to account statements, withdrawal records and complete Bitcoin transaction history. The company says it has alerted the agency to the unauthorised mailbox on its domain, blocked the address and begun notifying regulators. It has not named the agency, explained how someone obtained a mailbox there, or given a number of affected customers. ZachXBT, who circulated the notices, believes the incident was limited in size and aimed at high-net-worth users.

Glamsterdam testing is moving fast, and a few things just got settled. → EIP-8253 is heading to Hegota, with rough consensus that it’s too late for Glamsterdam. → EIP-8037’s SELFDESTRUCT state-gas refill stays declined, reaffirming the ACDT #94 decision. → Hive will be used for the new EL reorg testing suite. → Column gossip limits will be derived from the largest blob schedule value instead of a static ~8 MB cap. → DevNet-11 is targeting mid-to-late week, pending the Prysm alpha.14 merge. Full updates from AllCoreDevs Testing #095 + CL Breakout #095: 🔗 eipsinsight.com/calls/acdt/0… 🔗 eipsinsight.com/calls/acdtcl… #Ethereum #Glamsterdam #DevNet

We’re also playing our part in making Ethereum’s coordination easier to follow. Track All Core Devs calls, breakout discussions & key decisions in one place on @EIPsInsight 👇 eipsinsight.com/calls

New EIP! Fast Execution Payload Broadcast 🔗 github.com/ethereum/EIPs/pul… Highlights: - Replaces the single `execution_payload` gossip message (from EIP-7732) with a new `execution_payload_chunks` topic that broadcasts the payload envelope in 64 independently verifiable chunks. - The builder commits at bid time to the full set of chunks using a Merkle root (`payload_chunks_root`) included in the signed `ExecutionPayloadBid`, enabling per-chunk verification via inclusion proofs after one bid signature verification. - Chunking reduces propagation latency and bandwidth waste by (a) avoiding large duplicate in-flight transfers and (b) allowing pipelined forwarding—nodes can relay chunks immediately instead of waiting for the full payload per hop. - `beacon_block_root` is removed from the committed envelope (because it’s unknown when bidding) and is instead included in each `PayloadChunk`; validators must explicitly bind chunks to a known block whose bid contains the matching `payload_chunks_root`. - This is a breaking networking change (requires a fork): the old `execution_payload` topic is deprecated/removed; future extensions may add erasure coding or apply the same chunked scheme to other large data (e.g., BAL messages). ELI5: Ethereum blocks contain a big “package” of execution data that everyone needs quickly. If the package is sent as one huge file, it’s slow to relay and wastes bandwidth when duplicates arrive. This proposal says: split the package into 64 smaller pieces, let nodes forward pieces immediately as they arrive, and attach a simple “fingerprint” (a Merkle root) so each piece can be checked as real. This helps everyone get the full package before important deadlines.

How would you most like to contribute to Ethereum?

What a week in crypto. 🚨 Ethereum delayed Glamsterdam’s Sepolia activation, DeFi suffered fresh exploits, regulators moved closer to onchain markets & institutional adoption continued expanding. Here’s everything you may have missed 🧵 #Ethereum #Crypto #Web3 #Blockchain #CryptoNews

Happy Janmashtami 🧡🪈 “Set your heart upon your work, but never its reward.” A timeless reminder from Krishna that feels especially relevant to those who build. In Web3, we’re often building things before the outcome is certain open protocols, new ideas, and infrastructure that may take years to realize their potential. Build with purpose. Let the impact follow. Wishing everyone celebrating a very Happy Janmashtami! #Janmashtami #Krishna #Web3 #Ethereum

EIPs & Network Upgrades | August 2026

Every major Ethereum change starts as an idea written for public review. An Ethereum Improvement Proposal explains the motivation, technical specification & tradeoffs of a proposed standard or protocol change. Learn EIPs: ethshala.com #EIP

The @SECGov is preparing for 24-hour U.S. equity trading while proposing blockchain-ready transfer-agent rules, signaling a major shift toward always-on and on-chain markets. 📌What's covered: - SEC Brings 24-Hour Trading Into Focus - The SEC Is Looking Beyond Trading Hours - Blockchain Moves Into the SEC’s Transfer-Agent Rules - Two SEC Moves Point Toward Always-On, On-Chain Markets Details👇 #US #SEC #Blockchain #Trading #Crypto

New post on Eth Research! Proposed PQ upgrade for ecrecover By: - mirabelenkiy-circle 🔗 ethresear.ch/t/25844 Highlights: - Problem scope: many existing EVM contracts rely on ecrecover for ECDSA verification and would be vulnerable under quantum attacks; the proposal targets contract-level signature checks, not securing EOAs themselves. - Core idea: add a backward-compatible “PQ mode” to ecrecover triggered by a sentinel signature pattern, so immutable deployed contracts can keep calling ecrecover but get post-quantum verification when the sentinel is present. - Compatibility constraints drive the design: ecrecover must remain effectively “pure,” the EVM constraint r < n requires r to start with 0x00 for embedded data, and older OpenZeppelin implementations constrain v ∈ {27,28} and s < n/2—so the chosen sentinel is v=27, s=0 (since valid ECDSA never has s=0). - Mechanism: encode lookup metadata into r as 0x00 || signatureIndex (11 bytes) || verificationFunctionId (20 bytes), where signatureIndex points into EIP-8141’s tx.signature[] array and verificationFunctionId selects a canonical pure verifier (or a pure-style registry/precompile). - Key open dependency: returning the claimed address requires a pure way to prove that the claimed address authorizes the post-quantum public key; the post suggests possible anchors (EIP-8164, EIP-7932, EIP-8130) but notes the final approach depends on how EIP-8141 and related standards evolve, with alternatives discussed and rejected mainly due to breaking old contracts or introducing unsafe/non-pure behaviors (e.g., ERC-1271 view calls enabling unintended authorizations). ELI5: Lots of Ethereum smart contracts use a tool called ecrecover to check “did this person really sign this message?” using today’s signature math (ECDSA). Powerful future quantum computers could forge those signatures. Instead of turning ecrecover off (which would break old contracts), this proposal suggests giving ecrecover a special “secret pattern” (a sentinel) that tells it to verify a newer, quantum-resistant signature that is carried inside a newer transaction format (EIP-8141). The goal is to let old, immutable contracts gradually migrate without changing their code, while still keeping ecrecover behaving like a ‘pure’ function (no surprising state reads or side effects).

Your Ethereum learning should feel measurable. ETHShala’s My Learning area keeps your journey organised so you can return, continue & build knowledge one module at a time. Sign in and keep moving: ethshala.com #EthereumEducation

From one meeting to ACDE, ACDC & ACDT, Ethereum’s All Core Devs coordination has evolved organically over the years. In her latest piece, @PoojaRanjan19 looks back at how these roles evolved - from early ACD & Hard Fork Coordination to ECH, Protocol Support & today’s distributed structure. Follow the evolution of ACD coordination 👇 #Ethereum #ACD #ProtocolGovernance #CoreDevs #EthereumCommunity

The latest AllCoreDevs Testing #094 updates are live on @EIPsInsight. Glamsterdam devnet-9 is targeting launch tomorrow, with Sepolia shadow-fork testing planned for mid-to-late September. FOCIL is moving forward with a 4,112 inclusion-list size limit and a gossip rule rejecting inclusion lists with empty transactions. An ePBS gossip fix also addresses bids from builders who exited in the previous full payload. EIP-8037’s SELFDESTRUCT refund is a no-go for Glamsterdam, while the cross-frame state-gas bug is deferred to ACDC on September 4. Snap2 shadow-fork testing will start on Sepolia before moving to mainnet. @parithosh_j @nero_eth @lightclients 🔗 ACDT: eipsinsight.com/calls/acdt/0… 🔗 CL Breakout: eipsinsight.com/calls/acdtcl… #Ethereum #Glamsterdam #FOCIL #EIPs