ChainSafe

The protocol determines correctness. The operator determines reliability. blog.chainsafe.io/decentralized-…

Catch @0xzak and I live with @laurashin 1pm ET

The EF is shrinking. Researchers are leaving. Vitalik says ETH is "the most high-value product" and CROPS is the new mandate. What does that all mean for Ethereum? @0xzak + @gregthegreek join @laurashin Today at 1 pm ET Join us on: X - x.com/Unchained_pod YouTube - youtube.com/channel/UCWiiM… or PumpFun - pump.fun/coin/GgzH3GfJa…

Read part 1 of our 3 part blog series on decentralized infrastructure blog.chainsafe.io/decentralized-…

The protocol determines correctness. The operator determines reliability. How do you manage uptime and failover when the underlying system is fundamentally beyond your control? Our latest piece breaks down this operational shift and where the new boundary of DevOps actually begins. Link below 👇

What if your users could trade with capital they've already deployed somewhere else? @alexmattm breaks down how credit-backed Trading Accounts work, and what Sprinter's credit engine looks like in practice 👇

The DeFi stack, 2026: Settlement ☑️ Trading ☑️ Stablecoins ☑️ Lending ☑️ Credit❔ One layer is still uncredited. This month we're filling it in - sector by sector.

Blockchain privacy is moving from ideology to architecture. For years, privacy in web3 was treated as a philosophical ideal. In 2026, it’s a hard engineering requirement for institutional digital asset management. We’re no longer just talking about why we need privacy. We’re looking at how we build it using ZK-Rollups, private L2s, TEEs, and FHE. We took a look at today's privacy landscape in the article below 👇

👀

We're joining @ethStaker to talk protocol development in the age of AI, minority clients, and how Zig is the future of all the things. Starting 1500 UTC, tune in here!

Zig is becoming an increasingly attractive choice for building native Node.js modules. But the JavaScript binding layer still feels stuck in 2015. Even the simplest native function requires repetitive plumbing. For every useful line of logic, you write several lines of binding code. While building native infrastructure, we kept running into this problem repeatedly inside zapi, a Zig N-API wrapper library and CLI for building and publishing cross-platform Node.js native addons. We wanted a way to preserve full control over Node's N-API when needed while dramatically simplifying the common path. The result is a new high-level DSL introduced in zapi that lets you write plain Zig functions and automatically turns them into JavaScript APIs at compile time. The DSL is already powering production bindings in lodestar-z, where we are migrating Lodestar, ChainSafe's Ethereum consensus client, from JavaScript to Zig.

This week Ethstaker will have Community Call #65 to talk with the Chainsafe (@ChainSafeth) team working on Lodestar (@lodestar_eth) on what's new in CL client development. When: Wednesday May 13 at 15:00 UTC Tune in to hear the latest and ask questions in the chat! YouTube livestream link in next tweet.

Our latest blog breaks down 5 privacy approaches for institutional digital asset management in 2026. The emphasis on blockchain privacy that emerged in the early 2020s has concluded not with a single winner, but with a mosaic of specialized solutions. The mandate for institutional adoption is clear: Architecture is Strategy. The most successful firms of this era are those that remain cryptographically agile, ensuring that as these technologies mature, their digital assets remain secure, compliant, and, above all, private. Read more ⬇

Something I was building recently. Very useful if you have some performance bottleneck in NodeJS and want to fix with native layer. #nodejs #performance

Read the full writeup here: blog.chainsafe.io/zapi-zig-nativ…

Find the complete update here: github.com/ChainSafe/fore…

This month in Forest, the Rust-based node, making Filecoin faster and easier to use. ✅ NV28 upgrade Forest joins Lotus and Venus in supporting the NV28 upgrade. The calib net upgrade is scheduled for May 7th - make sure to upgrade your Forest node before that date to avoid any issues ✅ Finality calculator integration New Forest releases integrate the finality calculator. This allows Forest to provide a safe finality estimate for the latest block, especially in cases where fast finality is not available (currently on mainnet). 🏗️ Strict JSON validation JSON-RPC is a quite forgiving protocol when it comes to parsing JSON. This can lead to some unexpected behaviour, e.g., when missing fields are silently ignored or when map key are not unique. Setting FOREST_STRICT_JSON will catch some of these issues, punishing technically-correct-but-probably-broken JSON with an error instead of silently accepting it. Useful in development and testing, but adds some overhead, so it's not enabled by default. 🏗️ State Tree snapshots We're tinkering with a different approach to archival snapshots, with a leaner format that would improve archival snapshot ergonomics and reduce the amount of disk space needed. Read the full update for more improvements and fixes the team tackled this month. ⤵️