ChainSafe (@ChainSafeth) / X

ChainSafe

4,813 posts

ChainSafe

@ChainSafeth

Infrastructure and protocol development for the decentralized web. Home of the @lodestar_eth Ethereum client & Forest🌲 Filecoin client.

Toronto, Ontario

Joined August 2018

Replies Articles Media

ChainSafe
@ChainSafeth
Jul 29
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👇
Volodymyr Khomichenko
@V_Khomichenko
Jul 28
Article
Patreon. How Escaping the Algorithm Powered Its Growth
An audio version of this issue is also available as a podcast. If you prefer listening to reading, you can access it on the platform that is most convenient for you. Spotify | Youtube | Apple podcast...
ChainSafe
@ChainSafeth
Jul 27
Exciting Core upgrade from @LidoFinance 👀 Leveraging MaxEB to consolidate validators actively reduces L1 consensus strain. This is responsible scaling at the protocol layer.
Lido
@LidoFinance
Jul 27
Lido Core 2026 Upgrade The biggest evolution of Lido Core brings improvements across the staking modules to keep the protocol aligned with Ethereum’s roadmap and ensure long-term protocol sustainability. No action is required from stakers - the upgrade is protocol-level. ↓
00:00
ChainSafe
@ChainSafeth
Jul 24
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 👇
ChainSafe
@ChainSafeth
Jul 22
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
00:00
ChainSafe
@ChainSafeth
Jul 21
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
See @ChainSafeth's full profile
Sign up
Log in

See @ChainSafeth's full profile

See @ChainSafeth's full profile