Search results

  1. A

    October 2015 Budget Proposal

    Since I haven't been that active in this community the last few months, can you update me regarding the DS replacement?
  2. A

    October 2015 Budget Proposal

    First of all, regardless of how exactly the winner is chosen or how often one is declared, I think we have to make sure what exactly we incentivize and how we can avoid incentiviztation of things we do not want (like more bloat). I Think the expected return needs to be less than 1. So for every...
  3. A

    Which Masternode model should we implement?

    Well it's just a suggestion I came up with on the fly since this was about to be decided. I might be totally wrong but I thought it was worth bringing this up.
  4. A

    Which Masternode model should we implement?

    Thanks for the link. It was not a suggested solution for the anonymity issue but for the "-No direct connection to masternodes (DS will be slightly less secure)" part.
  5. A

    Which Masternode model should we implement?

    I think this can be fixed by using a bitmessage-like system where communication between mixing participants and the masternode is broadcast to everyone on the network. This communication can be encrypted with a public key only that specific masternode has the private key to. It then answers with...
  6. A

    Darksend lost coins what happened

    Hello "whathappened". This indeed seems like a Darksend denominations transaction. This transaction splits your coins into stacks of different sized, but it should by no means lose the coins. When your Client loads up, it create 1000 addresses that aren't directly visible to you. They can be...
  7. A

    Security Advisory for CoinShuffle and Darkwallet

    Nice find! Every output would have to be flagged and outputs that are flagged as being used as a combined payment cannot be used in a single Tx. However, regarding blockchain analysis, they could still be used for a single payment if the payment is of the same nature as the one before, because...
  8. A

    Security Advisory for CoinShuffle and Darkwallet

    Sorry for deleting my previous post. When I read over it, I felt like it doesn't add anything new to the discussion because it basically only rephrased what I wrote in the post before it. I didn't know you were in the process of answering to it, else I would have let it there. Using multiple...
  9. A

    Security Advisory for CoinShuffle and Darkwallet

    I have to agree that with this kind of analysis, while some things might be highly unlikely, they are not impossible. I also think these kinds of scenarios are really important to find and possibly use the unlikelyness of them happening for further development. In fact I see a lot of chances...
  10. A

    Nominate Projects for the Developer Bounty Fund. #1

    That is how SPV clients work. A lightweight client that only gets the info it actually needs from nodes. However, this comes with a drawback in safety compared to having the full chain. It is what I meant when I said that if has to be on the protocol level it we do not want it centralized.
  11. A

    Nominate Projects for the Developer Bounty Fund. #1

    I'd like to see some work regarding blockchain pruning. It's on the protocol level (if we do not want it to be centralized), yet it is not a direct work on the core client, so does this count? :P
  12. A

    v0.11.0 - Darkcoin Core Release

    Thanks for the info, I thought you meant Dead Change that occurred as a change from spending a DS denomination. The amounts you got there are some collaterals and the 0.672407 seems to be just too small to actually attempt mixing (on avg. there would be a significant portion of the 0.672407 lost...
  13. A

    Welcome Mario Müller To The Team

    Yes, my bitcointalk account is "Aswan" as well.
  14. A

    Welcome Mario Müller To The Team

    Yeah I am German :)
  15. A

    Welcome Mario Müller To The Team

    Thanks! I really appreciate everyone in the community being so nice and helpful. Looking forward to being a member of the team. :)
  16. A

    v0.11.1 - InstantX Development Update

    Thats why I keep doing it. It's a pleasure to have development going that way. How is this enforced? I have made the experience that timestamps and the blockchain don't go well together. Why not make it 2 blocks or 3 blocks. Something like ntimelock, but in reverse (ntimecap?) There would...
  17. A

    v0.11.1 - InstantX Development Update

    I think the collateral system is flawed. If 3 people sign a Tx with a 0.1 DRK miners fee and, instead of publishing the Tx, it will only be cashed with a chance of 1/40, then there are a lot of unclaimed and uncashed but signed transactions in the hands of MN owners, and most of them will remain...
  18. A

    v0.11.1 - InstantX Development Update

    I see a problem with the incentive for masternode mining since there is no reward for doing it. I actually see the same problem with the current implementation of Darksend and it's collateral system, but to keep this thread on topic, lets talk about incentivized masternode mining. Also, this...
  19. A

    v0.11.0 - Darkcoin Core Release

    I'll re-test it with the current version before I do that :) Edit: Why is .14 not on Darkcoin.io?
  20. A

    v0.11.0 - Darkcoin Core Release

    Yeah I'd be interested if this problem occurs for other wallets as well. After another DS round I have more DS balance but it is still 0.1 DRK short of what it should be.
  21. A

    v0.11.0 - Darkcoin Core Release

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

    v0.11.0 - Darkcoin Core Release

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

    v0.11.0 - Darkcoin Core Release

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

    v0.11.0 - Darkcoin Core Release

    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 :)
  25. A

    v0.11.0 - Darkcoin Core Release

     { "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" ...
  26. A

    v0.11.0 - Darkcoin Core Release

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

    v0.11.0 - Darkcoin Core Release

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

    v0.11.0 - Darkcoin Core Release

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

    v0.11.0 - Darkcoin Core Release

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

    v0.11.0 - Darkcoin Core Release

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

    v0.11.0 - Darkcoin Core Release

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

    v0.11.0 - Darkcoin Core Release

    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. :)
  33. A

    v0.11.0 - Darkcoin Core Release

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

    v0.11.0 - Darkcoin Core Release

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

    v0.11.0 - Darkcoin Core Release

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

    v0.11.0 - Darkcoin Core Release

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

    v0.11.0 - Darkcoin Core Release

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

    v0.11.0 - Darkcoin Core Release

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

    v0.11.0 - Darkcoin Core Release

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

    v0.11.0 - Darkcoin Core Release

    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