Currencies that implemented Zerocoin are forks from the bitcoin source code and not soft forks. It could be implemented in Bitcoin with a soft fork update if there would be interest for it.
-
Decentralised vs centralised.
-
When input/output pair are invalid.
-
By increasing the number of small transactions.
-
Coinjoin transactions work today, Zerocoin requires a change to the Bitcoin protocol.
-
What is the benefit of CoinJoin over BitLaundry, if any?
You dont have to trust on 3rd parties to make the transaction (decentralized). On CoinJoin you finally decide if signing the transaction or not , and if you sign it , it will be processed only if others do as well.
Also anonimity could be much higher than BitLaundry depending on the number of participants -
About halfway down, Maxwell writes: “failure (retry) risk mean that really huge joint transactions would not be wise.” Explain failure (retry) risk
it means that if more parties participate in the transaction , more chances to failure the transaction due to other party not signing it , for example. -
How can anonymity set be increased while keeping small transaction sizes?
Increasing the number of people who participate -
What is the main benefit of CoinJoin over Zerocoin?
Zerocoin need a softfork , while coinjoin works today without any need to change bitcoin protocol.
- Coinjoin is a decentralised trustless service. You do not need to trust someone like BitLaundry that they won’t steal your Bitcoin.
- When one party of the Coinjoin transaction does not sign its transaction or if someone spends their UTXO used for the Coinjoin in another transaction before the transaction can complete.
- As higher the number of participants per transactions as higher the anonymity level.
- Coinjoin does not require any changes in the Bitcoin network. It is based on existing functionality and can be directly used as a tool. Zerocoin would require a soft fork of the Bitcoin network.
-
What is the benefit of CoinJoin over BitLaundry, if any?
BitLaundry is more centralized, so you need to trust your fund to a 3rd party. Since CoinJoin has the opposite philosophy, where the users agree on several inputs and outputs which must be individually signed and after being merged. -
About halfway down, Maxwell writes: “failure (retry) risk mean that really huge joint transactions would not be wise.” Explain failure (retry) risk.
The risk of other participants failing to co-sign the joined transactions, or a DOS attack.
If one input/output pair is rejected, everyone needs to update their signature. -
How can anonymity set be increased while keeping small transaction sizes?
By increasing the number of transactions. -
What is the main benefit of CoinJoin over Zerocoin?
Zerocoin needs a soft-fork to work with bitcoin protocol, whereas CoinJoin doesn’t.
- CoinJoin is (more) decentralized (p2p really)
- failure (retry) risk is when one participant does not want to validate the transaction = transaction fails, need to retry
- the BTC that we are trying to transfer could be spread across multiple small transactions which increases the anonymity set
- no need for soft-fork or any protocol changes
What is the benefit of CoinJoin over BitLaundry, if any?
The signatures, one per input, inside a transaction are completely independent
of each other. This means that it’s possible for Bitcoin users to agree on a
set of inputs to spend, and a set of outputs to pay to, and then to individually
and separately sign a transaction and later merge their signatures. The transaction
is not valid and won’t be accepted by the network until all signatures are provided,
and no one will sign a transaction which is not to their liking.
CoinJoin is not centralised fff
About halfway down, Maxwell writes: “failure (retry) risk mean that really huge joint transactions would not be wise.” Explain failure (retry) risk.
really huge joint transactions would not be wise
How can anonymity set be increased while keeping small transaction sizes?
if you have can build transactions with m participants per transaction you can create a sequence of m*3 transactions which form a three-stage switching network that permits any of m^2 final outputs to have come from any of m^2 original inputs (e.g. using three stages of 32 transactions with 32 inputs each 1024 users can be joined with a total of 96 transactions). This allows the anonymity set to be any size, limited only by participation.
What is the main benefit of CoinJoin over Zerocoin?
Zerocoin requires a soft-forking change to the Bitcoin protocol, which all full nodes must adopt, which would commit Bitcoin to a particular version of the Zerocoin protocol. This cannot happen fast—probably not within years
CoinJoin transactions work today, and they’ve worked since the first day of Bitcoin. They are indistinguishable from normal transactions and thus cannot be blocked or inhibited except to the extent that any other Bitcoin transaction could be blocked.
Can you explain why?
I’m understanding it as, the larger joint transactions, increases the risk of some participants “going down” during the process of Coinjoin or the possibility of DOS attack.
-
One advantage of CoinJoin over BitLaundry is that it doesn’t require any modification in protocol or trust in an external party to complete a transaction.
-
“Failure (retry) risk” refers to the possibility of a DOS attack, or one of the participants spending the available funds after having signed but before all parties have signed. The more participants there are, there is a larger risk of this happening.
-
The anonymity set of a transaction can be increased by distributing it into several smaller ones.
-
Unlike Zerocoin, CoinJoin doesn’t require a soft fork and can be done today.
1. What is the benefit of CoinJoin over BitLaundry, if any?
The transactions are co-joined with other transactions and signed by multiple signatures in a decentralized manner which enhances privacy.
On the other hand, BitLaundry is centralized, requiring users trust that the service will mediate fund transfers as they advertise. Also, it is less private considering each transaction is treated as its own entity and so it becomes easier to deanonymize the identities of the people making transfers.
2. About halfway down, Maxwell writes: “failure (retry) risk mean that really huge joint transactions would not be wise.” Explain failure (retry) risk.
It could be in the event of DOS attack, refusal to sign transactions by a particular party, failure to retrieve signatures within a time limit, conflicting created transactions.
3. How can anonymity set be increased while keeping small transaction sizes?
By adding multiple transactions from different participants per CoinJoin transaction and breaking up the CoinJoin transaction in a way which ensures the overall transaction size isn’t too large which can lead to failures…e.g. retry
4. What is the main benefit of CoinJoin over Zerocoin?
No soft-forking change required.
-
What is the benefit of CoinJoin over BitLaundry, if any?
BitLaundry is a centralized entity that adds a required trust to the equation. Bitjoin really only requires two individuals that can a agree on the inputs and outputs. -
About halfway down, Maxwell writes: “failure (retry) risk mean that really huge joint transactions would not be wise.” Explain failure (retry) risk.
Failure risk is one of the party’s not signing the transaction, making the other sides’s attempt fail. -
How can anonymity set be increased while keeping small transaction sizes?
The transactions are cheap with no limit to said transactions, so more participants will join and increase the anonymity. -
What is the main benefit of CoinJoin over Zerocoin?
The main benefit is that it doesn’t require a soft fork of the bitcoin network.
1 Bitlaundry is a third party! You take quite a risk sending them your bitcoin whereas CoinJoin only requires minor agreement adds to the users in order to gain extra privacy.
2.Group of people does not validate the txn thus making you retry the process all over again.
3. Making more tnxs with Coinjoin method
4. Does not require any changes to the protocol!
-
BitLaundry is essentially a 3rd party involved in the transactions. CoinJoin remains anonymous in the sense that it is an agreement of inputs and outputs. The Bitcoin protocol
-
It is a stop to validate or sign a transaction. You could ask yourself out of 50 people, why did that ONE person choose not to sign? It could be argued it is an action to cheat the system.
-
Smaller transactions mean more moving parts; more things to asses and more angles to cover
-
Zerocoin forces a FORK in the bitcoin protocol.
- What is the benefit of CoinJoin over BitLaundry, if any?
Bitlaundry is centralized, CoinJoin is decentralized. Users on coinjoin agree to certain amount of input and pay out.
2. About halfway down, Maxwell writes: “failure (retry) risk mean that really huge joint transactions would not be wise.” Explain failure (retry) risk.
risk that the CoinJoin transaction fails, either because of a DOS attack or because a member of the transaction is not able/willing to perform its part of signature. It is an increased risk when it comes to huge transactions because it would put at risk all other parties involved.
-
How can anonymity set be increased while keeping small transaction sizes?
Increasing number of transactions in process -
What is the main benefit of CoinJoin over Zerocoin?
No soft fork?
Yes, Coinjoin works on Bitcoin now
thank you for your response! appreciate it!
- BitLaundry is centralized and CoinJoin is P2P.
- There is a risk of failure because people can back out of a transaction before it is confirmed.
There is also the risk of a DOS attack. - By increasing the number of inputs in a transaction.
- Zero coin needs a soft fork.
The user can back out by not signing the tx (before its even put in the mempool to get confirmed). This is effectively a DOS because it prevents other users from completing the service
-
BitLaundry is centralized, CoinJoin is decentralized.
-
It would be happen if a party fails to sign or get DOS attacked.
-
By making many transactions.
-
Zerocoin asks for softfork to the bitcoin while Coinjoint does not require a softfork.