You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 19, 2020. It is now read-only.
Post-Mix Wallet Uniformity Requirement: Post-mix wallet SHOULD prevent its users to utilize RBF. Replace-by-Fee, RBF is a often used feature. On the one hand its usage is beneficial, on the other hand the way RBF is used by a wallet software helps blockchain analysis to identify the wallet software in used.
Creation of a common algorithmic utilization of RBF should be an interest of future research. Bram Cohen's article might be a good starting point.
It would be better if the wallet would generate RBF an non-RBF transactions randomly, yet still not utilizing RBF. This way, if a transaction was RBF, it's still not obvious if the wallet wasn't a ZeroLink wallet.
In fact, maybe the wallet could even monitor the percentage of RBF transactions on the network and set the likelihood decidision if the transaction is RBF or not accordingly.
The text was updated successfully, but these errors were encountered:
It would be better if the wallet would generate RBF an non-RBF transactions randomly, yet still not utilizing RBF. This way, if a transaction was RBF, it's still not obvious if the wallet wasn't a ZeroLink wallet.
In fact, maybe the wallet could even monitor the percentage of RBF transactions on the network and set the likelihood decidision if the transaction is RBF or not accordingly.
The text was updated successfully, but these errors were encountered: