# Lighthouse Storage

> IPFS and Filecoin storage tooling for decentralized files, metadata, and app assets.

- Readiness score: **79/100** (score.v2)
- Integration difficulty: low
- Chains: arbitrum-one, ipfs, filecoin
- Categories: storage, ipfs, filecoin
- Last verified: 2026-05-29 by composewith.eth seed research (confidence: medium)

## Resources

- docs: https://docs.lighthouse.storage/
- sdk: https://github.com/lighthouse-web3/lighthouse-package
- template: https://docs.lighthouse.storage/
- support: https://discord.gg/c4c5GHZCdX
- grant: https://www.lighthouse.storage/

## Good for

- NFT metadata
- decentralized app assets
- agent-readable manifests
- encrypted files

## Avoid for

- high-mutation databases
- latency-critical app state

## Capabilities

### IPFS file storage (production-ready)
Best for: static assets, metadata, published manifests
- Pinning, retrieval, and gateway strategy must be planned for production.

## Composes with

- **erc-8004** (agent_identity_and_trust; supports) — Can store agent-readable manifests, registration metadata, or service descriptions referenced by ERC-8004 agents.
- **x402** (payments_and_commerce; supports) — Can store paid-content artifacts, receipts, or manifests around x402 API and commerce flows.
- **ens** (wallet_and_identity; supports) — ENS records can point users and agents to IPFS/Filecoin-hosted metadata and public project assets.

---
Canonical: https://composewith.eth/protocols/lighthouse-storage · JSON: https://composewith.eth/protocols/lighthouse-storage.json