This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:defact:ipfs:start [2021/08/18 10:05] murphy [Abstract] |
dido:public:ra:xapend:xapend.b_stds:defact:ipfs:start [2022/01/05 17:04] (current) nick |
||
|---|---|---|---|
| Line 22: | Line 22: | ||
| ==== Abstract ==== | ==== Abstract ==== | ||
| - | : //The InterPlanetary File System (IPFS) is a peer-to-peer distributed file system that seeks to connect all computing devices with the same system of files. In some ways, IPFS is similar to the Web, but IPFS could be seen as a single BitTorrent swarm, exchanging objects within one Git repository. In other words, IPFS provides a high [[dido:public:ra:xapend:xapend.a_glossary:t:thruput|throughput]] content-addressed block storage model, with content addressed hyper links. This forms a generalized Merkle DAG, a [[dido:public:ra:xapend:xapend.a_glossary:d:datastructure|data structure]] upon which one can build versioned file systems, blockchains, and even a Permanent Web. IPFS combines a distributed hashtable, an incentivized block exchange, and a self-certifying namespace. IPFS has no single point of failure, and nodes do not need to trust each other.(( | + | : //The [[dido:public:ra:xapend:xapend.a_glossary:i:ipfs]] is a peer-to-peer distributed file system that seeks to connect all computing devices with the same system of files. In some ways, IPFS is similar to the Web, but IPFS could be seen as a single BitTorrent swarm, exchanging objects within one Git repository. In other words, IPFS provides a high [[dido:public:ra:xapend:xapend.a_glossary:t:thruput|throughput]] content-addressed block storage model, with content addressed hyper links. This forms a generalized Merkle DAG, a [[dido:public:ra:xapend:xapend.a_glossary:d:datastructure|data structure]] upon which one can build versioned file systems, blockchains, and even a Permanent Web. IPFS combines a distributed hashtable, an incentivized block exchange, and a self-certifying namespace. IPFS has no single point of failure, and nodes do not need to trust each other.(( |
| "IPFS - Content Addressed, Versioned, P2P File System (DRAFT 3)", Juan Denet, 24 July 2014, | "IPFS - Content Addressed, Versioned, P2P File System (DRAFT 3)", Juan Denet, 24 July 2014, | ||
| [[https://github.com/ipfs/ipfs/blob/master/papers/ipfs-cap2pfs/ipfs-p2p-file-system.pdf]] | [[https://github.com/ipfs/ipfs/blob/master/papers/ipfs-cap2pfs/ipfs-p2p-file-system.pdf]] | ||