Storage network transport optimization: use HTTP protocol instead of P2P protocol

[0xbillw]

Existing Problems

Currently, CESS's storage network protocol stack uses 'libp2p', but the main business scenarios have not increased efficiency due to the use of 'libp2p'. For example, the transmission of file data blocks is designed in such a way that data is transferred only between two nodes, not shared with other nodes to create a BitTorrent-like effect that accelerates transmission. In addition, due to the use of the address discovery, reporting, and subscription features of 'libp2p', additional traffic will be generated for storing miners. These functions are unnecessary in the current design, as the meta-information of the storage miners can be obtained on-chain.

Proposed Solution

1. Remove the libp2p library;
2. Remove the 'bootnode' service of the storage network, and directly report the address information of the storage miners to the chain;
3. Replace the data block transmission with other protocols, such as the simple HTTP protocol;

Remaining Issues

1. There is a risk of exposing the addresses of storage miners. One of the initial reasons for using libp2p was the belief that exposing only the PeerId of storage miners on-chain would be beneficial for their security. While this approach means we cannot directly obtain the addresses of storage miners, it does not meet the requirements for address security. As long as an attacker can establish a connection with a storage miner, they can still obtain their address. If the need to conceal the addresses of storage miners is reasonable and strong, this should be considered at another level. For example: address encryption, using privacy networks like I2P or TOR.

Repositories or Modules That May Be Involved

• cess chain runtime related
• cess-miner
• DeOSS
• cess-sdk-go
• cess-sdk-rust
• cess-sdk-js
• Other downstream code that depends on the Cess SDK

Tasklist

• [ ] CESSProject/cess-miner#289
• [ ] CESSProject/config-gen#28
• [ ] CESSProject/cess-nodeadm#46
• [ ] CESSProject/cess#404
• [ ] To update documents related to storage-miner

[democ98]

CESS faucet also rely cess-go-sdk,if there are any function change like doing transaction or event listening which faucet related,pls let me know