pull down to refresh

13 sats \ 1 reply \ @yo2xncv0 15 Jan \ parent \ on: Is ecash private enough for dark markets? privacy
The onus should be on the original people claiming that Monero was traced, but ok I'll play the game. All articles about the arrests mention credit card fraud and the Mercari e-commerce platform in connection to how they were caught (or give no details at all on how they "traced" Monero): https://u.today/100-million-yen-crypto-scam-exposed-via-monero-xmr-data-in-japan-organizer-arrested https://regtechtimes.com/18-caught-in-monero-money-laundering-scheme-in/ https://www.perigon.io/news/finance/2024/10/21/japan-arrests-18-monero-fraud-case https://cryptoslate.com/japanese-authorities-dismantle-monero-linked-scam-in-landmark-investigation/
Your tool doesn't "automatically eliminates every decoy spender and heuristically identifies the real spender". It's all manual guessing. It's a glorified Monero block explorer that you added buttons onto.
Some LN custodians and LSPs have really good privacy policies
You must be kidding. Privacy policies? Lol
You talk about encryption on P2P Lightning traffic as if it applies to the vast majority of Lightning users on custodians and LSPs. Using a remote Monero node reveals far less data to 3rd parties than custodial LN or LSPs, enforced by encryption (not privacy policies), and all without giving up custody to ecash mints.
Like I said the remote node can't see amounts, addresses, balances, true spend, etc: https://localmonero.co/knowledge/remote-nodes-privacy
write
preview
21 sats \ 0 replies \ @supertestnet 15 Jan
Your tool doesn't "automatically eliminates every decoy spender and heuristically identifies the real spender". It's all manual guessing.
It's not all manual guessing, it automatically applies heuristics when possible. You can see an example in this video:
Note that I don't manually guess anything. I simply pick a transaction from a recent block and it automatically identifies the decoys: namely, every Possible Spender except #1 is (according to the automatically-applied heuristics) a decoy. #1 is the "real" spender.
The heuristic applied in that case is called Recency Bias and is discussed as a standard characteristic of monero's decoy selection algorithm in the excellent Breaking Monero series (see Episode 5).
The recency bias heuristic takes advantage of the fact that the decoy selection algorithm used in the most popular monero wallets is biased toward selecting keys from recently created txos (on the principle that actively circulating coins are more likely to be spent than old ones). When you have a group of "new coin" decoys, coins that are significantly older stick out like a sore thumb, and you can plausibly identify them as the real spender's coins.
Consequently, I didn't need to manually eliminate the decoys; my software simply noticed that every decoy in the example transaction was a recently-created txo, but there was one txo that was much older. That one stuck out and, per this heuristic, was the real spender, because it is very unlikely that the decoy selection algorithm would choose that txo.
reply