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

Joined October 2021
734 Photos and videos
Pinned Tweet
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
11
2
30
1,366
Lighthouse retweeted
🎙️ Founder Led Marketing │ TODAY, 5 PM UTC Anonymous accounts built crypto… Founders are building the next cycle 🛠️ @LighthouseWeb3 @vs1_finance @NebulaiHQ 3 more! Unpacking why winning projects have one thing in common: visible founders who know how to communicate.
32
75
207
10,099
1/ RWA perps alone did $524 billion in trading volume last quarter. the documents proving the underlying assets are real? sitting on centralised servers. RWA has an infrastructure problem nobody's talking about 🧵
1
6
242
9/ Genuine question for anyone building in RWA: Where are your off-chain documents stored right now? asking because the answer we hear most often is "S3" or "we haven't figured that out yet" and at $16T by 2030 that answer needs to change.
1
3
45
10/ this is the problem we exist to solve at @LighthouseWeb3 Decentralised storage with client-side encryption and on-chain access control. asset documents your token holders can verify and only they can read. the token is decentralised. the proof should be too. → lighthouse.storage
3
48
Lighthouse retweeted
Big update from the @CodeXero_xyz ecosystem. Someone just built a crazy tool called “AnonWall” just by chatting with AI. This tool is an anonymous wall where people will be able leave their confessions, secrets and even their hot takes forever onchain. This means that whatever gets written on AnonWall today could still exist decades of years from now. It’s: → Live on @base → Permanently stored with @LighthouseWeb3 → Cant be edited or deleted This is just another level of how creative and unpredictable onchain apps are now becoming. Check out the video in the quoted tweet below to see for yourself.
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?
12
3
22
619
Lighthouse retweeted
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
108
98
266
36,038
Lighthouse retweeted
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?
149
201
386
80,987
Lighthouse retweeted
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!
3
14
444
we don't talk about the 9 second incident
3
130
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]
3
7
430
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]
1
1
60
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. → lighthouse.storage [12/12]
1
79