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