1.6 Storage node

Storage node

The storage node needs several command line options

1. -d ~/publiqpp_testnet.storage - this sets a data directory for the publiqd node. This is where all the working files will be stored.
2. -k 5Jo6zDAqZLRnSbQfSsRPK65RxuPFVNnJRBWCCaxvnYTq3cDafEa - an example private key. This address needs to hold 10.000 PBQ in order for the storage to be functional.
3. -r 127.0.0.1:14106 is the RPC endpoint that can control the node.
4. -s 0.0.0.0:14108 is the storage server endpoint, where the node listens for connections.
5. -a storage.publiq.host:14108 this is the public internet address that is forwarded to -s endpoint Then every other node in the network, from time to time, will check that this endpoint is indeed able to provide cryptographic signature.
6. -A storage.publiq.host:14107 this endpoint is configured for reverse proxy such as nginx to process https requests and forward to same -s endpoint. This endpoint is also being broadcast to all nodes in the network.
   in case of nginx be sure to have proxy_http_version 1.1; specified in the configuration.
7. -t storage - tells the node to broadcast itself to the blockchain as a storage node. Also this node autonomously broadcasts service statistics to the blockchain.
8. -f 10000000 - we configure the storage autonomous transactions fees. the unit is 10 to -8 power PBQ.

The storage node works mostly autonomously. It tracks each file created as part of the story and then duplicates the file to its own storage (~/publiqpp_testnet.storage/storage). Then it broadcasts to the blockchain that it is ready to serve the file. Also periodically, it tracks its own file server activity and broadcasts service statistics transactions.

publiqd -i 0.0.0.0:14105 -r 127.0.0.1:14106 -a north.publiq.network:14108 -A north.publiq.network:14107 -s 0.0.0.0:14108 -d ~/publiqpp_testnet.storage -k 5Jo6zDAqZLRnSbQfSsRPK65RxuPFVNnJRBWCCaxvnYTq3cDafEa --testnet -t storage -f 10000000