Lighthouse

Immutable storage for AI & Web3, built on IPFS. Trusted by 1000s of apps 🌐

[Lighthouse @LighthouseWeb3]

Lighthouse, reimagined.

A cleaner interface.
A sharper story.
A stronger foundation for what’s ahead.

Built for a world where data is permanent, private, and composable.

Explore the new experience → link in comments

[Cluster Protocol @ClusterProtocol]

Cluster Roundtable: "Who actually owns the data that trained the AI you're using?"

Every model you interact with was trained on something: scraped websites, licensed datasets, maybe even your own content.

But who owns that data, who profits from it, and who gets to decide how it's used? We're breaking it all down.

ft.
~ @0xFF__, CSO @vs1_finance
~ @heenie1998, Tech Lead @inflectivAI
~ @_fiatisabubble, Community Coordinator @NEARProtocol
~ @nanditmehra, Founder & CEO @LighthouseWeb3
~ Jordan, COO @MoonWhaleAI
~ @pratikbin, CTO & Co-founder @BuildOnNodeOps
~ @m_defi24, Growth Manager @ant_fun_trade
~ @ArjunKalsy, Chief of Growth @Covalent_HQ
~ Eniitan, Community Manager, @paywithmana
~ @myo_visions, CMO @gamepad_co
~ @lmc_security, Founder & CEO @kash_bot
~ @ZTchikadze, COO @LLMTUNE_IO

🗓5th June | 2:30 PM UTC | X Spaces

[Lighthouse @LighthouseWeb3]

@SolanaFndn Solana just leveled up again 🔥

[Lighthouse @LighthouseWeb3]

https://t.co/gJMjaWyieW

[CodeXero (vibecode/acc) @CodeXero_xyz]

Introducing AnonWall.

An open notebook built on @CodeXero_xyz just by chatting with AI, where anyone can write a secret, a confession, or a hot take anonymously.

Nobody knows who wrote what, and nothing on it can ever be edited or deleted.

Live on @base, pinned permanently on @LighthouseWeb3. Whatever you write today will still be there in 2050.

What would you say if no one knew it was you?

[Nandit Mehra @nanditmehra]

Weekly 2500+ installs of Lighthouse SDK, more than any other IPFS and Filecoin SDKs like Synapse, Storacha, Akave, etc.

Hence, Lighthouse is most popular and consistent product for storing data, proofs, encryption, retrievals, etc. for developers and startups in decentralized storage ecosystem.

Organic and stable!

[Lighthouse @LighthouseWeb3]

we don't talk about the 9 second incident

[Lighthouse @LighthouseWeb3]

@0xharrynguyen That line is going in the next deck.

Audit trail + undo are two halves of the same problem.

You can't undo what you can't prove existed.

Most teams treat backups as the proof.
Then realize the backups live in the same blast radius.

[Lighthouse @LighthouseWeb3]

88% of organizations had AI agent security incidents this year.
60% can't even terminate a misbehaving agent.
33% have no audit trail of what their agents did.

Your backup strategy was built for human error.
Your AI agents operate at machine speed.

Why centralized backup architecture is breaking 🧵

[1/12]

[Lighthouse @LighthouseWeb3]

source - https://t.co/zPaovi9ayi

[Lighthouse @LighthouseWeb3]

THE LIGHTHOUSE STACK:

Decentralized storage via IPFS
↓
Client-side encryption (Kavach - BLS threshold crypto)
↓
Incremental backups with content addressing
↓
Go SDK for programmatic integration

Built for AI-first teams who need backups their agents literally cannot touch.

Because the only safe backup is one that doesn't live in the same infrastructure your agents access.

→ https://t.co/4LpvH6X1Bg

[12/12]

[Lighthouse @LighthouseWeb3]

THE RECOVERY REQUIREMENT:

In 2026, backups aren't valid until they're restored and verified.

Lighthouse incremental backups:
→ Content-addressed deduplication (store only changes)
→ Point-in-time recovery (rollback to 10 min ago, not 3 months)
→ Cryptographic verification of chunk integrity
→ No full re-backup needed (saves bandwidth + storage)

Built for SQL/NoSQL databases + object storage.

[11/12]