v0.10.17.x Testing

Status
Not open for further replies.
It is not the same computer as with cold wallet for MN. I want to set it not as "local/remote" but only on local...
 
It is not the same computer as with cold wallet for MN. I want to set it not as "local/remote" but only on local...
darkcoin.conf should look like that:
It's for hot one

testnet=1
rpcuser=anything
rpcpassword=anything
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=256
masternode=1
masternodeprivkey=masternode genkey
 
Last edited by a moderator:
It is not the same computer as with cold wallet for MN. I want to set it not as "local/remote" but only on local...
oh.. then make sure your local firewall has port 19999 open and you have line "testnet=1" in config
 
rpcuser=..........................
rpcpassword=.............................
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=256
masternode=1
masternodeprivkey=.........................
addnode=23.23.186.131

and run with -testnet -conf......
 
i think he also needs ''masternodeaddr=hisserveripadress:19999'' in his darkcoin.conf ?
that is if he is starting from cold wallet...
 
  • I did 1000DRK / 8 Rounds with the v0.10.16.16 wallet some days ago, result was a Darksend balance of 999.something tDRK or so.
  • installed v0.10.17.0, opened it, everything's fine
  • Mined a couple of tDRK at P2P-pool
  • Enabled Darksend mixing -> 99.00000018 tDRK available before it even started mixing. Where's the rest gone?
Edit:
Got it: eduffield mentioned here that the larger denominations (500 DRK and 100 DRK) are gone with v0.10.17.0.

999 - 500 - 4x100 = 99 DRK

Shouldn't those 500 DRK and 100 DRK stay denominated?
 
Last edited by a moderator:
im about to start a testnet masternode on the same server my mainnet masternode is running. Is this going to workout? :)
 
Can anyone else see MN 176.126.241.100? It thinks it's valid and it's on its own list, but my local QT isn't picking it up.
 
of the 7 clients of mine thats doing Darksend mixing i have 1 client thats getting hit with 0.1 fees a bit too often for my taste :

VWNdKql.jpg
 
anybody running two darkcoin daemons on one server could use this script daemon.sh:

#!/bin/sh
./darkcoind -testnet -datadir=/home/user/.darkcoin-testnet -conf=/home/user/.darkcoin-testnet/darkcoin.conf $1

and then execute things like
sh daemon.sh getinfo
or
sh daemon.sh "getaccountaddress 0"
 
Hmm, don't think I've done anything wrong or different from usual.

Code:
root@crouton6:~/.darkcoin# ./darkcoind masternode start
successfully started masternode
root@crouton6:~/.darkcoin# ./darkcoind masternode list
{
  "64.251.69.134:19999" : 1,
  "50.254.73.146:19999" : 1,
  "50.254.73.147:19999" : 1,
  "50.254.73.148:19999" : 1,
  "50.254.73.149:19999" : 1,
  "176.126.241.100:19999" : 1
}
 
found a problem with mixing.. a large amount (826.97 in my case) is excluded from mixing and my wallet actually thinks its finished now
(constant idle status)

edit : found it on a second client as well...
edit : actually on several clients now .. didnt notice it untill some got to that 100% .. with
every 1000 wallet for mixing the amount 800-830 gets excluded from mixing.....

4d4MyPc.jpg

jDWiDat.jpg
 
Last edited by a moderator:
Status
Not open for further replies.
Back
Top