15

There are three main ways to fix this. The first one is to attempt to select outputs which are unrelated, if possible. This only works if you are sending an amount of monero that can be represented with unrelated outputs. This means that if you have received a single payment, you won't be able to select unrelated inputs, since they're all related - unless ...


15

Your public address will never appear on the blockchain. What you're spending is amounts sent to one-time destinations so they're unlinked. Not only that, but each one-time addres will be "mixed" with a few others. With this, there's no way to link the two payments together. To the recipient, they will seem unrelated unless you tell him yourself they're ...


12

Answers below:) Yes, except if you're consistently using some weird number like 103, in which case you're leaking the fact that every transaction using that mixin might be yours. In a way, yes, but you're paying for the physical size of the transaction, so if you can afford to stuff the Monero blockchain you can afford to stuff all the others. Linearly; if ...


12

There is a small difference. In summary, ringsize will always equal mixin + 1. So, a mixin of 2 is the same as a ringsize of 3. Mixin refers to the number of other inputs used in a ring signature that you do not control. Ringsize refers to the number of total inputs used in a ring signature, including ones you control.


10

Aeon does not have a minimum mixin by design. Transactions with mixin 0 can be very small and inexpensive. This is by design. According to smooth If usage increases there is a built in system to limit growth of <2 mixin transactions, thereby preventing the low mixin generated cascading privacy reduction described by the Monero Research Lab as follows: ...


10

It will always be a sliding scale, much like how many confirmations will give me full security? The answer is neither can give you "full" security, but they can make it so that it's enough to thwart even the most determined attacker. Right now RingCT hasn't been rolled out so privacy is "OK", but once it is in effect it will not only obfuscate better, but ...


10

Monero mixin 0 is still superior to a Zcash "T" transparent transaction due to the fact that Monero uses stealth addresses for every transaction whereas Zcash does not have this feature. I do not imagine there would be any scenario for Zcash to eliminate transparent transactions as this would break a lot of the intentional bitcoin compatibility that is ...


9

There is no concept of full privacy, and therefore no magic mixin enabling full privacy. The default mixin is 4 in monero-wallet-cli, and the network will enforce a minimim of 2, except for particular circumstances in which an input can't be mixed. See https://lab.getmonero.org/pubs/MRL-0004.pdf for a discussion of how the minimum mixin can prevent chain ...


9

It is known that Poloniex switched to non zero mixin for a short time for withdrawals. However, they reverted to zero not long after, and I believe this to be due to the increased fees. Unfortunately, exchanges have to deal with people sending very small amounts of every coin, as they mine directly to the exchange address, or if they don't, they send ...


9

According to Monero Blocks statistics the highest pre RingCT ringsize was 850. I was not able to immediately locate that transaction on the blockchain. I was able to find a sample 150 mixin transaction from block 1,067,631 with a size of 70,219 bytes and a transaction fee of 0.69 XMR. The above pre RingCT ring size and transaction size records were prior ...


9

Privacy: Outputs are where amounts of Monero are stored on the blockchain. When you spend one of your outputs in a transaction, it cannot be known which of 7 different source outputs you're really spending. Therefore your anonymity set grows by 40%. Another advantage is that outputs that you receive will now more likely be used as decoys in other people's ...


8

fluffypony gave a good answer for pre-rct, I will give one for post rct, which is both similar, and different: A higher mixin means selecting another input that could be the one that's being spent. So yes, in general. Using many inputs can currently show correlations between inputs if you have few of them, but when RingCT is merged, this will be lessened, ...


8

When sending a payment, the amounts are split by denominations, such that every single output's decimal representation is made up of a single non zero digit, and zeroes for the remainder. For instance, 875.4 would be split into 800, 70, 5, and 0.4. If you're sending, or receiving, 875.4, the protocol will be sending these 4 different outputs. The intent is ...


8

The behavior in the transaction you linked is a new one. It did not exist at the time MRL-0004 was written. Now, if you make a transaction now including your 0.00111111 output, it will appear as is as an input to that transaction (and you may have to send it with mixin 0, unless there are two other outputs of that size on the blockchain already). However, ...


7

There were two main reasons outputs were called dust: small outputs (typically well below 0.01, which is the fee per kB) "complex looking" amounts, such 0.000013852456 The problem with the first type is that they might not "pay for themselves" in fees. Since fees in Monero are 0.01 per kB, if you use only small outputs, you may end up with a transaction ...


7

As of the Monero 0.9.0 Hydrogen Helix release the minimum mixin is 2 (2 foreign outputs per ring for a total of 3) with the exception of dust transactions. The minimum mixin will be raised to 4 in a future fork probably at the same time as RingCT according to discussions from the most recent developer meeting. The numbers above along with the simplewallet ...


7

Dust is not a very well defined term in general. However, in the context of your question ("allowed to be sent with a mixin of 0"), this is about which outputs have enough other outputs of the same amount on the blockchain. If there are enough such outputs, then the output is not considered dust for the purposes of mixin 0 rules. If there are not enough, ...


7

There is no mixin amount that gives you "full" privacy. The minimum mixin of 2 gives the smallest amount of plausible deniability possible (1 in 3), and the default of 4 is a little bit better (1 in 5). The importance of each additional mixin decreases for each additional one. For example, a change from "1 in 10" to "1 in 11" is less meaningful than a change ...


7

For any particular person, maybe not. But in general, a miner might want to hide the fact that he or she may be mining (or even mining a particular block). For instance, if a third party knows you mined block B, and they see coinbase from block B moving, then they know it must be you. The minimum mixin is imposed to prevent a tragedy of the commons scenario ...


7

As mentioned by JustinEU4, degradation of privacy for one party also degrades privacy for others. The effect is typically small, but if there is a lot of degradation, there comes a threshold effect. This can be understood intuitively with a simple, contrived, example: Alice, Bob, and Charlie each write their names on a piece of paper, fold it, and put it ...


6

One option would be modifying the selection algorithm so that it selects ring partners in a similar date range to your own outputs. Then all of the transactions in your ring would be from the same date range, rendering this sort of analysis useless. RingCT will make this sort of solution a lot more practical, as the presence of correct output denominations ...


6

No. It just splits the transaction amout into denominations commonly found on the blockchain. Then, each of those denomitation is mixed with few more of the same kind, depending on the mixin level specified. This is to ensure there are always plenty of denominations avaliable to mix with. If you used arbitrary amouts like a single 0.324123 transaction, it ...


6

I have this, which may be wrong as I've not tested it a whole lot. The constants at start are "close enough", I did not try to be 100% precise: 47 + inputs * (39+(mixin+1)*2) + outputs*38 + 64 * inputs * (mixin+1) If you want to know whether a fee is acceptable before it is actually sent, you can use set always-confirm-transfers 1 in simplewallet, and you'...


6

Block 1406997 doesn't come for 341.5 days (as of this writing, Oct 19th, 2016, at block 1161101). September 25th of 2017 seems a bit...much. Please correct my errors. (I would have posted as a comment to the answer above, but my rating on stackoverflow is too low. You could help by up-voting me, just for trying to be constructive.)


6

You must choose mix inputs of the same amount as the one you are spending. Other than that there are no restrictions, though it's not a good idea to choose a really recent output (less than 10 blocks old -- you'd also have to modify the daemon and/or wallet to do so). The wallet currently chooses outputs as follows: 25% are chosen randomly from "recent outs"...


6

The mixin count refers to the number of other signatures (aside from yours) in the ring signature that authorizes the transaction. A default mixin of 4 means that there are 5 total signatures. Someone looking at a transaction with a mixin of 4 has no way of knowing which of the five signers is the true sender (source). "Mixin" as a term used in Monero is ...


6

As in my comment: The transaction size is mainly determined by the number of outputs. The number of inputs and mixin have smaller impact on the tx size. To be more precise, each output comes with a range proof using Borromean ring signature containing 64 pubkeys (representing commitments of all digits) and 2*64+1 scalars. This amounts to 193 instances of ...


6

The only change from that list which actually requires a HF is the minimum / uniform ringsize. The other 2 can be rolled out at any time. AFAIK, the current list for the upcoming hard fork is: Only RCT transactions will be allowed Minimum / uniform ringsize Range proof size reduction and the exact date hasn't been decided yet. The discussion on 2. can be ...


6

First, it should be noted that sweep_all combines all available unspent outputs in the current account in a single transaction. Thus, your transaction may have a lot of inputs, which could be detrimental to your privacy if you received outputs that are close in proximity, i.e., from the same transaction or from multiple transactions in the same block. Now, ...


5

Output selection is random. That is, simplewallet will pick one random output in your available outputs list, then again, and again, until the total is enough to satisfy the amount to send plus the fee. This means that, depending on what outputs are selected first, you may need either a large set of outputs (if you pick small values ones first), or a small ...


Only top voted, non community-wiki answers of a minimum length are eligible