• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

v0.10.12.x RC4 Testing

Status
Not open for further replies.
If I run masternode list from the console, my IPs are listed XXX.XXX.XXX.XXX,1 so I'm hoping that all is ok until I turn up in elbereth list! I won't be calm until they have though.
 
If I run masternode list from the console, my IPs are listed XXX.XXX.XXX.XXX,1 so I'm hoping that all is ok until I turn up in elbereth list! I won't be calm until they have though.

If console returns :1 then its all good
 
I am using the option



in my commandline, and this stops my QT RC4 client from denominating.

The information was hidden in one of Evans' release notes:

flare, someone on the btctalk thread claimed that disabling DS didn't work for him. I haven't tested this on v.27 so I'm not really sure. But I did test this on a previous version and it worked. Or to make sure after you disable DS, restart the wallet, it should work.
 
flare, someone on the btctalk thread claimed that disabling DS didn't work for him. I haven't tested this on v.27 so I'm not really sure. But I did test this on a previous version and it worked. Or to make sure after you disable DS, restart the wallet, it should work.
I am running v27 without any problems on disabling denom, but i did not use the GUI options dialog. Maybe that setting is ignored.

Using disabledarksend=1 works for me.
 
I am running v27 without any problems on disabling denom, but i did not use the GUI options dialog. Maybe that setting is ignored.

Using disabledarksend=1 works for me.

Noob question: How do you use this command line in windows wallet? I'm not sure which directory. Thanks.
 
Noob question: How do you use this command line in windows wallet? I'm not sure which directory. Thanks.
instead of starting darkcoin-qt.exe directly, create a shortcut to that file, and add the parameter to the Properties. (i do only have german screenshots at hand at the moment, but you should get the idea) :)

7bAj0zS.png
 
instead of starting darkcoin-qt.exe directly, create a shortcut to that file, and add the parameter to the Properties. (i do only have german screenshots at hand at the moment, but you should get the idea) :)

Ah hah! So cool, flare, i love this :) I don't have a MN (will put it back up but not now) so I had to take out "-datadir=.\drkmn01". Here's my screen:
upload_2014-8-14_11-53-54.png


and it does put a check mark on the gui to disable Darksend. Thanks!
 
I'm thinking if you disable Darksend before you run the wallet with the MN in it, it should be okay, but I'm not sure. The devs should have a clear instruction on this somewhere.

Maybe this has been answered already but V27 will not kill your MN
you just need the 1000DRK in any addy
and MN=1 in config file
:)
- even if you don't have a MN - it would still work :)
 
Maybe this has been answered already but V27 will not kill your MN
you just need the 1000DRK in any addy
and MN=1 in config file
:)
- even if you don't have a MN - it would still work :)

I can also confirm this. If you have masternode=1 in your conf file darksend WILL be disabled by default thus making sure that your 1000DRK will not be denominated.
 
I can also confirm this. If you have masternode=1 in your conf file darksend WILL be disabled by default thus making sure that your 1000DRK will not be denominated.
Yeah, but if you need a new masternodeprivkey you need to set masternode=0 first AFAIK - so it could turn out to be inconvenient to rely on implicit disabling denom.

I will stick to explicitly disabling it ;)
 
ready for some testing ? :)

From Evan : https://bitcointalk.org/index.php?topic=421615.54320

****** PLEASE UPDATE TO v9.12.28 (Stable) OR 10.12.28 (RC) *******

The unconfirming issue was caused by DS going too fast once and awhile and the view not being able to keep up with what inputs were spent. This caused double spends in about 2% of cases. To fix this I've introduced a limit where darksend will only denominate once a block.

If you have a long standing unconfirmed transaction, simply right click the transaction, copy the txid. Then execute the command "erasetransaction txid" in the console. After that reopen the client with the command -salvagewallet, and the money should be back.

It will still be possible to mix with clients that haven't updated, so avoid activating darksend for a day or so while the network updates. This update is backwards compatible, so masternodes need not update.

Source: Compile if you are running a pool, exchange, etc.

https://github.com/darkcoinproject/darkcoin

9.12.28 (Stable) Binaries: Does not include Darksend

Windows.exe: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/darkcoin-0.9.12.28-win.zip
Windows installer: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/darkcoin-0.9.12.28-win32-setup.exe
Mac OSX: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/darkcoin-0.9.12.28-osx.dmg
Linux: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/darkcoin-0.9.12.28-linux.tar.gz

10.12.28 (RC) Binaries: Includes Darksend - Masternode Operators

Windows .exe: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/rc/darkcoin-0.10.12.28-win.zip
Mac OSX: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/rc/darkcoin-0.10.12.28-osx.dmg
Linux: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/rc/darkcoin-0.10.12.28-linux.tar.gz
 
Status
Not open for further replies.
Back
Top