Search results

  1. A

    v0.11.0.x Core Testing

    With the testnet explorer it's a real pain manually tracking transactions :) I had some success tracking it, but didn't chase too far because of the testnet explorer not making it any easier. With the chainz.cryptoid.info explorer it used to be much easier, but they don't have one for testnet...
  2. A

    What's in a name? ...or, is a rose by any othername worth the trouble?

    I am in favor of a name change to something that makes it seem less dodgy. I think it would not hurt Darkcoin. However, this would have to be planned carefully.
  3. A

    Cannot use Darksend mixing

    Same here. Mixing seems to be weird right now and I've rarely seen a Darksend Tx hitting the Blockchain withing the last few days.
  4. A

    v0.10.17 - Onyx v3

    Hello everyone, I haven't been around for quite some time but I am pleased to see there has been a solution implemented to the Dead change issue. Thanks to everyone who joined the discussion and helped with the issue. Now let's see what other flaws I can find :P
  5. A

    Dead Change - an anonymity issue

    Exactly! Normal DS is 3 participants per round right now. It can be increased once there are enough people using it but right now, it would take way too long with more than 3 ppl being required. However, since there are multiple rounds it's fine. Of course more participants would be better. the...
  6. A

    Dead Change - an anonymity issue

    Of course there is nothing stopping darksend denominations from further being used in the darksend anonymization process. In fact I took it as granted that we both think that would be a natural thing to do. But that doesn't change anything. The transaction in question (the one you dont want to...
  7. A

    Dead Change - an anonymity issue

    Because the fee is paid by parts of the actual transaction(the leftover that would otherwise be change) and is not a separate input (like in the old DS)
  8. A

    Dead Change - an anonymity issue

    Sorry for the late reply, I had a lot to do :) You are right that more participants increase the anonymity with this jar solution. However, if there is a malicious masternode used to do this Tx, there might be a problem. I got the paper and will read it, then report back. It's true that...
  9. A

    Dead Change - an anonymity issue

    I'll try to answer your whole post tomorrow. It's kinda late and I gotta walk the dog, but what you described is is exactly what I suggested. Dead change that is bigger than the smallest denomination can re-enter the Darksend pool, but it has to do so alone (you cannot use multiple dead changes...
  10. A

    Dead Change - an anonymity issue

    I am not sure I understand you here. The Darksend mixing process has no problem with all inputs being non-anonymous in the first iteration because there are more to follow and the critical spending will only happen after several instances. A transaction using only coins that have been freshly...
  11. A

    Dead Change - an anonymity issue

    I am sorry for this being the 2nd Darksend flaw I had to point out in such a short time, but I think the coinjoin route is the right one, it's just not easy to get everything covered. Micro denominations are useful for a variety of reasons, including paying Darksend fees. I am not sure the...
  12. A

    Dead Change - an anonymity issue

    Putting all the changes into a "change-pool" is not a good solution as I have already explained in my other posts as is links together the purchases. Every change has to be mixed separately. For leftovers there could be an option in the client where the user can save some donation addresses of...
  13. A

    Dead Change - an anonymity issue

    What I mean is the whole amount of the input, so when you have an input of 10.00000001 DRK and only have to pay 9.8 DRK, then there would be a dead change of 0.20000001 DRK which possibly threatens anonymity when reused. However, if you give that 0.20000001 DRK as a tip, there will not be dead...
  14. A

    Dead Change - an anonymity issue

    It potentially does so. It potentially does so, not necessarily. If you send some anonymized coins to an exchange and then send some more coins to the exchange using the dead change from the transaction that first sent coins to that exact exchange, then it doesn't matter since there only one...
  15. A

    Dead Change - an anonymity issue

    I can understand blockchain analysis being a little confusing in this case, since in cases like this, most transaction-chains are traced backwards in the blockchain, while in this case, it's traced forwards. You are right that coins that are linked to a transaction can be re-anonymized by...
  16. A

    Dead Change - an anonymity issue

    haha, alright :)
  17. A

    Dead Change - an anonymity issue

    I'm sorry if there are some things unclear. What made you haveing to read it twice? Maybe I can edit some things.
  18. A

    Dead Change - an anonymity issue

    Hello, I think I have found a flaw with Darksend mixed coins anonymity which I am going to call "Dead change" in reference to Zombies which, if they stay dead, it's fine, but once they start moving they are gonna infest everyone whos in the same room/town with them. If this issue is already...
  19. A

    v0.10.16.x Testing

    A brilliant solution! This also allows clients to flock to only a few masternodes at a time making it more likely to find peers for the mixning process. I love it! I really like this solution. I'd like to hear more about how the "randomly charging" process works. If it's decided only by the...
  20. A

    v0.10.16.x Testing

    Thank you for the quick testnet implementation of a fix. I got a few questions and concerns regarding this implementation though. Interesting. How many zero-tee Txs can they make within what time frame? How is this enforced? What if the network grows and more and more pool adapt a "only Txs...
Back
Top