Title: utxotrack Post by: albert0bsd on September 02, 2023, 12:51:38 AM Hey everyone.
Lately I get some interest about Bitcoin transaction privacy. I've been testing various scenarios on the testnet, and I've come to realize that it can be quite challenging to determine if your UTXOs share previous TXIDs or addresses in common. Manual tracking can be especially tricky. Here are a couple of resources I found that might be helpful: Know Your Coin Privacy (KYCP): https://kycp.org/ https://oxt.me/ However, please note that these resources still require some manual searching, and the results may not always be conclusive at first sight To address this challenge and assist me in selecting the right UTXOs for certain transactions having considering the privacy and other factors, I develop a small and not complex script in python Utxotrack (https://github.com/albertobsd/utxotrack) available on github This script works seamlessly on both the Bitcoin mainnet and testnet. Currently, it's a standalone script, but I plan to expand its functionality in the future if you like it. The main idea is to identify any instances where transactions share reused addresses or TXIDs across different levels of their ancestry. It's a step toward enhancing privacy in Bitcoin transactions. Just to clarify, I didn't really check if there are other scripts for this. I'm just into coding, and this task seemed like a relatively simple one to work on. I open this topic to get feedback about the script and get some interesting ideas that could be helpful to this community. If you want to talk about UTXOs privacy or some other topic I suggest open a new topic for it. Executing the script. Code: python3 utxotrack.py Code: Missing arguments expected: Let’s to said that you have an utxo in some TXID Code: python3 utxotrack.py bitcoin a95e587f7ed6813b567c291f91db80785c5e5a3d73f97222f0d3dfcf04e988f3 1 Code: Level 0 TX a95e587f7ed6813b567c291f91db80785c5e5a3d73f97222f0d3dfcf04e988f3 have 1 inputs and 1 outputs. But if we increment the level to 3 or 4 the things become more interesting, the program mark with a different color those TX and address that appear more than one time Code: python3 utxotrack.py bitcoin a95e587f7ed6813b567c291f91db80785c5e5a3d73f97222f0d3dfcf04e988f3 4 Code: Level 0 TX a95e587f7ed6813b567c291f91db80785c5e5a3d73f97222f0d3dfcf04e988f3 have 1 inputs and 1 outputs. It is normal that a single utxo have some repeated address or TXID in its ancestors a lot of explanations can fit here (Consolidations in the same address, Change address equal to the source address, mixers, etc…) But the idea is to check different utxos and check if they share something in common up to 5 levels of ancestors (I said 5 here because more than it can be very messy some times, i am going to open a topic asking for that ) Feel free to check out the script and share your thoughts. I'm also open to suggestions and improvements, so please let me know if you have any ideas to make it even more effective. |