Search results

  1. P

    Dead Change - an anonymity issue

    No, I had 37 "darksend denominates" in my transaction ledger over the weekend. That is 37 separate DSD transactions. (I think I had the liquidity set to 30.) Meanwhile, I had no fees charged at all. Love it!
  2. P

    Dead Change - an anonymity issue

    1. Thanks! Got it! 2. As LP, it sets the rounds to 999999 automatically. I definitely went 37 rounds because I can look at any one of those transactions. A DSD definitely occurred each time...and a new address each time. It's just that the "# of rounds" shown on my inputs list stayed at 9...
  3. P

    Dead Change - an anonymity issue

    Oblox, I posted this on the v.16 thread... do you know these answers? Hey All, I have 2 stupid questions if someone could enlighten me! How does the new DS mix work so that the fees are zero? Who pays the TX fees? I left my liquidity provider on all weekend and had 39 "Darksend Denominates"...
  4. P

    v0.10.16 - Onyx v2

    Hey All, I have 2 stupid questions if someone could enlighten me! How does the new DS mix work so that the fees are zero? Who pays the TX fees? I left my liquidity provider on all weekend and had 39 "Darksend Denominates". Why do my inputs show only "9 rounds"? I did 8 rounds DSD on the...
  5. P

    Dead Change - an anonymity issue

    I think follow regarding the single TX being the issue here. Providing I did a 4x DS mix prior to all private transactions. Then I did several separate private transactions. Then the "jar mix". Finally 4x DS mix with the whole numbers and put the dead change aside. Now, spending the whole...
  6. P

    Dead Change - an anonymity issue

    Easy to do. The blockchain is public so the crawler is basically already there. The part that makes it anonymous is 2 parts. First, there (should not be) any connection to someone's personal ID and the address. (Bitcoin has this) Second, by mixing our balances between many people (using...
  7. P

    Dead Change - an anonymity issue

    If the client requires(forces) 2 rounds of DS mixing, then the process "jar mix" could simply be the first round of DS... the client could automatically DS mix the resulting whole numbers to the required (2x) or more times as the user specifies.
  8. P

    Dead Change - an anonymity issue

    The issue is that it is tied by the transaction, not the address. To break this connect would change the basic theory of blockchain. (ie destroy the previous amount and reissue the amount to a new address.) Plus, the amount would be the same and thus suspicious.
  9. P

    Dead Change - an anonymity issue

    Thanks Aswan and have a good night. I will be out until late Sunday night... I look forward to reading your response. Yes, it seems we are in agreement on most points, I just needed to be sure. My secondary points are useless if the primary assumptions do not hold up. Thanks for lending your...
  10. P

    Dead Change - an anonymity issue

    Aswan, Thank you for taking the time to consider my approach. If I could bother you for with more questions. (Let's assume that DS is improved to use whole numbers for this discussion.) Large Change: Regarding "dead change" greater than 1.0. (i.e. 4.87 drk from a single transaction)... Do you...
  11. P

    Dead Change - an anonymity issue

    Aswan, I follow your discussion and agree with your request for whole numbers (1,10,100 etc). It is more anonymous if they are indistinguishable from other non-darksend transactions. Outside observers would not know if blockchain transactions were purchases or a person mixing. It seems that...
  12. P

    v0.10.16 - Onyx v2

    Thanks Quizzie... I will wait a little... I thought the warning was strange, saying "too recent". It seems like it should say something else if the network has not stabilized like... "nodes not found" or "no matching transactions to mix" etc. I will wait a bit, but I am anxious to try out this...
  13. P

    v0.10.16 - Onyx v2

    I noticed Even mentioned something about "Darksend request incomplete. Last darksend was too recent". That it would not happen often, but it could still come up under some circumstances and when you first start up. I am trying to "Mix" and I am getting this "Darksend request incomplete...
  14. P

    Darksend Liquidity Provider - v0.10.16.4

    Thanks moocowmoo. Yeah, I'm not doing any of those things (Interrupting) and my internet service is very good. I did send my log to Evan a with the info. Is this something that everyone is getting or only some users? Do you see this moocowmoo yourself? Thanks!
  15. P

    Darksend Liquidity Provider - v0.10.16.4

    2 collateral charges... phooey! So that's 2 collaterals and 4 DD in less than 2 hours. It just seems like I must be doing something wrong. Any advice?
  16. P

    Darksend Liquidity Provider - v0.10.16.4

    4 denominates in 17 minutes! (Yes, on the collateral charge. Thanks) I'm going to finish 6 rounds and then fire up the Liquidity Provider Wallet.
  17. P

    Darksend Liquidity Provider - v0.10.16.4

    OK - Got 1 "payment to yourself" (0.10 DRK) and then a Darksend Denominate (0.0125) within a minute after that. Will send the log to Evan.
  18. P

    Darksend Liquidity Provider - v0.10.16.4

    I don't understand this... no mixing at all. I tried to throw away everything from my old wallet and start fresh. I thought I had a new wallet because it took time on boot-up to generate 1000 keys. (I had taken out the old wallet.dat and the .log etc out of the old folder, but I left the...
  19. P

    Darksend Liquidity Provider - v0.10.16.4

    I got ZERO denominates over 24 hours. (Using the above configuration - Last post) I have not gotten any denominates for the past 2 weeks, but before that I had several over a couple days. I figured it was time to start up a new wallet. So I sent some DRK to a new wallet and starting fresh...
  20. P

    Darksend Liquidity Provider - v0.10.16.4

    Can someone tell me the port to open through my router so I can get more than 8 connections? Thanks! Got it :8333 ... 31 Connections!
Back
Top