Re: ★★DigiByte|极特币★★[DGB]✔ DigiSync v6.14.2 - DigiSpeed

Quote from: Jumbley on November 27, 2017, 09:02:29 PM

OK, I stand corrected! Grin

While we are here, can we go into this a little further and spell out where and what changes Ian will need to make please?

I can see how the above conversation could lead to more mining on the DigiByte network.
I know how so many people hate asking questions but cant wait to hear the answers, so they can try things for themselves without looking foolish.
Grin

Oh by the way this is an open question, anyone with the answers can butt in and explain with their community spirit. It doesn't have to be Jared who possibly just went to bed at 5am, if he's in HK. Wink

Once you have 5 data directories setup you can make a shell script like below:

Code:

digibyted --datadir=/root/data/sha256d/
sleep 2
digibyted --datadir=/root/data/scrypt/
digibyted --datadir=/root/data/qubit/
sleep 2
digibyted --datadir=/root/data/skein/
sleep 2
digibyted --datadir=/root/data/groestl/

Note: calling digibyted only works to start wallet. To execute commands run a script like below by calling "digibyte-cli":

Code:

/root/digibyte/src/digibyte-cli -datadir=/root/data/sha256d/ stop
sleep 2
/root/digibyte/src/digibyte-cli -datadir=/root/data/scrypt/ stop
sleep 2
/root/digibyte/src/digibyte-cli -datadir=/root/data/qubit/ stop
sleep 2
/root/digibyte/src/digibyte-cli -datadir=/root/data/skein/ stop
sleep 2
/root/digibyte/src/digibyte-cli -datadir=/root/data/groestl/ stop

Each instance of digibyted needs to run on a different RPC port. What we do is we run 4 out of the 5 algos with the "prune=550" command to keep from bloating the server. All data comes from one algo and gets relayed to other 4 algos locally.

Example Sha256 config:

Code:

rpcuser=user
rpcpassword=password
port=14012
rpcport=14011
daemon=1
server=1
algo=sha256d
maxconnections=500
prune=550

The prune=550 command purges data beyond 550mb of the most recent blocks and txs. It is not enabled be default.