This is a simple description of where the codebase stands.
There are multiple subpackages:
bitswap
- the block exchangeblocks
- handles dealing with individual blocks and sharding filesblockservice
- handles getting and storing blockscmd/ipfs
- cli ipfs tool - the main entrypoint atmconfig
- load/edit configurationcore
- the core node, joins all the piecesfuse/readonly
- mount/ipfs
as a readonly fuse fsimporter
- import files into ipfsmerkledag
- merkle dag data structurepath
- path resolution over merkledag data structurepeer
- identity + addresses of local and remote peersrouting
- the routing systemrouting/dht
- the DHT default routing system implementationswarm
- connection multiplexing, many peers and many transportsutil
- various utilities
- merkle dag data structure
- path resolution over merkle dag
- local storage of blocks
- basic file import/export (
ipfs add
,ipfs cat
) - mounting
/ipfs
(try{cat, ls} /ipfs/<path>
) - multiplexing connections (tcp atm)
- peer addressing
- dht - impl basic kademlia routing
- bitswap - impl basic block exchange functionality
- crypto - building trust between peers in the network
- block splitting on import - Rabin fingerprints, etc
- ipns - impl
/ipns
obj publishing + path resolution - expose objects to the web at
http://ipfs.io/<path>
- version control -
commit
like data structure - more...
A list of cool demos to work towards
- boot a VM from an image in ipfs
- boot a VM from a filesystem tree in ipfs
- publish static websites directly from ipfs
- expose objects to the web at
http://ipfs.io/<path>
- mounted auto-committing versioned personal dropbox
- mounted encrypted personal/group dropbox
- mounted {npm, apt, other pkg manager} registry
- open a video on ipfs, stream it in
- watch a video with a topology of 1 seed N leechers (N ~100)
- more in section 3.8 in the paper