Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 4743. (Read 9723847 times)

They're still going to be fundamentally different TX types: denominating transactions, versus combining (multiple inputs) transactions. The point is it doesn't matter.

As I mentioned above, if you have, say, 27.000 DRK (27 DRK exactly, comma users), and you denominate it into whatever, and if you later recombine all your denominated addresses (via multiple input) to send 27 DRK to someone else (or even yourself), there exists a *suggestive* link between the original denomination TX and the new sending TX. It's not mathematical proof or anything, though.

They're still going to be fundamentally different TX types: denominating transactions, versus combining (multiple inputs) transactions. The point is it doesn't matter.

As I mentioned above, if you have, say, 27.000 DRK (27 DRK exactly, comma users), and you denominate it into whatever, and if you later recombine all your denominated addresses (via multiple input) to send 27 DRK to someone else (or even yourself), there exists a *suggestive* link between the original denomination TX and the new sending TX. It's not mathematical proof or anything, though.

Not necessarily. When RC4 hits, there's going to be a frenzy of MN activity as everyone's balances get randomly denominated. After that, my gut instinct is that with increased actual use, the MN tx's aren't going to stand out at all amongst 'real' transactions.

DarkSend+

Over the last week or two, Darksend+ has made some significant advances. We’re happy to say that we’re closing in on a finished product.

We've opted to employ a strategy for Darksend+ that is slightly different than the one we outlined in our last update. This new strategy has several advantages, and we think it is a significant improvement over the previous iteration in terms of both privacy and efficiency. The Darkcoin client will now store pre-mixed, denominated Darkcoins in the user’s wallet, to be used instantly at any time the user desires. The mixing and denomination process is seamless, automatic, and requires no intervention on the part of the user. The 10 DRK limit previously in place with Darksend v1 will be permanently removed. With RC4, the amount that users can send via Darksend+ is limited only by the available balance in their wallet.

Here's how it works:

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.

Depending on the desired depth of security and privacy, users may select between 2 and 8 “hops” to successive Masternodes before their coins are sent back to the client. Hops are made every 10 blocks, so anonymization at a depth of 2 hops will take 10*2*2.5=50 minutes, 3 hops 10*3*2.5=75 minutes, and so on. The desired mixing depth can be selected in the client GUI.

At the end of the anonymization phase, the user’s coins are returned to their client at randomly generated change addresses. When the user wishes to make a transaction, the client forwards the intended amount from these anonymous change addresses directly to the intended receiver’s address. There is no direct involvement of of Masternodes in the final person-to-person transaction.

Proof of payment will work as it always has: a user can see the send transaction with the receiver’s address in their own wallet, and the blockchain will show that the receiver’s address received an input in the corresponding amount.

They're still going to be fundamentally different TX types: denominating transactions, versus combining (multiple inputs) transactions. The point is it doesn't matter.

As I mentioned above, if you have, say, 27.000 DRK (27 DRK exactly, comma users), and you denominate it into whatever, and if you later recombine all your denominated addresses (via multiple input) to send 27 DRK to someone else (or even yourself), there exists a *suggestive* link between the original denomination TX and the new sending TX. It's not mathematical proof or anything, though.

At the end of the anonymization phase, the user’s coins are returned to their client at randomly generated change addresses. When the user wishes to make a transaction, the client forwards the intended amount from these anonymous change addresses directly to the intended receiver’s address. There is no direct involvement of of Masternodes in the final person-to-person transaction.

It seems you're missing the critical piece of the puzzle: the mixing. Multiple random-sized inputs go in, in multiple stages; denominated, homogeneous outputs come out at various stages. If you're not missing that, then your analysis does indeed apply, but only in cases of people mixing everything then sending the whole chunk back to some other address. Why would you do that? What would it accomplish?

Not necessarily. When RC4 hits, there's going to be a frenzy of MN activity as everyone's balances get randomly denominated. After that, my gut instinct is that with increased actual use, the MN tx's aren't going to stand out at all amongst 'real' transactions.

MNs will show up on the blockchain many orders of magnitude more often than non-MN clients. It's a blockchain-based form of traffic analysis. We can tell the difference between clients and MNs by this alone and it's REALLY obvious.

That doesn't appear to be true from where I am standing.

If I am standing in the wrong place, help me relocate.

An outside observer will have no idea whatsoever of the amount being transacted, because ALL transactions will use denominated amounts. It's just one big sea of zero useful information.

I think it's this...

https://www.youtube.com/watch?v=ohiCNDT7W08

Development on RC4 is nearing an end and we expect that we’ll be firing up testnet in the coming week. Depending on what we find, testing and QA should take 2 to 4 weeks.

I'm saying that the send can be correlated to the receive. The nature of it, who knows.

I'm saying that it's too much information. The blockchain is still transparent, and always should be. Information always adds up. Put as little correlative data out there as possible. The same script that correlates BTC could still correlate DRK.

It's less information, but it's still enough for a 3rd party to gather that A sent X to B.