Skip to content

Latest commit

 

History

History
23 lines (18 loc) · 1.4 KB

IPFS.md

File metadata and controls

23 lines (18 loc) · 1.4 KB

IPFS

  • It's a file system with content based addressing. Instead of domains, you use the content as the domain. Because content can be very very long, we run a small program on it to produce a unique identifier based on that content (a hash). These identifiers are long enough that the possibility of two pieces of content creating the same one is virtually impossible.
  • Once something is added, it can't be changed anymore.
  • IPFS supports versioning using commits.
  • Keeping files available is a challenge. If the nodes storing a file go down, it'll disappear from the network. Filecoin can help with this adding incentives to the equation.
  • IPFS makes some nice properties the default. E.g: content addressing.
  • Data model for IPFS
  • Everything is a node. Nodes have types.
  • The data structure is a Merkle Tree.
  • Makes easy to have interoperability of data. Useful for distributed databases.
    • Bridges content addressing and distributed systems.

LibP2P

  • Modular peer to peer networking layer.
  • Multiple users across the decentralized ecosystem.
  • Many implementations of each module.