dcousens
commented
9 years ago @kristovatlas is there a possibility that we could [together?] write up a BIP for documenting best practice in regards to [at least] the following aspects of transaction creation:
- Input/Output ordering
- Fee calculation (if a "hard-fee" isn't set by the user, otherwise, how can we encourage masking it such that it appears more deniable)
- nLockTime
And various other aspects which currently, are just slightly different enough for each implementation that they leak vital bits of privacy such that transactions can easily be linked with a high probability between matching software.
CoinJoin does help some aspects of this, but in the end, even CoinJoin could benefit from a communally set BIP that addresses some of these concerns.
Related discussion to one aspect of this:
kristovatlas
Transactions generated by this software are still identifiable to this software.
The order by address change prevented the users change address being easily identified (it was always originally always the last output, sorting by address changed that).
However, what it did not prevent is the transaction being recognizable as being produced by this software.
To change this, we need to sort the inputs/outputs by some non-deterministic entropy or user secret.