ChainSafe

@ChainSafeth

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

Toronto, Ontario

chainsafe.io

Joined August 2018

904 Following

13.8K Followers

Replies Reposts Media Articles

ChainSafe
@ChainSafeth
5h
You can verify this yourself: ChainSafe operates default bootstrap nodes in all three independent Filecoin client implementations → Lotus, Forest and Venus. They're listed right in the source. Links and ProbeLabs dashboard, check em👇
1
ChainSafe
@ChainSafeth
Oct 5
🌲 This Month in Forest: September 2026 Fix, v. "To remove [a bug] by redefining the program specification in order to take advantage of an unexpected feature." — Stan Kelly-Bootle, The Computer Contradictionary This month, we fixed things the hard way: → NV29 "Solstice":
1
ChainSafe
@ChainSafeth
Oct 2
ChainSafe is now the default proof parameter provider for Forest & Lotus. Older build? Check your fallback isn't pointing at the default. Links 👇
2
ChainSafe
@ChainSafeth
Sep 29
The only way to run AI on your data while minimizing trust is math. There are two main ways to do it. Fully homomorphic encryption lets a server run the model on your data while it stays encrypted, so the server never sees it. Multi-party computation splits your data into
00:00
1
ChainSafe
@ChainSafeth
Sep 28
"Providers can be single sources of failure and take down a blockchain." This is why multi-provider infrastructure isn't optional for web3. Operational complexity is a small price to pay for network resilience.
Josh Dougall
@joshdougall
Sep 25
I keep getting asked by providers to consolidate ChainSafe infrastructure into a single provider, and they ask why ChainSafe runs multi-provider by default. Short answer: providers can be single sources of failure and take down a blockchain. Hetzner, OVH, CherryServers, etc.,