chaeplin
Well-known member
Masternode holds nothing ;DHow will password-locked wallets do such mixing?
Masternode holds nothing ;DHow will password-locked wallets do such mixing?
Could you make this semi-random? If you let everyone set whatever they want in the wallet from 2-8, almost all people will either select 2 for speed, or 8 for more stealth, and nothing in between. This would give a fairly decent assumption an attacker might be able to find a way to leverage when trying to trace coins. Instead offering "about 4-6" which would be actually done as pick a random number of what the user chose plus or minus 2 cycles would destroy that assumption.The desired mixing depth can be selected in the client GUI.
Could you make this semi-random? If you let everyone set whatever they want in the wallet from 2-8, almost all people will either select 2 for speed, or 8 for more stealth, and nothing in between. This would give a fairly decent assumption an attacker might be able to find a way to leverage when trying to trace coins. Instead offering "about 4-6" which would be actually done as pick a random number of what the user chose plus or minus 2 cycles would destroy that assumption.
How is a timing analysis done? Does this make it easier to double spend without being caught? This might be important to bring up to Evan (in case he doesn't check here again)So, will no one address ever contain more than the largest possible denominated amount? And the client just groups them together appropriately for transactions, which are redenominated at the other end? Because that renders the whole blockchain entropic sludge and makes timing analysis impossible...
What happens with change.
What happens when one (or all) masternodes involved break down/get hacked/do intentionally bad things/... while _my_ coins are on their trip to anonymity?[...]Every 10 blocks, user clients network-wide will send any unmixed, traceable Darkcoins in their possession through an anonymization phase. In this phase, Masternodes are used in chained succession to mix the coins they receive from the network and break them down into homogenous denominations. After being processed by a minimum of 2 Masternodes, the coins are either sent to the next Masternode in the chain or back to the user’s wallet at randomly generated change addresses.
The coins are never in the control of the masternodes, so you'll still have them.Was this question not answered so far because...
- it's incredibly dumb because it's already answered on page one of a manual I don't know of?
- it's even more dumb because it's trivial to find out by firing up some Masternodes in a source-code debugger?
- it's already answered in about 10000 posts but I always failed to enter the proper search string in the forum search?
- I'm already on everyone's ignore list :grin:?
- nobody cares because Evan knows what he's doing?
- nobody knows (really?)
- [ insert your preferred option here ]
Curious minds would like to know...
Will another attempt to mix them be made automatically, or must the user do it manually?The coins are never in the control of the masternodes, so you'll still have them.
Here is the process:
Your client sends what transaction it wants to do to the masternode.
The mastenode crafts a transaction joining multiple peoples' transactions together, however it needs all of them to sign off on it.
The masternode sends out the that transaction to the people involved, so they can check it and sign off on it.
The clients check to see that their inputs and outputs are in the transaction sent to them.
If they agree that it looks right, they send a signature for it to the masternode.
Once the masternode collects up the signatures, it can publish the transaction.
As the coins are never under the masternode's control, if it fails to complete the process your coins will still be in your wallet, just not mixed.
The masternode sends out the that transaction to the people involved, so they can check it and sign off on it.
The clients check to see that their inputs and outputs are in the transaction sent to them.
If they agree that it looks right, they send a signature for it to the masternode.
Extra transactions will cause extra bloat. Fortunately, space is cheap, and the blockchain isn't growing that quickly, so it's unlikely to become unmanageable any time soon. If it truly did get too large(keep in mind that bitcoin's blockchain is only up to about 20GB, which although annoying to download, is hardly significant for current hard drives), there are some things that could be done to try to lower it. The current block data compresses very well, and just for the sake of testing, I ran it through winrar and was able to decrease the size by more than 40%. Obviously that isn't a format you'd try to run in-line, but I'm sure you'd get significant gains with something else that you could use to directly save and load compressed data. Another possibility is blockchain pruning could be attempted to be done, although that would likely be controversial, as it would break the ability to verify all the way back to the beginning.1. How does the math work when it comes to all of these additional transactions, i.e. 1 'real' transaction could take many multiples of that during the mixing process to succeed in creating a truly anonymous transaction? Is that correct? Will it therefore exponentially increase the rate of growth in the blockchain at an unsustainable rate?