bluΞavm.Ξth 🦇🔊 retweeted
we are launching a stealth addresses working group, featuring the best engineering teams dedicated to solving stealth addresses’ toughest crypto and ux problems on Ethereum
goals: pq security, new keystore designs, hardware wallets integration and broadening adoption
let’s go!
stealthaddresses.xyz/
bluΞavm.Ξth 🦇🔊 retweeted
𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝗶𝗻𝗴 𝗡𝗲𝘁𝗵𝗲𝗿𝗺𝗶𝗻𝗱 𝗟𝗶𝗴𝗵𝘁 𝗖𝗹𝗶𝗲𝗻𝘁
Trustless RPC for every wallet.
Verify Ethereum yourself, without running a full node.
𝗛𝗼𝘄 𝗶𝘁 𝘄𝗼𝗿𝗸𝘀
→ One trust anchor: a recent finalized beacon block root
→ Consensus: sync committee updates over libp2p, with signatures and Merkle branches verified
→ Execution: state on demand through SNAP, every range proven against the state root
→ Performance boosted through partial state caching for selected and frequently queried accounts.
𝗕𝘂𝗶𝗹𝘁 𝗼𝗻 𝗯𝗮𝘁𝘁𝗹𝗲-𝘁𝗲𝘀𝘁𝗲𝗱 𝗡𝗲𝘁𝗵𝗲𝗿𝗺𝗶𝗻𝗱 𝗰𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁𝘀
→ eth_call and eth_estimateGas run locally in the Nethermind EVM, nothing forwarded
→ Developed inside the Nethermind client codebase
→ Glamsterdam-ready
𝗙𝗼𝗿 𝘆𝗼𝘂, 𝗶𝘁’𝘀 𝗷𝘂𝘀𝘁 𝗹𝗼𝗰𝗮𝗹𝗵𝗼𝘀𝘁:𝟴𝟱𝟰𝟱
Point MetaMask, or any wallet, at it.
In active development. Congrats @__flcl and the team.
Follow the progress and share feedback:
github.com/NethermindEth/net…
bluΞavm.Ξth 🦇🔊 retweeted
My advice to everyone, if you have a networked smart device, rip the connectivity out of it, *now*.
Unplug the ethernet, get it off the WiFI, trash it if you can’t. There’s a storm coming, and it’s going to be scary.
It’s the time of reckoning for decades of IoT negligence.
bluΞavm.Ξth 🦇🔊 retweeted
My take on the immutable contracts affected by Glamsterdan:
While I value every protocol that has deployed their code as an immutable contract, expecting a contract to work forever is a heavily wrong assumption. This would require the Ethereum network to ossify at its current state. Every immutable contract is known to work perfectly until the next fork, while it will need to be reviewed and maybe users would need to migrate to a more recent implementation. Those who make fewer assumptions may continue working, some may not.
This is not the first time that an Ethereum fork ships breaking changes. Stable containers, just to name one feature, will also break all contracts that relied on state proofs in the name of making future changes safer and easier for everyone. That EIP broke Merkle tree verifiers a single time, while committing to forward compatibility from that fork onwards. That was very positive, but required many immutable contracts to be replaced by newer versions. If you designed your protocol to be completely immutable on top of a protocol that is mutable you just made a wrong design decision.
Changes on how Ethereum works are expected and positive for the network and if you're trying to stop them because your contract making gas assumptions broke, I would invite you to move to an ossified-too-soon-network like Bitcoin.
I'm against solutions that involve a dual-schedule or versioned approach to this as it just adds more complexity to an already too complex protocol. We should be removing complexity, not adding it.
If you have a contract affected by Glamsterdam, feel free to reach out to Ethlabs. My DMs are open!
---
Here is a personal view on the Glamsterdam controversy.
This comes from me as someone who was a builder on Ethereum for close to ten years and only recently (two-ish months ago) became more closely aligned with the core development.
Unlike what some posters would like you to think, there isn't an internal mathematician ivory tower cabal completely uninterested with the app layer.
There are individuals, often with wildly dissenting opinions - working towards a mandate of a scalable, private, CROPS aligned chains.
They work under very tight constraints for bandwith, state growth, i/o and compute. Not to mention the biggest constraints of them all - 100% uptime and backwards compatibility.
For this reason, almost *all* invariants have been kept as they are and contracts deployed as far back as ten years ago work just the same as they did before.
So sometimes, some of them propose upgrades which break certain invariants. This is never done in a vacuum and without discussions on the potential implications.
However, as the Ethereum app ecosystem became so complex - almost every property of the chain is depended on by some contract, somewhere.
Naturally, breaking those contracts is not something which is taken lightly. But sometimes it *must* be done. (note: this is my personal opinion - not the official stance of Ethlabs or core devs. )
What's important in that case is that proper disclosures are done, a proper security audit completed and all the relevant parties notified. This is the part where the comms failed and its the part which needs improvements.
Lucikly, AI swarms are now able to scan huge amounts of deployed contract code for invariant breaks (thanks in no small part to @SourcifyEth) and generate reports. I think those swarms will become essential parts of the way new EIPs are done.
bluΞavm.Ξth 🦇🔊 retweeted
PSA: Please verify that your contracts are still working after Glamsterdam! We created a repository with Invariants that will be broken after the fork, so you can verify for yourself.
blog.ethereum.org/2026/11/06…
bluΞavm.Ξth 🦇🔊 retweeted
Ethereum is stepping to it for post quantum. Frame tx in Hegotá. leanSPHINCS in I\*. That’s your wallet safe.
PQ key registry for validators in Hegotá. Fully PQ by Dec 2028, subject to delays and changes.
Looking For Group, as they say in sportsball.
strawmap.org
bluΞavm.Ξth 🦇🔊 retweeted
We are pleased to introduce ETHIndia Institutional
As the Ethereum ecosystem matures and its focus turns institutional, we want to help progress Ethereum's institutional adoption in India.
Follow our work: institutional.ethindia.co/
Quantum computing poses a serious threat to the cryptography blockchains currently rely on, while advances in AI compress best estimates for the threat's timeline.
That's why experts gathered in Cambridge to coordinate research upgrading our cryptography to be quantum-resistant.
bluΞavm.Ξth 🦇🔊 retweeted
So far, the promise of Ethereum has failed
1000s of nodes secure the chain. But when most users check their balance, their wallet asks a server what they own, and they believe it
More on this Nov 4 at 4pm
bluΞavm.Ξth 🦇🔊 retweeted
🚨 PSA for anyone running a Linux server, node, or relay
CVE-2026-98432 is a critical Linux kernel bug (CVSS 9.8). Someone on the internet can send crafted TCP packets and take over your machine. No login needed.
Ubuntu and Red Hat haven't shipped a fixed kernel yet. Debian, SUSE, Oracle and Amazon have.
What to do today:
1. Check your kernel: uname -r
Fixed versions: 6.1.190+, 6.6.159+, 6.12.113+, 6.18.56+, 7.2.10+ or 7.3+. Below that, you're exposed.
2. If your distro has a fix, update and reboot.
3. If not, block the attack. It needs TCP packets with "IP options," which normal traffic never uses. One nftables rule drops them. Log what gets dropped so you can see if someone's probing you.
4. Turn off MPTCP unless you need it:
sysctl -w net.mptcp.enabled=0
Programs built with Go 1.24+ use MPTCP automatically, and that's how the known exploit gets in.
5. Make it survive a reboot, and check it still works after one.
If you run a Bitcoin node, a Lightning node or a Nostr relay, your machine is on the internet by design. Do this today.
Self-hosting is freedom. Patching is part of the job. 🛡️
bluΞavm.Ξth 🦇🔊 retweeted
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.
github.com/ethereum/EthLib
bluΞavm.Ξth 🦇🔊 retweeted
Is Ethereum ready for the quantum threat?
On the latest Ready for Merge podcast, EF cryptographer @asanso broke down the aggressive timeline and massive architectural shifts required to migrate Ethereum to PQ cryptography. 🧵👇
bluΞavm.Ξth 🦇🔊 retweeted
1/ Today we’re releasing Aerie: fast post-quantum signature aggregation, using lattice-based SNARKs for lattice-based Falcon signatures. On a laptop (CPU only), it aggregates roughly a full Ethereum slot’s worth of signatures (32,768) in 0.65 seconds.
bluΞavm.Ξth 🦇🔊 retweeted
This is also what will happen to Ethereum - the pace of changes will be beyond human governance abilities and the chain will start behaving like an adaptive system with hierarchies defined by the value of signal and infrastructure shape in the given region.
New on our Engineering blog: Creating in-house source control.
In May, we merged around 2,500 code changes per day. In September, we merged more than 30,000 per day. As a result, we became bottlenecked by developer infrastructure built for human (rather than agent) scale.
Here, we share how we built a new version control system—and fully migrated our monorepo from git—in five months: anthropic.com/engineering/re…
bluΞavm.Ξth 🦇🔊 retweeted
L2s are shutting down because being useful requires costly integrations: oracles, liquidity, stablecoins…
With EEZ, everything on Ethereum is also available on your L2 out of the box - so L2s can focus on their core business!
bluΞavm.Ξth 🦇🔊 retweeted
Glamsterdam just went live on Sepolia, bringing ePBS and block-level access lists one step closer to mainnet.
This Nethermind node is following it with no separate consensus client, using a beacon chain plugin we're still developing.
bluΞavm.Ξth 🦇🔊 retweeted
Update your nodes!
Glamsterdam activates on Sepolia in 24hrs and only half the network is signaling ready 😆
enrscout.ethnodeops.xyz/fork…





























