<a​lfieedwards:monero.social> Hello, I guess it could be the right room for this. Could someone explain or give more details on an observation made by Justin Ehrenhofer (SamsungGalaxyPlayer) regarding recent CCS wallet breach? In particular, what interests me is how Txs bb77d...d1a58 and then both 2c5b4...ad5ec and 06550...ca47b were linked together? How true spends were estimated? Unusual fee amounts? Or just<clipped message>

<a​lfieedwards:monero.social> time correlation? Thanks in advance!

<a​lfieedwards:monero.social> monero-project/meta #916

<a​lfieedwards:monero.social> monero-project/meta #916#issuecomment-1791309479

<a​lfieedwards:monero.social> monero-project/meta #916#issuecomment-1791446149

He's "sgp" on IRC, doesn't seem around atm, unless behind a bridge.

<r​ucknium:monero.social> Alfie Edwards: Did you read the explanation by SGP here?: moonstoneresearch.com/2023/11/03/Postmortem-of-Monero-CCS-Hack.html

<a​lfieedwards:monero.social> Thanks, that is what I looked for

<t​rasherdk:monero.social> Mixing testnet (280xx) and stagenet (380xx) won't work 😆

<s​gp:magicgrants.org> sgp here, let me know if you have questions

<s​gp:magicgrants.org> What are the best ways to learn what Monero transactions are dropped/modified as a result of a reorg? monero.stackexchange.com/questions/…-transactions-that-were-dropped-mod

It doesn't happen often because we don't usually have reorgs more than 2-3 blocks deep. But if some transactions become invalid, they'll stay in mempool for, IIRC, 5 days, and it will be clearly visible

Because they will be invalid and unmineable

There's also "kept_by_block" in transaction info when you call RPC to get the mempool

kept_by_block = transaction was in a block and was reorg'd