v0.10.12.x RC4 Testing

Status
Not open for further replies.

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,287
2,406
1,183
Germany
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!

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.
 
  • Like
Reactions: Light

thelonecrouton

Well-known Member
Foundation Member
Apr 15, 2014
1,135
813
283
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.
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.
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,287
2,406
1,183
Germany

thelonecrouton

Well-known Member
Foundation Member
Apr 15, 2014
1,135
813
283
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:
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...
 

Propulsion

The buck stops here.
Feb 26, 2014
1,008
467
183
Dash Address
XerHCGryyfZttUc6mnuRY3FNJzU1Jm9u5L
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
?
 

chaeplin

Active Member
Core Developer
Mar 29, 2014
749
356
133
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:
[email protected]:~/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
 
  • Like
Reactions: flare

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
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.
 

CODERsp

Member
Jul 5, 2014
114
35
78
Currently I have 7 darksend rounds and 2 collateral payments of 0.026 each. In wallet I have one faucet 1000 tDRK tx.
 

thelonecrouton

Well-known Member
Foundation Member
Apr 15, 2014
1,135
813
283
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).
I think Evan said that on main net the dev fund will get them all.
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,287
2,406
1,183
Germany
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
?
Unfortunately there is no command yet to stop GUI wallet from splitting 1000 DRK vin - but according to
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!
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:

Propulsion

The buck stops here.
Feb 26, 2014
1,008
467
183
Dash Address
XerHCGryyfZttUc6mnuRY3FNJzU1Jm9u5L
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.
 
  • Like
Reactions: flare

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,287
2,406
1,183
Germany
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.
Glad it worked, nevertheless it's a ugly workaround :D

EDIT: And now it even split my locked unspent... grrrr....
 

illodin

Member
Apr 26, 2014
122
71
78
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.
Ok, apparently the behaviour I was seeing is not intended: https://darkcointalk.org/threads/rc4-testing.1830/page-61#post-14890
 
  • Like
Reactions: flare

eduffield

Core Developer
Mar 9, 2014
1,084
5,319
183
****** 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
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
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
 

CODERsp

Member
Jul 5, 2014
114
35
78
v 15 - darkSend Status => not compatible with existing transactions.
 
Last edited by a moderator:

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,287
2,406
1,183
Germany
****** 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

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

CI-builds for v0.9.12.15


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

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

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

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


CI-builds for v0.10.12.15

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-4/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
 

MangledBlue

Well-known Member
Jun 28, 2014
1,246
678
183
USA
I was going to report the ver 14 this morning had ZERO collateral payments
Not sure if it's because I have 50Mb/s connection??
But yesterday night was the 1st time I could get on test net - LOVE it so far.
Gonna play with it all night tonight and tomorrow - no work tomorrow.
Hope there's somebody to play with tonight - lol

Great job Evan - will update to V15 tonight
 

Propulsion

The buck stops here.
Feb 26, 2014
1,008
467
183
Dash Address
XerHCGryyfZttUc6mnuRY3FNJzU1Jm9u5L
this will be sorted by CI builds

EDIT: Will need to invest in more CPU instances on AWS :D
Ha! Off topic, but you wouldn't believe the bill I received for my Masternodes on Amazon.
Will definitely have to look into other options...
 

Propulsion

The buck stops here.
Feb 26, 2014
1,008
467
183
Dash Address
XerHCGryyfZttUc6mnuRY3FNJzU1Jm9u5L
latestCoinControl.png
Wallet is now showing all of the addresses with funds in it in coincontrol. No denomination has taken place as of yet.
 

elbereth

Active Member
Dash Support Group
Mar 25, 2014
440
466
133
Costa Rica
dashninja.pl
Dash Address
XkfkHqMnhvQovo7kXQjvnNiFnQhRNZYCsz
tdrkmn01-08 updated to 0.10.12.15 (and masternode started).
tp2pool compiled from master-rc4 to 0.9.12.15.
Portchecker now indicates 0.9.12.15 and protocol version 70027.
 
Status
Not open for further replies.