ChainSafe

Read the full breakdown: blog.chainsafe.io/open-creator-r…

Patreon proved how power moves when creators own their audience. For devs and builders who want to take that further by self-hosting on their own site: Open Creator Rails (OCR) gives you an open-source, onchain paywall that you control. Learn more in comments👇

Lodestar processes SSZ data throughout every slot. That’s blocks, states, attestations, and more. How do we achieve less runtime machinery and lower memory pressure on this hot path? In Lodestar-z, Zig’s comptime generates specialized code directly from each SSZ schema. Field types, offsets, and serialization paths are resolved ahead of time. At runtime, the serializer writes directly into a caller-provided buffer. It still processes each field, but it doesn’t interpret a dynamic type descriptor or allocate per-field intermediate objects. Do the heavy lifting at compile time so the hot path doesn't have to.

Exciting Core upgrade from @LidoFinance 👀 Leveraging MaxEB to consolidate validators actively reduces L1 consensus strain. This is responsible scaling at the protocol layer.

RPC Performance: Forest vs Lotus: docs.forest.chainsafe.io/reports/node_c…

Our latest performance report shows Forest serving requests with significantly lower latency. Average wall time per HTTP request: 🌲 Forest: ~10-15 ms 🪷 Lotus: ~30-50 ms See the full data breakdown 👇

Most Web2 platforms pay early creators exactly $0 until they hit arbitrary thresholds—1k subs, 10k followers, 4k watch hours. Open Creator Rails (OCR) changes that math. Built as an open source stack under contract for the @ethereumfndn, OCR gives creators permissionless monetization on their own landing pages from Fan #1. Article below 👇

One reason we’re rebuilding Lodestar’s state-transition hot path in Zig: to reduce GC pressure and make latency more predictable. In a garbage-collected runtime, the application doesn’t precisely control when memory is reclaimed. Instead, allocation pressure may trigger collection, which can also pause execution. For most software, that's a fine trade. For a consensus client running against per-slot deadlines, unpredictable pauses can become latency you can’t reliably budget for. Zig has no garbage collector. Instead, you pass an allocator (an object that hands out and reclaims memory) into the functions that need it, so you decide where memory comes from and when it's freed.

Interesting read by @nad_roid on two tokenised RWAs. On paper one looks bulletproof and the other looks like a red flag. The safer one to hold is not the one you think. Read the article for spoilers 👇

Are you testing Lodestar's Fast Confirmation yet? Get a stronger-than-head safety signal in seconds instead of waiting 12.8 minutes for full finality. ⚠️ Keep in mind, it's a new, performance-heavy feature under active optimization!👇

We treat our staking rigs like a full-body engine: every layer tuned, from the bare metal in the rack to the client software running on top. When you write the client yourself, as we do with @lodestar_eth, you know exactly how it runs because you built it. Stake with us across Ethereum, Celestia, zkVerify, and ssv_network 500M+ USD secured and counting ⤵️

Fast Confirmation provides an extremely high level of confidence that a transaction will reach finality. They're fast. A Fast Confirmation can be reached in a single slot, which is a about -13 seconds. It's a 98% reduction compared to ~12.8 minute finality times. Why does it matter? Entities like CEXs, L2s, and bridges can rely on Fast Confirmation to speed up processing times, providing a better experience for end users. Fast Confirmation is now supported in Lodestar 👇

ETH Daily did a great job compressing our technical article on Fast Confirmation in Lodestar :D (Take a look if you’re a bit busy for flowcharts right now) ETHDaily and source articles below 👇🧵

⛓️🦺 infra.chainsafe.io/staking-overvi…

Fast Confirmation: safer than 𝐡𝐞𝐚𝐝 and faster than 𝐟𝐢𝐧𝐚𝐥𝐢𝐳𝐞𝐝, now enabled in Lodestar. Learn how it works and how to test it out below 👇🧵 ⚠️ This is a new feature and performance-intensive.