-M gctwh
to the Command field under Execution Command. This will load only the ScPrime modules necessary for providing, and should help long term stability and leanness. If you’re using non-standard ports, this should also be added here using the additional flags --host-addr :4292 --host-api-addr :4293
or whichever ports you chose to use.sudo docker ps
should return the container name, which is used in the next command, sudo docker exec container_name spc
to see the status of the blockchain sync. This first-time sync can take several hours, as it is catching up with 3+ years of blocks. Compare the height of your sync to the current latest height on the explorer. You can continue with setup while your new node is syncing.spc
(ScPrime console) commands, just with sudo docker exec scprovider
in front of them. Generate the provider wallet with sudo docker exec scprovider spc wallet init
which will output a private key/seed. You must protect this seed at all times, as it is the only way for you (or anyone else) access your wallet. Once this has been recorded somewhere safe, count the number of words recorded. It should be 28 or 29 words long. If this is correct, return to the Docker Containers menu and stop the running container by clicking the slider. Then click the now-stopped container, go to Edit->Environment, and paste your seed words in to the SCPRIME_WALLET_PASSWORD value. This will allow the image to unlock the wallet upon finishing starting up, but take caution as you must now protect access to the NAS control panel as well. Apply and start the container again.sudo docker exec scprovider spc wallet unlock
should be able to unlock the wallet (if not done by default). Confirm that sudo docker exec scprovider spc
returns the wallet status is unlocked.-it
flag (i.e. sudo docker exec -it scprovider spc wallet unlock
) should return a more detailed explanation as to what the issue is. Using the help flag (-h)
can also help you navigate what wallet commands are available (i.e. sudo docker exec scprovider spc wallet -h
).sudo docker exec scprovider spc host folder add /scp1_1 2000gb
. One must take great care not to over-allocate space. Disks (for reasons googleable) typically have lower usable space than advertised. Because of this overhead, and because the docker image and metadata folders are all on volume 1, do not allocate all the available space (and certainly not all the advertised space) for scprime to use. In this example, though disk 1 is advertised as 12 TB, you may have noticed under Storage Manager that only 10.8 TB is usable.sudo docker exec scprovider spc host folder -h
will show what the available commands are. Again, you can add -h
or -v
(for verbose) to the end of most commands to see how they are used or get additional information returned.sudo docker exec scprovider spc host
should return something like the following image. This command (often with -v
) in particular is one you will use often as a provider, as it returns a summary of your provider’s config and status. sudo docker exec scprovider spc host config maxduration 9w
sudo docker exec scprovider spc host config collateral 5SCP
sudo docker exec scprovider spc host config minstorageprice 5SCP
sudo docker exec scprovider spc host config mindownloadbandwidthprice 1SCP
sudo docker exec scprovider spc host config minuploadbandwidthprice 1SCP
sudo docker exec scprovider spc host config collateralbudget 500SCP
sudo docker exec scprovider spc host config maxcollateral 200SCP
sudo docker exec scprovider spc wallet address
and know that this command will generate a new, equally valid address every time it is used. Your wallet ultimately consists of many addresses all belonging to your private key/seed. Copy the produced address and send some balance to it.sudo docker exec scprovider spc wallet balance
which should return the state of the wallet. If the blockchain is still syncing, the balance will not appear yet. If it was just sent but not yet included in a mined block, it will appear as an Unconfirmed Delta.sudo docker exec scprovider spc host announce
which will announce using the external IP automatically resolved by the gateway module, and with the default host entry port (4282). If a dynamic DNS is used, the non-default ports are being used, or the gateway module is unable to properly resolve an external IP, this is expanded to sudo docker exec scprovider spc host announce external_IPv4:4282
or whichever host-addr port was decided earlier. If you don't know your external IPv4, you can easily get it from a site such as WhatIsMyIP.sudo docker exec scprovider spc host
or the more verbose sudo docker exec scprovider spc host -v
but external validation is the best way to know with certainty that everything looks good.