@silverpill @p @Moon

> From what I heard, you split objects into pieces and transfer them via IPFS... Is that correct?

No. Kind of. IPFS is an alternative supplemental channel that works transparently by fortuitous coincidence: IPFS and Revolver both use SHA-256. So Revolver can kind of optimistically request blocks from IPFS and it can send them to IPFS as a fire-and-forget, but I have IPFS disabled on most of the nodes because it slows down the network. It has its own protocol for moving the slush and it can make use of side-channels, like it uses HTTP as one side-channel, so it can fetch blocks over HTTP/HTTPS/Tor and probably I2P, and eventually other stuff. The idea is that it should be easy to move data into and out of your node regardless of network-level censorship, so you set the protocols you want your node to speak and it looks for peers that advertise that they speak that protocol. IPFS is almost only accidentally a transport layer because it's a pluggable backend layer that happens to speak to a network; there's no reason it couldn't support Tahoe-LAFS or something as another storage backend (venti is planned). For network propagation, at some point it might even support bittorrent at some point (looking into it is planned).

> You can use regular HTTP to deliver them and fetch them, but you can also use other transports.

This is a good plan.