Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Bypass the need for multiple mixing rounds #21
Right now if the fixed denomination is 1btc and the user wants to mix 3btc, it must participate in 3 mixing rounds. However it could potentially register 3btc input and then register 3 times 1btc outputs. With this it can mix cheaper, because it only participates in one round.
This topic should be further explored.
The updated 'Simplified Protocol' section would look like this:
A. Simplified Protocol
Alice and Bob are the same user, however the Tumbler does not know this.
1. Input Registration Phase
Many Alices register their
Tumbler checks if inputs have enough coins, are unspent, confirmed, were not registered twice and that the provided proofs are valid, then signs the blinded outputs.
2. Output Registration Phase
Bobs register their signed outputs to the Tumbler.
3. Signing Phase
Tumbler builds the unsigned CoinJoin transaction and gives it to Alices for signing.
It also comes with some implementation difficulties, because all Bob outputs must be registered within 1 minute. Therefore the change between a user's Bob identities must be fast, since multiple Bob identities per user wer introduced. (Tor circuit changes.)
This would also make deanonymization somehow easier, because there'd be less distinct participant in a mix.