v0.11.0 - Darkcoin Core Release

camosoul

Grizzled Member
Sep 19, 2014
2,263
1,130
1,183
Lols, the irony... It's usually me having the problems nobody else has. Now, everyone else is having problems and mine are all working fine...

this not-quite-a-fork situation is not going to resolve until people get their butts on 0.11...
 
  • Like
Reactions: fernando

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
No I am talking about this:

1.) Tx "caa2111b924b44437cce277f939f5d177b3ad96acce8bcb6d006f9e193602bf4" is splitting 350 DRK to get ready for DS

2.) Tx "b6b285ffbcc23db6e8c9e817378372fc47e7423d84e1b1af5d84c000d0e848e9" is DS round 1 for these funds. The 349.575 DRK are the biggest input. The output 227.47499967 DRK is the biggest output and is bigger than all other inputs, making it highly likely it is a change of the 349.575 DRK input. This can further be verified by looking at the mDRK numbers (which indicate relations between inputs/outputs if the amount of potential DS denominations is taking into account). So We got the change of this address.

3.) Tx "d6837f60aa13bfe02b9feea8509a1a96904927f7569cc29f29e45906291f87df" Uses out 227.47499967 DRK as input. It is very interesting that we also have an output of 227.47499967 DRK. This means the 227.47499967 DRK have not been mixed at all and should not have entered this DS Tx, This is an obvious design error. Furthermore, that tells us that it is highly likely that other smaller denominations derived from the initial input of 349.575 DRK in 2.) participated here. This becomes even more likely when looking at the Transaction the inputs for 3.) came from as we can see 2.) there not only for the 227.47499967 DRK input, but also for some DS denominations.

4.) Tx "366059bd66989564fb3f8dca5bf5144bae1b4cc21ade403a6cae3ca052804eaf" Is an easy one. Same this as above. This time only 285.82489983 DRK get transacted in total, with 227.47499967 DRK coming from 3.) Since there is an output of 215.37499945 DRK is can be easily linked. Also, there have been some DS denominations from 3.) and therefore also from 2.) mixed in this.

This means that with 4.) we have some freshly denominated coins that will only have 1 DS round and this is handled correctly by the client. However, we have also some denominations that we had in 2.) and WE KNOW THAT. These coins are marked with 3 DS rounds in the client, but in reality they only have the anonymity of a single round since we know they are involved.

This is why we need smaller non-denominated outputs, or even better, no non-denominated outputs at all.

When splitting the initial 350 DRK, why not split them into DS denominations? That way, this kind of tracking is not easily possible. Also, PLEASE finally make denominations convertible (removing 1 duff from all DS denominations). That way we have more liquidity since a 100 denom will not have to wait for other 100s, but can mix with 10s since it can be converted to 10s. With the current DS denomination system, it would lack 9 duffs and could simply not do this.

An additional suggestion is to make DS payments through a DS Tx possible. Because of the dead change issue we already have round up to the smallest denom when sending DS funds, so this wouldn't make it cost more.
When I want to send 5 DRK to someone, I could tell by client to do this but use a Darksend Tx for it. That means it would take a 10 denom, start a DS request with outputs of 1s, and once it is accepted it would send 5 DRK to the receiver and 5x1 DRK (DS denom) to 5 different addresses of mine. There could also be other coins of mine mixed in this Tx.
It would get rid of the extra Tx to send the coins since I mix my coins anyway, it is a lot harder to trace and it reduces bloat since there is no extra payment Tx in addition to the DS Tx.

The only disadvantage is that it would take longer because I would have to find ppl to mix with the moment I want to pay. However, with more and more adoption the waiting times will be reduced. Plus this can be optional. You can always pay the usual way if you want it to be fast.


Edit: Also, please change the recombining of DS denoms. It is like a soft reset of the already gotten anonymity especially when used in conjunction with the problem above =/

I feel like DS is now less safe than before =/
I'm wondering because of the hard fork we're having, DS wasn't working properly in splitting that amount 227.47499967 DRK.. I'll wait until everybody has updated and we'll see.
 
  • Like
Reactions: fernando

Aswan

Member
Jun 26, 2014
68
216
73
I'm wondering because of the hard fork we're having, DS wasn't working properly in splitting that amount 227.47499967 DRK.. I'll wait until everybody has updated and we'll see.
Maybe that one Tx, but that does not invalidate all the other issues I have brought up. I hope they can get fixed =/
 

camosoul

Grizzled Member
Sep 19, 2014
2,263
1,130
1,183
To help this process go more quickly...

delete your blocks and chainstate folders

remove peers.dat every time you restart the qt

restart the qt every time you get a whole lot of rejected/orphan blocks while pulling a completely new chain

Once you finally get a full chain, "cd ~/.darkcoin && scp -C -r blocks/ chainstate/ [email protected]:~/.darkcoin/"

This assures that all the masternodes get the correct chain without each one haveing to pull it, restart, delete peers.dat, etc just like the qt. You manually propagate a known good chain to all of your nodes so they can share it, and also so you don't have to fight like a bitch to get them all to pull on their own. Now all of your masternodes are sharing only known good chaindata.

Getting miners and pools to update will stop the monkeywrenching...
 
Last edited by a moderator:

ourlink

Well-known Member
Foundation Member
Jun 9, 2014
237
65
188
Heartland, USA
www.p2poolmining.us
All 3 of my p2pool nodes are up and running on Darkcoin Core version 11.00.07 with no issues!

Great job guys, now if I could only get the Windows 64 Bit wallet to work for my cold storage then I could call it a complete success. I had to fall back to using the 32 bit client to get the thing to synch and not shutdown.
 

Aswan

Member
Jun 26, 2014
68
216
73
My DRK client now also got stuck at some block (don't exactly know which one). This was right after a DS Tx, so this DS Tx has was shown as unconfirmed.
I looked for the TxID on an actual up to date chain but it was not there o_O
I let it -rescan the wallet which did not help.
I then deleted the blockchain and let it redownload the blockchain, which helped to get back up to date with the chain. However, since the Tx never made it into the blockchain, it was still shown as unconfirmed.
I waiting a bit longer so my client could rebroadcast the Tx. However, I eventually gave up after a few hours and did a -zapwallettxes.
After rescanning, the Tx in question was gone. Idk how it got there and why it didn't confirm. Maybe one of the DS participants did a double spend. however, this would probably have been recognized by my client.
We need some validation for Txs that behave like this so they can get automatically removed by the client if they are no longer valid.
 

paperThin

Member
Jun 13, 2014
106
19
68
My client has been stuck for 2 days. (At first it was mixing very well.) I had tried zapping the wallet several times over those 2 days. Today, it picked up and started mixing again. Yay!

Meanwhile, I loaded the Mac Client for the first time ever. Looks good, thanks devs! The question I have is regarding the "receive" addresses. After I created several, it seems there is no way to edit, the label or message. Am I missing something here? Thanks!

(Now I checked on my Windows (32) on XP. It seems to be the same way. I remember in the past these were editable.) Can someone confirm this feature is unavailable now? Thanks!
 

crowning

Well-known Member
May 29, 2014
1,415
1,997
183
Alpha Centauri Bc
My client has been stuck for 2 days. (At first it was mixing very well.) I had tried zapping the wallet several times over those 2 days. Today, it picked up and started mixing again. Yay!

Meanwhile, I loaded the Mac Client for the first time ever. Looks good, thanks devs! The question I have is regarding the "receive" addresses. After I created several, it seems there is no way to edit, the label or message. Am I missing something here? Thanks!

(Now I checked on my Windows (32) on XP. It seems to be the same way. I remember in the past these were editable.) Can someone confirm this feature is unavailable now? Thanks!
Just double-click on an existing address.
 

paperThin

Member
Jun 13, 2014
106
19
68
Just double-click on an existing address.
No dice. not in Mac nor in XP. I have a value of zero coins in those addresses. Do you think that could be a factor? I added 2 addresses to the wallet. I did not add any message nor label when they were created. They read (no message) and (no label). Am I missing something?
 

UdjinM6

Official Dash Dev
Dash Core Team
Moderator
May 20, 2014
3,638
3,538
1,183
No dice. not in Mac nor in XP. I have a value of zero coins in those addresses. Do you think that could be a factor? I added 2 addresses to the wallet. I did not add any message nor label when they were created. They read (no message) and (no label). Am I missing something?
Go to "File" -> "Receiving addresses..." and then
Just double-click on an existing address.
:D
 

paperThin

Member
Jun 13, 2014
106
19
68
Have you actually tried doing this with this version? It only kinda works. Both in the mac and XP version. If you change the "label" by going to the FILE menu, it does not actually change the label on the "Receive" tab.

Also, I have 6 receive addresses, but they only show up under the file menu. They are not listed on the receive tab. (XP version).

[EDIT] The receive tab is showing only 1 address, it is unlabeled. (no label)
 

UdjinM6

Official Dash Dev
Dash Core Team
Moderator
May 20, 2014
3,638
3,538
1,183
Have you actually tried doing this with this version? It only kinda works. Both in the mac and XP version. If you change the "label" by going to the FILE menu, it does not actually change the label on the "Receive" tab.

Also, I have 6 receive addresses, but they only show up under the file menu. They are not listed on the receive tab. (XP version).

[EDIT] The receive tab is showing only 1 address, it is unlabeled. (no label)
Receive tab shows recent payment requests (and their labels), not addresses!
Tick "Reuse an existing receiving address (not recommended)" checkbox and click "Request payment" button to reveal your addresses (same as going through menu).
And yes, there is no way to change label in "Requested payments history" table now.
 

Aswan

Member
Jun 26, 2014
68
216
73
Look at this DS Tx:

dedff92207f23cac7bfa92b1c6233b25c082d9c84aaf766ab620c43f485c11e3

It has 28 inputs of 0.10000001 and 28 outputs of 0.10000001. The perfect Darksend Tx... one would think...

Until we look at the Transactions using those outputs. d2bb9c9ea910c738cb358aee2d2ae7033e9aefa37057fee6877a687240d568af uses 11 of those 0.10000001 outputs as inputs while in dedff92207f23cac7bfa92b1c6233b25c082d9c84aaf766ab620c43f485c11e3 there have been 11 0.10000001 inputs from the same source (3e9d8b8311fb7d88e207090606d195bfd21964713c682e98b831004a59ba5064).

It's obvious that the 11 inputs are the 11 outputs and that they belong to the same person.

While I really appreciate what Evan and the rest of the dev team did for Darkcoin and especially for this release, I unfortunately have to say that Darksend is not safe to use regarding anonymity in it's current state.
I would like to have a discussion with one of more people from the dev team about the current implementation of DS and how things can be improved. There are so many things on my list regarding this.
Is there anyone willing to discuss this? Preferably in audio. Darkcoin and especially the masternode network and the way it can be used with coinjoin is such an awesome technology, but somehow it just doesn't seem to come together. I think I can really help with that. =/
 
Last edited by a moderator:

Lukas_Jackson

Member
Nov 9, 2014
160
70
88
Look at this DS Tx:

dedff92207f23cac7bfa92b1c6233b25c082d9c84aaf766ab620c43f485c11e3

I has 28 inputs of 0.10000001 and 28 outputs of 0.10000001. The perfect Darksend Tx... one would think...

Until we look at the Transactions using those outputs. d2bb9c9ea910c738cb358aee2d2ae7033e9aefa37057fee6877a687240d568af uses 11 of those 0.10000001 outputs as inputs while in dedff92207f23cac7bfa92b1c6233b25c082d9c84aaf766ab620c43f485c11e3 there have been 11 0.10000001 inputs from the same source (3e9d8b8311fb7d88e207090606d195bfd21964713c682e98b831004a59ba5064).

It's obvious that the 11 inputs are the 11 outputs and that they belong to the same person.

While I really appreciate what Evan and the rest of the dev team did for Darkcoin and especially for this release, I unfortunately have to say that Darksend is not safe to use regarding anonymity in it's current state.
I would like to have a discussion with one of more people from the dev team about the current implementation of DS and how things can be improved. There are so many things on my list regarding this.
Is there anyone willing to discuss this? Preferably in audio. Darkcoin and especially the masternode network and the way it can be used with coinjoin us such an awesome technology, but somehow it just doesn't seem to come together. I think I can really help with that. =/
For me is a kind of a magic how darksend really work and I try to understand it better but I really enjoy seeing people like you. More like you + brainstorm = Darksend Perfect 1.0
 
  • Like
Reactions: moli and Aswan

Light

Well-known Member
Foundation Member
Jun 4, 2014
346
256
233
Look at this DS Tx:

dedff92207f23cac7bfa92b1c6233b25c082d9c84aaf766ab620c43f485c11e3

It has 28 inputs of 0.10000001 and 28 outputs of 0.10000001. The perfect Darksend Tx... one would think...

Until we look at the Transactions using those outputs. d2bb9c9ea910c738cb358aee2d2ae7033e9aefa37057fee6877a687240d568af uses 11 of those 0.10000001 outputs as inputs while in dedff92207f23cac7bfa92b1c6233b25c082d9c84aaf766ab620c43f485c11e3 there have been 11 0.10000001 inputs from the same source (3e9d8b8311fb7d88e207090606d195bfd21964713c682e98b831004a59ba5064).

It's obvious that the 11 inputs are the 11 outputs and that they belong to the same person.

While I really appreciate what Evan and the rest of the dev team did for Darkcoin and especially for this release, I unfortunately have to say that Darksend is not safe to use regarding anonymity in it's current state.
I would like to have a discussion with one of more people from the dev team about the current implementation of DS and how things can be improved. There are so many things on my list regarding this.
Is there anyone willing to discuss this? Preferably in audio. Darkcoin and especially the masternode network and the way it can be used with coinjoin is such an awesome technology, but somehow it just doesn't seem to come together. I think I can really help with that. =/
Dude (or Dudette) , you are a cool ^%%#%! :D I hate you and love you like a brother at the same time :D I hate you because you are keep finding things in the system that needs to be fixed, no matter how much I wanna believe that we already have a perfect system. And I love you because you are doing this like a real gentleman and offering to help. You have my great respect, sir! Thank you. I am sure you will be contacted by the dev team soon. It is still Sunday 8:30am in US now (East Coast).
 
Last edited by a moderator:

crowning

Well-known Member
May 29, 2014
1,415
1,997
183
Alpha Centauri Bc
It has 28 inputs of 0.10000001 and 28 outputs of 0.10000001. The perfect Darksend Tx... one would think...

Until we look at the Transactions using those outputs. d2bb9c9ea910c738cb358aee2d2ae7033e9aefa37057fee6877a687240d568af uses 11 of those 0.10000001 outputs as inputs while in dedff92207f23cac7bfa92b1c6233b25c082d9c84aaf766ab620c43f485c11e3 there have been 11 0.10000001 inputs from the same source (3e9d8b8311fb7d88e207090606d195bfd21964713c682e98b831004a59ba5064).

It's obvious that the 11 inputs are the 11 outputs and that they belong to the same person.
I didn't look into Darksend for quite a while, so I may be wrong because I probably already forgot half of it.

Anyway: wouldn't the number of identical inputs/outputs get less with each round of mixing?

  • 28: 11+11+6
    • 11: 4+4+3
      11: 4+4+3
      6: 2+2+2
      • 4: 2+1+1
        3: 1+1+1
        ...etc...
 

Aswan

Member
Jun 26, 2014
68
216
73
I didn't look into Darksend for quite a while, so I may be wrong because I probably already forgot half of it.

Anyway: wouldn't the number of identical inputs/outputs get less with each round of mixing?

  • 28: 11+11+6
    • 11: 4+4+3
      11: 4+4+3
      6: 2+2+2
      • 4: 2+1+1
        3: 1+1+1
        ...etc...
With the current implementation, funds get recombined to non-ds outputs several times during a 16 rounds DS process, which causes a "soft reset" of the anonymization process. So it doesn't just split but also recombine.
With denomination convertibility (which I already suggested somewhere else), recombination would not have to cause this "soft reset".
I am not sure why this "soft reset" is done, but I suppose it is to reduce bloating the chain.

Regardless of the recombination of funds, your example unfortunately misses the point.
The Tx is question did not achieve any kind of additional anonymity because outputs can be linked with inputs accurately. Yet the client will still count this as a DS round, effectively reducing the rounds these funds go through by 1.
This in itself might not always be a problem, depending on how many rounds you are going for, but I have founds severals other transactions which have funds that are easily linkable as well, which reduces the amount of effective DS rounds even more.
This cascade of leaking Transactions is what causes the anonymity issue.
 
  • Like
Reactions: moli

Aswan

Member
Jun 26, 2014
68
216
73
Hi Aswan,

Maybe you should raise a ticket for this here : http://jira.darkcoin.qa/secure/Dashboard.jspa
Make it a critical bug or something ? Chances are that you receive feedback from the development team faster that way

Well its not just this. I have a List of stuff regarding DarkSend I'd like to talk to a dev who is an expert at coinjoin/darksend about. A lot of the things in the list are connected etc. so if I just start raising tickets there it will become a long way to get this resolved. This should be talked about in a serious discussion and if no dev is available for this, I can still go and look for other ways to communicate all of this.
 

jpr

Active Member
May 11, 2014
493
393
133
Well its not just this. I have a List of stuff regarding DarkSend I'd like to talk to a dev who is an expert at coinjoin/darksend about. A lot of the things in the list are connected etc. so if I just start raising tickets there it will become a long way to get this resolved. This should be talked about in a serious discussion and if no dev is available for this, I can still go and look for other ways to communicate all of this.
Have you tried contacting Evan directly and talk about all this?
 
  • Like
Reactions: studioz

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
Well its not just this. I have a List of stuff regarding DarkSend I'd like to talk to a dev who is an expert at coinjoin/darksend about. A lot of the things in the list are connected etc. so if I just start raising tickets there it will become a long way to get this resolved. This should be talked about in a serious discussion and if no dev is available for this, I can still go and look for other ways to communicate all of this.
Please email Evan, [email protected].
 

eduffield

Core Developer
Mar 9, 2014
1,084
5,319
183
Well its not just this. I have a List of stuff regarding DarkSend I'd like to talk to a dev who is an expert at coinjoin/darksend about. A lot of the things in the list are connected etc. so if I just start raising tickets there it will become a long way to get this resolved. This should be talked about in a serious discussion and if no dev is available for this, I can still go and look for other ways to communicate all of this.
Please email me directly, I'd love to talk about it: [email protected]
 

eduffield

Core Developer
Mar 9, 2014
1,084
5,319
183
Well its not just this. I have a List of stuff regarding DarkSend I'd like to talk to a dev who is an expert at coinjoin/darksend about. A lot of the things in the list are connected etc. so if I just start raising tickets there it will become a long way to get this resolved. This should be talked about in a serious discussion and if no dev is available for this, I can still go and look for other ways to communicate all of this.
Hey, I've read through your posts and I believe all issues you bring up are presently fixed in 11.0.8. UdjinM6 wrote a nice patch which entirely removes non-denomination DRK from being in the pool at all. I'm going to compile and release this version in the morning, as a nice side effect, mixing should be about 100% faster too. We're getting to an almost perfectly working system, it's just taking some real work to do it the right way ;)

Changes are here:

https://github.com/darkcoin/darkcoin/pull/116/files
 

brownmon

New Member
Oct 6, 2014
11
3
3
I can't sync my Windows wallet v0.11.0.7-g5db4831-beta (64-bit) . Stuck 11 weeks ago, at block 161574.
 

brownmon

New Member
Oct 6, 2014
11
3
3
Close your wallet. At the command prompt run \darkcoin-qt.exe -reindex .
[Window Title]
darkcoin-qt.exe

[Main Instruction]
darkcoin-qt.exe has stopped working

[Content]
A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.

[Close program]
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
[Window Title]
darkcoin-qt.exe

[Main Instruction]
darkcoin-qt.exe has stopped working

[Content]
A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.

[Close program]
Which wallet version are you using? 32-bit or 64-bit? Did you try -reindex in the Command Prompt?