> in the context of a cryptocurrency a "transaction tracing tool" would be able to identify the source, destination and amount of transactions
I don't think it has to automatically do that. A tracing tool is good if it helps automate some parts of the tracing task even if other parts remain manual.
> random chance identifies the sender in "about 1 of 15 cases"
But random guessing uses no data. This tool uses *data* to identify the sender. A random guess would not be grounds for doing anything. A statistical analysis is worth a lot more.
> the recipient that is published on-chain is a one time stealth address. not useful for tracing since SAs break the transaction graph.
They do not break the transaction graph. Stealth addresses do not appear just once, they appear again whenever the recipient spends his money and possibly in other transactions as decoys. Filtering out the decoys leaves you with only the true spend tx. You can do that *because* there is a tx graph that stealth addresses appear multiple times in.
> and amounts remain opaque
Except part of the amount is visible (the fee) and gives you info about the amount in the outputs as well as in the inputs
> additionally, if it takes "a considerable amount of off-chain information" to *actually use* NOBODY is tracing monero transactions
Seems like you contradict yourself here. First you say "nobody" and argue that the data doesn't exist, then you admit some people might do it and governments might have that data.
Not a good look.
Super Testnet
npub1yx…c399s
2024-08-05 16:51:18
in reply to nevent1q…zcvw
Author Public Key
npub1yxp7j36cfqws7yj0hkfu2mx25308u4zua6ud22zglxp98ayhh96s8c399sPublished at
2024-08-05 16:51:18Event JSON
{
"id": "4f276b2c6ab22f4572ba19ba60a49ca8a947fb42dcf232985269a3fe714991a1",
"pubkey": "2183e94758481d0f124fbd93c56ccaa45e7e545ceeb8d52848f98253f497b975",
"created_at": 1722876678,
"kind": 1,
"tags": [
[
"e",
"e42b104f8d68b307db0e9c97737ca0ce10244cd9fbd2fc09b92b65b26407f34f",
"",
"root"
],
[
"e",
"a311071e8f352d6531b2e4b76831d0f5d9cca04f002707c892582af7e57d13cc"
],
[
"e",
"6f63a065534d814552918b52c946915cab478c382fb074d0fdd148046ebeb0ea",
"",
"reply"
],
[
"p",
"2183e94758481d0f124fbd93c56ccaa45e7e545ceeb8d52848f98253f497b975"
],
[
"p",
"5afa711a2e4f45294c9ca8033861a0e15a879e6fc1a4a6903640f7faeae0d7b8"
],
[
"p",
"f985d309197c805e1719c73185b574fc3ee407d7c1b6157dee99c6ace2599bbb"
]
],
"content": "\u003e in the context of a cryptocurrency a \"transaction tracing tool\" would be able to identify the source, destination and amount of transactions\n\nI don't think it has to automatically do that. A tracing tool is good if it helps automate some parts of the tracing task even if other parts remain manual.\n\n\u003e random chance identifies the sender in \"about 1 of 15 cases\"\n\nBut random guessing uses no data. This tool uses *data* to identify the sender. A random guess would not be grounds for doing anything. A statistical analysis is worth a lot more.\n\n\u003e the recipient that is published on-chain is a one time stealth address. not useful for tracing since SAs break the transaction graph.\n\nThey do not break the transaction graph. Stealth addresses do not appear just once, they appear again whenever the recipient spends his money and possibly in other transactions as decoys. Filtering out the decoys leaves you with only the true spend tx. You can do that *because* there is a tx graph that stealth addresses appear multiple times in.\n\n\u003e and amounts remain opaque\n\nExcept part of the amount is visible (the fee) and gives you info about the amount in the outputs as well as in the inputs\n\n\u003e additionally, if it takes \"a considerable amount of off-chain information\" to *actually use* NOBODY is tracing monero transactions\n\nSeems like you contradict yourself here. First you say \"nobody\" and argue that the data doesn't exist, then you admit some people might do it and governments might have that data.\n\nNot a good look.",
"sig": "900472dd9a281484f7eaf0f57e15e728f55f824ea95e3e0c0f4526b7b9788e64c5a8884f6e6266defb09456345b9bb5a0975552ef67a68253cb4a0d504f71fe0"
}