Hi all,
I am trying to figure out the source node of a propagated transaction in the bitcoin network. My approach is to set up multiple nodes and analyze the received transactions.
Additionally, I was curious on what I need to do to connect to a bitcoin node running tor(I'm guessing I have to configure the SOCKS5 proxy). After the TOR configuration can I just add a peer with their .onion address?
I am also planning to set the maximum connections to say 1000 per node. I was told this is a bad idea because it will slow down processing at my node if I don't have enough resources, but it seems like a good way to get transactions from multiple nodes.
Any ideas and opinions will be highly appreciated.
I am trying to figure out the source node of a propagated transaction in the bitcoin network. My approach is to set up multiple nodes and analyze the received transactions.
Additionally, I was curious on what I need to do to connect to a bitcoin node running tor(I'm guessing I have to configure the SOCKS5 proxy). After the TOR configuration can I just add a peer with their .onion address?
I am also planning to set the maximum connections to say 1000 per node. I was told this is a bad idea because it will slow down processing at my node if I don't have enough resources, but it seems like a good way to get transactions from multiple nodes.
Any ideas and opinions will be highly appreciated.
You need to do something along the following:
1. Make a index list of all Bitcoin Nodes IPs.
Multiple Block explorers might be helpful.
2. Check the block height of each node,
You need to verify, but I don't think a new transaction can be added if the node is not in sync with the blockchain.
If this is accurate, then you can exclude all nodes not in sync.
Now comes the tricky part. You need access to the internet backbone service providers.
3. This would allow you to verify every IP address Connected to the Node IP.
4. Then you can cross reference the packets sent to each node.
(A Packet Sniffer would help in determining key aspects.)
Cross Reference based up the transaction time.
An easier method, would be to setup a listening bot at the mining pools IP, recording the connected IPs and then record the time of adding of the transaction to the mempool. Then use the data from the ISP backbone to cross reference all of the IPs at that point. Using a Packet sniffer to backtrack to the 1st node to add the transaction.
Something along those lines.
As far a Tor goes, you create a few tor nodes and cross reference attached ip address while using a packet sniffer.
* If you do have access to the ISP backbone date, you can also get the hardware network address that is attached the PC,
find the government database that holds the hardware network address and you can get the serial # of the PC/Laptop that is being used.
Then a quick check to see where that PC/Laptop was purchased and if the user was dumb enough to buy it with a CC or debit card.
From there you can get their home address. * The ISP BackBone Providers also link the IP address and time with Physical location.*