IPFS

Decentralized Data Protocol

Peer-to-peer distributed file system and protocol that uses content-addressing to uniquely identify files in a global namespace

Comunidade

Links

Visitar Comunidade

Detalhes

Licença

MIT / Apache 2.0 (dual license)

Status de Dev 🟢 Ativo

Detalhe do Status de Dev

Released / Mature — widely deployed content-addressed networking stack; primary implementations in Go (Kubo v0.30+) and JavaScript (Helia); production use across NFT platforms, web3 tooling, and archival systems; Desktop app, browser extensions, and cloud pinning services broadly available

Proprietário

Protocol Labs (founded by Juan Benet)

Órgão de Governança Company-controlled (Protocol Labs) | IETF (Internet-Drafts for CID and content-routing specifications)

País

USA (San Francisco, California)

Ano de Início 2013

Stack

Go (Kubo), Rust (iroh), JavaScript (js-ipfs), Python

Financiamento

VC + ICO (Filecoin $257M in 2017, funds Protocol Labs broadly)

Última Investigação 9 de mar. de 2026

Domínios de Caso de Uso

Platform Evolution & Sovereignty

Decentralized Data Protocol Atributos

Origins

File sharing / Distributed storage

Database

Content-addressed distributed storage (no traditional database)

Query Language

N/A (IPFS Path/CID resolution)

Data Formats

Any (content-agnostic)

Collaborative Live Editing

Application-level (not protocol feature)

Rich Text Editing

N/A (application-level)

Mobile Support

Yes (implementations available)

Web Support

Yes (HTTP gateways + js-ipfs)

Native Apps

Yes (IPFS Desktop, CLI tools)

Terms

Self-hosting + Free public gateways + Paid services (Pinning)

Funds

$257M (Filecoin Token Sale 2017 total: $52M presale + $205.8M public)

Based On

BitTorrent + Git (conceptually)

P2P Architecture

Kademlia DHT (for peer discovery)

Overlay Network

Global DHT

Content Addressing

Content addressing (CIDs via cryptographic hashing)

Local-First

N/A (nodes store cached content)

E2EE

N/A (content is public by default, E2EE at application layer)

CRDTs Lib

N/A (IPFS itself doesn't use CRDTs, but can store CRDT data)

Byzantine Fault Tolerance

N/A (no consensus mechanism, content integrity via hashing)

Signature

Cryptographic hashing (content verification, not signing)

Permissions

N/A (public by default, no built-in access control)

Semantic Web Compatibility

IPLD (InterPlanetary Linked Data)

Smart Contract

N/A (Filecoin has smart contracts, not IPFS)

Protocol Stack Position

Application-layer (built on TCP/IP)

Asset / Value Embedding

None — IPFS is a content-addressed storage and retrieval protocol with no native token or economic incentive layer at the protocol level. Pinning services and storage nodes operate independently without protocol-mandated payment.

Protocol Maturity / Standardization

IETF Draft (CIDs specified in draft-multiformats-cid; content routing via HTTP delegated routing specs; libp2p components under active IETF submission)