Search results

I found something weird! Seems to be a bug. I am using 16 rounds of DS. There are some funds with 17 rounds which are now listed as available DS balance (Bottom right: Balance: 19.700198). I have selected all the denominations with 17 rounds. It's 18 denminations (Top left) and their total...

The fee is for the transaction doing the initial denomination. With the new DS rules, only DS denominations are allowed as inputs and outputs in any DS transaction. As a result, your client has to create the DS denominations before any of your coins enter the DS pool. This initial denomination...

Random is the key word here I think. Client side randomness when choosing which outputs to use for the current Tx will greatly improve anonymity. I will test this asap. Thanks. denomination convertibility would be a huge benefit not only for the current implementation, but also for...

Oh... I thought you meant that instead of 10.00000001 DRK as a denomination, we now have 10 DRK as a denomination =/ This is definitely not one of my most anticipated features then :)

 { "version" : 110010, "protocolversion" : 70053, "walletversion" : 61000, "balance" : Yes, I have some coins ! :D "darksend_balance" : 0.00000000, "blocks" : 206450, "timeoffset" : 3, "connections" : 10, "proxy" : "", "difficulty" : 4588.24182457, "testnet" : false, "keypoololdest" ...

This doesn't seem to work. I just started up a new wallet, put some coins in, and the denomination Tx still denominates into non-exact DS amounts.

Thank you UdjinM6 and Evan. For me, this is one of the most anticipated changes to Darksend since... ever :)

It wouldn't necessarily require a fork, just masternode compatibility with both systems. This would split the Darksend users into 2 groups. The ones that use the old and the ones that use the new system. Currently, we have 3 people mixing their coins per DS Tx, so at least 3 people using the...

Interesting. What are we gonna do when we introduce 0.01 denominations in order to adapt to a possible price increase? Also, I think a 0.01 denomination will be necessary for DarkSend fees in the future. I see a flaw with the current fee/collateral system which I have not publicly talked about...

Thats really good, but unfortunately, thats not enough, because of denomination recombination and splitting without denomination convertibility. Look at this Tx: 7df9af07fa9e519555eb8bcfbe4cbf514b035fd8b763b0f5778298b5447f48cb It has only DS denomination inputs. Let's look at the 100.00000001...

I have read through the code and I think at least one issue I have brought up is not fixed, plus I have some more on the list :) Also, with each denomination size only allowed 10 times, this will make denomination combination necessary if there are more than 10 inputs of one kind of denomination...

Thanks for the idea. I will do this tomorrow if there is no answer to my request here. It's already evening here so I might as well wait until tomorrow. :)

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...

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)...

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...

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...

Maybe that one Tx, but that does not invalidate all the other issues I have brought up. I hope they can get fixed =/

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...

I have had some time to test the new Darksend and have found that it is a lot easier to trace coins than is has to be because of the fact that the outputs are not all DS denominations but sometimes just regular change amounts which are so high that they can be tied to a specific input, sometimes...

Interesting. Look at this DS Tx: d6837f60aa13bfe02b9feea8509a1a96904927f7569cc29f29e45906291f87df It has an Input of 227.47499967 DRK and am output of 227.47499967 DRK. Seems like the coins haven't been mixed at all, yet they appear in a DS Tx and bloat the chain O_o