• 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.
stonehedge said:
Not strictly an RC4 issue but I was actuallly referring to this problem with the Mac wallet. Its a font packaging issue I think. I completely agree that the n/a is disconcerting too though!

screen-shot-2014-07-09-at-11-31-23-am-png.219
Click to expand...
Thanks for the report, this is fixed in RC4 https://github.com/darkcoinproject/darkcoin/pull/26

Will have a chat with Evan if we push 0.9.11.7 and 0.10.11.7 for Mac users to the darkcoin.io site today.
 
illodin said:
Can you explain it to me like I'm 80. If I have 100 addresses in my wallet, each address has 1 anonymized coin, and I send one of them. How does that "de-anonymize" the other 99? There must be something I'm missing in how bitcoin really works I should probably read the basics lol.
Click to expand...
No, in the case that you want to send 11DRK and you select for example under coin control anonymised inputs of 10, 1, and 1 (just in case, to cover any fees) then sending those shouldn't render the rest of your balance deanonymised. But upon having received that 11DRK, you'd want to have it DS+'d again to preserve anonymity when you come to spend them yourself.
 
BelStar said:
Please have a look at this darksend transaction: http://test.explorer.darkcoin.fr/tx/a12d1f2eb5afc216c81616cc150196c7d70dcae1d3bd19e967f262707f78fe67
I have basically sent 123.4567891 tDRK using anonymous funds but it seems that all available anonymized inputs of my wallet were sent and I am getting 3929.53121167 tDRK back to a change address?
screencaps:
Click to expand...
Had you selected all your anonymised inputs under coin control? Or did you get 3900DRK out of nowhere, because that would be a big exploit...
 
Trying to launch a masternode currently. Using wallet version 10.12.14.
To prevent the denomination on the single 1000 input, what command do I use for no denomination in the config file - is it :
Code: 
nodenomination=1
?
 
I have made a script to check whether collateral is caused by specific MN.

Looks like collateral tx is fixed to specific address(for checking).


Code: 
darktest@sv1:~/collateral> ./run.py 9660 10140
block: 9660, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9660, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9662, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9662, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9662, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9663, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9663, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9669, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9672, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9679, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9696, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9696, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9709, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9711, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9713, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9718, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9718, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9722, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9723, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9737, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9738, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9747, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9748, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9752, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9760, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9777, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9787, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9787, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9789, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9796, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9797, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9801, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9807, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9814, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9814, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9814, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9829, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9830, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9832, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9832, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9835, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9836, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9837, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9837, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9839, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9839, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9849, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9854, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9873, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9878, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9881, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9887, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9887, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9888, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9888, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9898, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9909, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9909, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9925, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9952, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9952, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9961, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9969, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9992, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 9993, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 10002, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 10005, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 10006, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 10007, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 10035, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 10040, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 10046, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 10049, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 10050, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 10080, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 10094, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 10096, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 10096, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 10098, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 10101, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 10102, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 10112, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 10117, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 10127, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
block: 10136, toadress: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf, toamount: 0.025
 
Update on my part: Got another fresh windows wallet, made sure got the darkcoin.conf file before I started to run the wallet so it would not go to main net ... Got 10k tdrk and I let it do its job over night. Still got 3 collateral fees this time.
 
Currently I have 7 darksend rounds and 2 collateral payments of 0.026 each. In wallet I have one faucet 1000 tDRK tx.
 
Propulsion said:
Trying to launch a masternode currently. Using wallet version 10.12.14.
To prevent the denomination on the single 1000 input, what command do I use for no denomination in the config file - is it :
Code: 
nodenomination=1
?
Click to expand...
Unfortunately there is no command yet to stop GUI wallet from splitting 1000 DRK vin - but according to
Lariondos said:
Tested with fresh wallet.dat. The first 1000 tDRK transaction gets splitted, the second stays intact. So here's my vote for a GUI switch!
Click to expand...
there is a chance that a second 1000 DRK vin does not get split in the first round :D

After that you can lock your 1000 DRK vin via coin control.

upload_2014-8-6_18-15-29.png
-->
after.PNG


additionally add

Code: 
darksendrounds=0
enabledaemondarksend=false

to your darkcoin.conf

HTH
 
Last edited by a moderator:
flare, correct, second tx did not become splitted. Sent the 1000 in change addresses back to the first generated wallet address and successfully started the MN.
 
Propulsion said:
flare, correct, second tx did not become splitted. Sent the 1000 in change addresses back to the first generated wallet address and successfully started the MN.
Click to expand...
Glad it worked, nevertheless it's a ugly workaround :grin:

EDIT: And now it even split my locked unspent... grrrr....
 
thelonecrouton said:
No, in the case that you want to send 11DRK and you select for example under coin control anonymised inputs of 10, 1, and 1 (just in case, to cover any fees) then sending those shouldn't render the rest of your balance deanonymised. But upon having received that 11DRK, you'd want to have it DS+'d again to preserve anonymity when you come to spend them yourself.
Click to expand...
Ok, apparently the behaviour I was seeing is not intended: https://darkcointalk.org/threads/rc4-testing.1830/page-61#post-14890
 
****** Please Update To 10.12.15 or 9.12.15 *******

We shouldn't see anymore collateral fees now, plus processing large amounts of funds will go MUCH faster. Try to make a wallet with 5000-100k DRK and let it run, let's see how well this works now.

- Added session IDs for masternode communication. Clients were getting confused when they got messages about other sessions (sometimes happened when they all jumped on the same masternode at once)
- Added a pre-session state where the client will query a random masternode and ask if they can perform a merge on N darkcoin without giving any other information. If that amount is compatible without losing anonymity, the client will then add it's entry for merging
- Added code to randomly use the top 20 masternodes, this can dynamically be increased as more transaction traffic starts to happen (although it's not implemented but it could be done later)
- After successful transactions clients will now automatically attempt another session on a random masternode, then repeat until they get any kind of error or run out of funds that need to be processed.
- Fixed a change address reuse issue
- Fixed an issue with the compatible join algorithm (Masternodes will only join the same denominations, this wasn't always the case before)
- Inc protocol to kick old users odd again

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
 
I've been getting the following error quite often, which makes the wallet not to send the coins, but after that the wallet still gets denominate and collateral fees:
upload_2014-8-6_14-23-2.png

upload_2014-8-6_14-26-40.png
 
v 15 - darkSend Status => not compatible with existing transactions.
 
Last edited by a moderator:
Status
Not open for further replies.
Back
Top