IPFS — The Permanent, Distributed Web

How IPFS refer everything

How it differs from HTTP

So one can think IPFS like HTTP web + Git+ BitTorrent.

Lets dive in to the working of IPFS

sudo mv ipfs /usr/local/bin/ipfs
C:\..>move .\go-ipfs\ipfs.exe C:\Windows
$ ipfs init
initializing IPFS node at /Users/romiljain/.ipfs
generating 2048-bit RSA keypair...donepeer identity: QmWwvCycToWiUfMtoAWW9r5aEoeHK4KcmubtKhEmCGJJmeto get started, enter:ipfs cat /ipfs/QmS4ustL54uo8FzR9455qaxZwuMiUhyvMcX9Ba8nUH4uVv/readme
$ ipfs cat /ipfs/QmS4ustL54uo8FzR9455qaxZwuMiUhyvMcX9Ba8nUH4uVv/readme
Make sure to read the warning :)
$ mkdir ipfsdir
$ cd ipfsdir
$ touch hello.txt
$ ipfs add hello.txtadded QmWATWQ7fVPP2EFGu71UkfnqhYXDYH566qy47CnJDgvs8u hello.txt
$ ipfs pin add QmWATWQ7fVPP2EFGu71UkfnqhYXDYH566qy47CnJDgvs8upinned QmWATWQ7fVPP2EFGu71UkfnqhYXDYH566qy47CnJDgvs8u recursively
$ ipfs daemon
Initializing daemon...Adjusting current ulimit to 2048...Successfully raised file descriptor limit to 2048.Swarm listening on /ip4/127.0.0.1/tcp/4001Swarm listening on /ip4/192.168.0.101/tcp/4001Swarm listening on /ip6/::1/tcp/4001Swarm listening on /p2p-circuit/ipfs/QmWwvCycToWiUfMtoAWW9r5aEoeHK4KcmubtKhEmCGJJmeSwarm announcing /ip4/127.0.0.1/tcp/4001Swarm announcing /ip4/192.168.0.101/tcp/4001Swarm announcing /ip4/71.75.18.38/tcp/23917Swarm announcing /ip6/::1/tcp/4001API server listening on /ip4/127.0.0.1/tcp/5001Gateway (readonly) server listening on /ip4/127.0.0.1/tcp/8080Daemon is ready
$ ipfs swarm peers

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store