• 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.
Good morning! Windows wallet v.21 still has this problem:

upload_2014-8-12_9-51-27.png


As you can see, there are 0 Anonymous DRK, and plenty of Non-Anonymous DRK but it won't send. Funny thing is if I use "No Preference" then it will send.

Edit: I use the same wallet.dat with the money left over from the previous version.
 
V.21 will only allow me to input 9999DRK in the Option>Main>Amount of Darkcoin to keep anonymized

Is that suppose to be like that?
I thought the "limit" was lifted.
 
(To Be Cont'd)... So, because my wallet would not do anymore denomination with that amount, and I could not send by using "Non-Anonymous funds", I went in option and disabled DS. Restarted the wallet and to my surprise this is what I got:

upload_2014-8-12_10-50-7.png


All of the coins suddenly got anonymized!

Edit: And I was able to Darksend some coins away (using Anonymous Funds) despite the DS feature is disabled.
 
Last edited by a moderator:
Anybody else's wallet taking a long time to start denominating?

Used an existing wallet.dat and started up the new version (in windows) -- set the number of rounds to 5 and the min anon funds value to over my total wallet balance -- send some coin between wallets then have waited about 20 minutes to this point. Whereas previous versions I got my first denomination fee within 5 minutes, with this version both wallets show no action.

Issue? Or am I not aware of something that needs to be done to get the newest version to start denomination?

I see a lot of "entries(1/2)" and "waiting for more entries(1/2)" in the status readout...
My wallet is still having that problem
 
Code:
2014-08-12 14:56:53 dssu - message doesn't match current masternode - [::]:0 != 211.99.224.173:19999

Does anyone still get this message? I am getting this on my MN running v0.10.12.21-beta (flare's build 20).
The MN config is
Code:
rpcuser=darkcoinrpc
rpcpassword=<REMOVED>
daemon=1
testnet=1
onlynet=IPv4
masternode=1
masternodeprivkey=<REMOVED>
masternodeaddr=66.172.33.248:19999
 
Code:
2014-08-12 14:56:53 dssu - message doesn't match current masternode - [::]:0 != 211.99.224.173:19999
Does anyone still get this message? I am getting this on my MN running v0.10.12.21-beta (flare's build 20, linux 64-bit).
 
Code:
2014-08-12 14:56:53 dssu - message doesn't match current masternode - [::]:0 != 211.99.224.173:19999
Does anyone still get this message? I am getting this on my MN running v0.10.12.21-beta (flare's build 20, linux 64-bit).
Yes I have a lot of that in my debug log.
 
Another issue with the GUI causing weird behavior of the client. Tested wit Win32, 0.10.12.21:
The number of darksend rounds in settings resets to 1 with every client restart. (Should the minimum number of rounds not be 2?)
With this wrong setting, I got some change (22 tDRK) to denomitate. After one successful round the corresponding inputs were locked and the client tried to process round 2. After 4 hours and 6 unsuccessfull denomitation rounds with fees, I stopped the client.
Directly after restart, the amount of anonymized funds increased by 22 tDRK. Everything seemed to be ok now. But If I check the inputs with coin control, the 22 tDRK are still at 1 round, leaving them unready for anonymous transfers.

Edit: It looks like the fallback to 1 round setting only takes place if darksend disabled is checked.

Edit2: After correction of the settings,enabling darksend and watching 5 more denominate transactions with fees, my 22 tDRK change is at 2 rounds. Looks like the anonymized balance sometimes includes even funds denominated once.
 
Last edited by a moderator:
Looks like evan did some changes within the last hour. Denominating is working again for my wallet

Finally 3000 tDRk anon after 9h with rounds = 4 and no more the 0.001DRK transaction fees for a single one ( V10.12.21 )
It stuck around 4-5 h without doing nothing
 


I didn't say I can follow, and didn't write any specific address.


I suggest fee has problem. Fee use changed address again and again.
(0.125 -> 0.124 --> 0.123 -->....)

I think anonymous transactions and darksend rounds should use denominated 0.01 for fee not 0.125.
 
Last edited by a moderator:
****** Please Update To 10.12.22 or 9.12.22 *******

All fees will use 0.001 sized inputs (they have no change so you can't follow them), all transactions now should look like this one: http://test.explorer.darkcoin.fr/tx/ce0ea2bdf630233955d459489b6f764e0d0bbe9e8a62531dd2a14b455626b59c

- Client now creates fee sizes inputs for use in darksend denomination phases to improve anonymity
- new rpc command erasetransaction. Some users have reported non-confirming transactions due to opening their wallet at multiple locations. This can and will create double spent transactions that will not confirm. erasetransaction is for removing them.
- SplitUpMoney can only execute every 10 blocks now.
- removed matching masternode debugging messages, that's not really an error
- Client now prioritises sending denominated funds back into Darksend. This will improve anonymity and help to respect the "anonymize darkcoin" amount in the configuration.
- fixed a bug where masternodes send failed transactions
- changed max to 100k in configuration
- added a warning message to startup (delete ~/.darkcoin/.agree_to_tou to see it)
- found a bug causing inputs to get locked forever.
- Darksend now checks diskspace before sending anything to a masternode.
- incrementing protocol version to knock all old clients off

Stable Binaries
http://www.darkcoin.io/downloads/master-rc4/darkcoin-qt
http://www.darkcoin.io/downloads/master-rc4/darkcoind

RC4 Binaries ( masternodes / auto-denom )
http://www.darkcoin.io/downloads/rc4/darkcoin-qt
http://www.darkcoin.io/downloads/rc4/darkcoind
 
****** Please Update To 10.12.22 or 9.12.22 *******

All fees will use 0.001 sized inputs (they have no change so you can't follow them), all transactions now should look like this one: http://test.explorer.darkcoin.fr/tx/ce0ea2bdf630233955d459489b6f764e0d0bbe9e8a62531dd2a14b455626b59c

- Client now creates fee sizes inputs for use in darksend denomination phases to improve anonymity
- new rpc command erasetransaction. Some users have reported non-confirming transactions due to opening their wallet at multiple locations. This can and will create double spent transactions that will not confirm. erasetransaction is for removing them.
- SplitUpMoney can only execute every 10 blocks now.
- removed matching masternode debugging messages, that's not really an error
- Client now prioritises sending denominated funds back into Darksend. This will improve anonymity and help to respect the "anonymize darkcoin" amount in the configuration.
- fixed a bug where masternodes send failed transactions
- changed max to 100k in configuration
- added a warning message to startup (delete ~/.darkcoin/.agree_to_tou to see it)
- found a bug causing inputs to get locked forever.
- Darksend now checks diskspace before sending anything to a masternode.
- incrementing protocol version to knock all old clients off

Stable Binaries
http://www.darkcoin.io/downloads/master-rc4/darkcoin-qt
http://www.darkcoin.io/downloads/master-rc4/darkcoind

RC4 Binaries ( masternodes / auto-denom )
http://www.darkcoin.io/downloads/rc4/darkcoin-qt
http://www.darkcoin.io/downloads/rc4/darkcoind
CI-builds for v0.9.12.22-g2e35234

Windows 32bit:
http://bamboo.darkcoin.qa/artifact/DWD-DRK/QTL/build-97/gitian-win-darkcoin-bin/32/darkcoin-qt.exe
http://bamboo.darkcoin.qa/artifact/...tian-win-darkcoin-bin/32/daemon/darkcoind.exe
http://bamboo.darkcoin.qa/artifact/...oin-bin/32/darkcoin-0.9.12.22-win32-setup.exe

Mac OS X:
http://bamboo.darkcoin.qa/browse/DOD-DRK-81/artifact/QTL/gitian-osx-darkcoin/DarkCoin-Qt.dmg

Linux 32bit:
http://bamboo.darkcoin.qa/artifact/BL-DRK/QTL/build-76/gitian-linux-darkcoin-bin/bin/32/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/BL-DRK/QTL/build-76/gitian-linux-darkcoin-bin/bin/32/darkcoind

Linux 64bit:
http://bamboo.darkcoin.qa/artifact/BL-DRK/QTL/build-76/gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/BL-DRK/QTL/build-76/gitian-linux-darkcoin-bin/bin/64/darkcoind

CI-builds for v0.10.12.22-g0c9e20d

Windows 32bit:
http://bamboo.darkcoin.qa/artifact/...arkcoin-rc-darkcoin-qt-bin/32/darkcoin-qt.exe
http://bamboo.darkcoin.qa/artifact/...coin-rc-darkcoind-bin/32/daemon/darkcoind.exe

Mac OS X:
http://bamboo.darkcoin.qa/browse/DOD-DRKRC-18/artifact/QTL/gitian-osx-darkcoin-rc/DarkCoin-Qt.dmg

Linux 32bit:
http://bamboo.darkcoin.qa/artifact/...tian-linux-darkcoin-rc-bin/bin/32/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/...gitian-linux-darkcoin-rc-bin/bin/32/darkcoind

Linux 64bit:
http://bamboo.darkcoin.qa/artifact/...tian-linux-darkcoin-rc-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/...gitian-linux-darkcoin-rc-bin/bin/64/darkcoind
 
****** Please Update To 10.12.22 or 9.12.22 *******

All fees will use 0.001 sized inputs (they have no change so you can't follow them), all transactions now should look like this one: http://test.explorer.darkcoin.fr/tx/ce0ea2bdf630233955d459489b6f764e0d0bbe9e8a62531dd2a14b455626b59c

- Client now creates fee sizes inputs for use in darksend denomination phases to improve anonymity
- new rpc command erasetransaction. Some users have reported non-confirming transactions due to opening their wallet at multiple locations. This can and will create double spent transactions that will not confirm. erasetransaction is for removing them.
- SplitUpMoney can only execute every 10 blocks now.
- removed matching masternode debugging messages, that's not really an error
- Client now prioritises sending denominated funds back into Darksend. This will improve anonymity and help to respect the "anonymize darkcoin" amount in the configuration.
- fixed a bug where masternodes send failed transactions
- changed max to 100k in configuration
- added a warning message to startup (delete ~/.darkcoin/.agree_to_tou to see it)
- found a bug causing inputs to get locked forever.
- Darksend now checks diskspace before sending anything to a masternode.
- incrementing protocol version to knock all old clients off

Stable Binaries
http://www.darkcoin.io/downloads/master-rc4/darkcoin-qt
http://www.darkcoin.io/downloads/master-rc4/darkcoind

RC4 Binaries ( masternodes / auto-denom )
http://www.darkcoin.io/downloads/rc4/darkcoin-qt
http://www.darkcoin.io/downloads/rc4/darkcoind

Warning message needs 'of' imo

Darksend uses a very large keypool and goes through keys quite rapidly. This means that you need to make backups more frequently than with other wallets, because when it anonymizes your funds a lot transactions happen in the background. To be safe make a new backup after each time your anonymized threshold of funds is reached.

Sound better?

Darksend uses a very large keypool and goes through keys quite rapidly. This means that you need to make backups more frequently than with other wallets, because when it anonymizes your funds a lot of transactions happen in the background. To be safe make a new backup after each time your anonymized threshold of funds is reached.
 
masternode list in qt client coming up empty on v0.10.12.22-beta

edit: deleted everything except wallet.dat in testnet3 folder and after resync looking better
{
"108.61.84.37:19999" : 1,
"54.183.79.141:19999" : 1,
"54.191.87.83:19999" : 1,
"54.208.138.69:19999" : 1,
"149.255.109.167:19999" : 1,
"54.64.7.206:19999" : 1,
"184.73.179.196:19999" : 1
}
 
Last edited by a moderator:
Status
Not open for further replies.
Back
Top