Institutional-Grade Blockchain Solutions, Built to Deliver. Nethermind has long been the foundation for institutional adoption in Web3. We are now making it easier than ever for institutions, enterprises, and crypto-native protocols to engage with our end-to-end blockchain

Nethermind is proud to support @boundless_xyz and the launch of The Signal, an open-source ZK consensus client that enables any chain to verify Ethereum’s state cryptographically. This milestone brings Ethereum closer to becoming a universal trust layer: Powering cheaper bridges,.

What gaps, nuances, protocols or features should we include?. · EIP impacts?.· Fair-exchange mechanisms?.· Protocol-specific nuances?. DM or reply, we want this to reflect community input. (4/4).

We’ll publish the SoK as an open-source PDF and keep it aligned with evolving resources, inspired by (3/4).

Why preconfirmations matter:.· Sub-second tx assurances via preconf are critical for UX.· Moving from centralized to decentralized preconf requires deep understanding.· Designs vary widely. Our SoK will clarify definitions, map trade-offs, and outline open questions. (2/4).

🧵 Excited to share we’re working on a Systemization of Knowledge (SoK) for preconfirmations in Ethereum. A collaborative, open-source reference covering theory, designs, critiques, and real-world implementations. Supported by @taikoxyz and an @EF_ESP grant. (1/4)

Our Head of Research @mpfzajac shares Nethermind’s vision for Ethereum: Scaling to billions of users and AI agents using ZK. · Offload heavy compute offchain .· Verify efficiently onchain. This unlocks verifiable, high-throughput systems for the agentic era.

From based rollup templates to L1-L2 composability to AI-aided smart contract audits:. At EthCC[8], we shared what we’ve been researching and building across the stack. 🔗

RT @Smartprogrammer: Nethermind's position on glamsterdam's headliners:.#ethereum.

RT @ant_sabado: The @NethermindEth leadership team together with @tkstanczak and I had a lively exchange with TradFi leaders on a number of….

6/. Next up: PerfNet, and how it fits into this performance journey.

5/. This is a living effort. We’re continuing to share data, tools, and dashboards, and working alongside others focused on improving Ethereum’s execution layer. Because resilience at scale requires deep visibility. 🔗

4/. The impact so far:. — Worst-case scenarios improved by ~25% .— Notable gains in complex transaction handling .— 45M gas block processing unlocked, with a clear path toward even higher limits .— Infra teams already benefiting from more stable throughput.

3/. Along the way, we surfaced issues that weren’t previously visible:. — Bottlenecks in opcodes and precompiles .— Execution slowdowns in complex tx types .— Patterns that hinted at deeper optimizations. Many of these led to upstream fixes, quietly, collaboratively.

2/. Each client behaves differently under load. So we created shared scenarios, ran gas-heavy transactions, and measured performance at scale, across time, versions, and configurations. It’s not about comparison. It’s about revealing the edges, together.

Last thread, we promised more on gas benchmarking. Through structured gas benchmarking, we’ve:.— Surfaced opcode bottlenecks.— Improved 7702 tx performance.— Helped some clients cut worst-case execution by 25%+.— Unlocked 45M gas blocks. Here’s how it happened ⬇️

RT @ant_sabado: Today, in the heart of Canary Wharf, London, @tkstanczak and I and the @NethermindEth team will be diving deep into the cor….

RT @NethermindSec: The @NethermindSec Formal Verification team, with support from the @ethereumfndn through the 2024 ZK Grants Round, has d….

Nethermind builds infrastructure for a modular, verifiable future. That’s why we’re contributing to The Signal: An industry-wide collaboration to connect all chains by ZK proofs. It’s a critical step toward trustless, cross-chain interoperability.

8/. More on gas benchmarking and PerfNet coming soon. Thanks for following along.

7/. We’re not the only ones doing this, many teams test and contribute every day. But we’re proud to add to that collective effort, through open tooling, data sharing, and a focus on performance-first thinking.