📅 Original date posted:2011-08-05
🗒️ Summary of this message: A mechanism to deanonymize Bitcoin transactions involves connecting to every node in the cloud and identifying the first IP consistently relaying transactions for a given identity.
📝 Original message:On 2011 August 05 Friday, Gavin Andresen wrote:
> "As reported, I've got a BitCoin deanonymization mechanism. It's not
> complicated.
>
> Connect to every node in the cloud, discoverable via sweeping/IRC/get_peers
> messages. The first IP to consistently relay transactions for a given
> identity, is the given identity.
Transaction forwarding could be randomised slightly, by randomising the
outgoing relay order; and adding a random delay between each forward. Even
the massively connected monitor can't represent _all_ the connections on every
real node, so it would have no way of knowing whether it got any transaction
from the originator or because it got a fast path through the first N nodes to
receive it.
Andy
--
Dr Andy Parkins
andyparkins at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110805/dd11a165/attachment.sig>;
Andy Parkins [ARCHIVE] /
npub1nx…7wjrv
2023-06-07 02:11:50
in reply to nevent1q…evcg
Author Public Key
npub1nxlvf9mj3jzgue25n5d9y47s3h5hvg0ded9hwpejdxj9mtrs34vs97wjrvPublished at
2023-06-07 02:11:50Event JSON
{
"id": "e583be7cb4c48bfea74c8eca4ba8a68fc6af6d7476427e24fe7f71982653ccbd",
"pubkey": "99bec497728c848e65549d1a5257d08de97621edcb4b77073269a45dac708d59",
"created_at": 1686103910,
"kind": 1,
"tags": [
[
"e",
"3fd0921829ed37c0f8350ddeea75079340fd443c86a6a3228d2e1e0ae90eb86b",
"",
"root"
],
[
"e",
"165408499953e545ab09f8ecbd6890f63dc461049f9c638bebbe6e2dfa0065d0",
"",
"reply"
],
[
"p",
"cd7fc091d5673974c36bf2b5c6e8b4a5079d6821b95f6719fd48571aeb25b785"
]
],
"content": "📅 Original date posted:2011-08-05\n🗒️ Summary of this message: A mechanism to deanonymize Bitcoin transactions involves connecting to every node in the cloud and identifying the first IP consistently relaying transactions for a given identity.\n📝 Original message:On 2011 August 05 Friday, Gavin Andresen wrote:\n\n\u003e \"As reported, I've got a BitCoin deanonymization mechanism. It's not\n\u003e complicated.\n\u003e \n\u003e Connect to every node in the cloud, discoverable via sweeping/IRC/get_peers\n\u003e messages. The first IP to consistently relay transactions for a given\n\u003e identity, is the given identity.\n\nTransaction forwarding could be randomised slightly, by randomising the \noutgoing relay order; and adding a random delay between each forward. Even \nthe massively connected monitor can't represent _all_ the connections on every \nreal node, so it would have no way of knowing whether it got any transaction \nfrom the originator or because it got a fast path through the first N nodes to \nreceive it.\n\n\n\nAndy\n\n-- \nDr Andy Parkins\nandyparkins at gmail.com\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 198 bytes\nDesc: This is a digitally signed message part.\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110805/dd11a165/attachment.sig\u003e",
"sig": "f963ef9c943f5943d93807d515bc5714ef342f99d34d9e32e262a2d7513f5fea0031e7319a5784722934f48d75cccbe7252aed8b398aa34510b21e6ad7438d84"
}