Add IPFS Amino DHT support

[dmitry-markin]

Currently, there is only partial IPFS support in Bulletin node. In order to download chunks via IPFS, a bulletin node needs to be added first to the swarm of an IPFS node (ipfs swarm connect <multiaddr> with Kubo IPFS client). After this, the data can be downloaded via Bitswap protocol (ipfs block get <CID> with Kubo). In production use this would require hardcoding Bulletin node addresses to wallets/proxies, which is not desirable. In order to overcome this, we should implement publishing of content providers to IPFS Amino DHT. After this, given the transaction CID, IPFS nodes will be able to discover Bulletin nodes having it.

Sub-tasks:

• RSA network identity keys support in litep2p (used by Amino DHT bootnodes)
  Support RSA remote network identity keys litep2p#423
• ADD_PROVIDER, PUT_VALUE queries success tracking in litep2p
  kademlia: Track success of PUT_VALUE queries litep2p#427
  kademlia: Workaround for dealing with not implemented PUT_VALUE ACKs litep2p#430
  kademlia: Track success of ADD_PROVIDER queries litep2p#432
• Kademlia queries optimization (FIND_NODE, ADD_PROVIDER, GET_PROVIDERS) for Amino-scale DHT networks
• Support more than one DHT in litep2p (we need two simultaneously, bulletin + ipfs)
• litep2p address store optimization to not "leak" memory when encountering big number of peers present in Amino DHT — optional, if needed
• publishing of content providers in Bulletin node for CID keys of transactions from transaction storage
• stopping providing CID keys for transactions over two weeks old (TODO: clarify exact period)

[bkontur]

@dmitry-markin @antkve Do we need this for initial launch? When do we need this to be ready?

[dmitry-markin]

@dmitry-markin @antkve Do we need this for initial launch? When do we need this to be ready?

No, as we agreed in the PoP chat, Bitswap support (ready) is enough for the initial launch (with a consequence that wallet IPFS proxies will need to hardcode bulletin chain node addresses).

[dmitry-markin]

When do we need this to be ready?

This should follow up for a proper decentralization. With IPFS DHT support we won't need to hardcode bulletin node addresses as they will be discoverable as any other content provider in IPFS.

[bkontur]

@dmitry-markin Do we expect any special hardware/software requirements to run Bulletin node?

[dmitry-markin]

@dmitry-markin Do we expect any special hardware/software requirements to run Bulletin node?

From what I know, we should keep the video proofs for two weeks (i.e., pruning depth is set to two weeks). Depending on the amount of proofs submitted within this period, the storage requirements can be quite substantial.