I am planning on building a utxo privacy analyzer, where you can select a series of privacy metrics to analyze a transaction by. The result will then say if the utxos included in the transaction passed or failed the various privacy metrics.
A few privacy metrics to watch for I have so far are,
- number of consecutive coinjoin rounds that a utxo came from.
- choose your anonymity set, aka how many txs should look like yours (aka equal output) in a tx.
- No change.
- no small change.
- no reused addresses
- reveal least amount of wealth
- reveal least amount of past tx history, aka don't combine utxos, especially not change outputs.
- don't mix post mixes (or any post mix tx change) from different rounds.
- don't mix postmix (or any post mix tx change) and non mixed.
- reduce change detection
- no round number payments.
- no same script type for the inputs and only one output.
- largest output amount heuristic (this is weak)
- spending to an exchange, it is obvious you are the change
- break the unnecessary input heuristic.
- more than one change output.
- change output should be of similar size of payment
- no dust attacked coins.
- break the common input ownership heuristic.
- break volume or other pattern recognition analysise.
- the change should not always be in the same output position.
- timing analysis, make sure you are not always receiving transactions on the same day.
- make sure do not spend utxos are not spent
- no kyc coins.
Does that sound like a useful tool to you?
bitcoin_mises / Bitcoin Mises
npub1f9…l3x8k
2024-10-16 14:27:40
in reply to nevent1q…fryy
Author Public Key
npub1f94ly2mkuc648vk2cuxyfdfcvumgkjmkzgzn5trcvz0nz3pjfqrsql3x8kPublished at
2024-10-16 14:27:40Event JSON
{
"id": "3654c06a023c6ebcdb6b7f93193e2562148d7c3e0cde27c253d70ae8fd0fd28e",
"pubkey": "496bf22b76e63553b2cac70c44b53867368b4b7612053a2c78609f3144324807",
"created_at": 1729088860,
"kind": 1,
"tags": [
[
"e",
"be62b869bb1b6545713d18bfdec748b06e999eca378d481c0a03ef8ef816d5d3",
"wss://relay.primal.net",
"root"
],
[
"p",
"7bfda8851f0bebfaad675be189f78532e95579270dd9827d6a6df66d7a768195"
]
],
"content": "I am planning on building a utxo privacy analyzer, where you can select a series of privacy metrics to analyze a transaction by. The result will then say if the utxos included in the transaction passed or failed the various privacy metrics.\n\nA few privacy metrics to watch for I have so far are, \n - number of consecutive coinjoin rounds that a utxo came from. \n - choose your anonymity set, aka how many txs should look like yours (aka equal output) in a tx.\n - No change. \n - no small change.\n - no reused addresses\n - reveal least amount of wealth\n - reveal least amount of past tx history, aka don't combine utxos, especially not change outputs.\n - don't mix post mixes (or any post mix tx change) from different rounds.\n - don't mix postmix (or any post mix tx change) and non mixed.\n - reduce change detection\n - no round number payments.\n - no same script type for the inputs and only one output.\n - largest output amount heuristic (this is weak)\n - spending to an exchange, it is obvious you are the change\n - break the unnecessary input heuristic.\n - more than one change output.\n - change output should be of similar size of payment\n - no dust attacked coins.\n - break the common input ownership heuristic.\n - break volume or other pattern recognition analysise.\n - the change should not always be in the same output position.\n - timing analysis, make sure you are not always receiving transactions on the same day.\n - make sure do not spend utxos are not spent\n - no kyc coins. \n\n\nDoes that sound like a useful tool to you?\n\n",
"sig": "ba24e39074a0f337bc375d373d4689662695acc3f1a1ed27e5549460e6e8b98bec70f063a0465d5d1ceacd03ebc46f0040f8983a8140baf3bdf92bbef5e3f42a"
}