hi

<s​packle_xmr:matrix.org> I think this got some attention recently but I want to point it out.

<s​packle_xmr:matrix.org> This tx has a high fee per byte but is stuck in the mempool: xmrchain.net/tx/12bcfcb24bafcfcb9fe…b4ffec6e65c61ce033ab31c87230f20f70e

<s​packle_xmr:matrix.org> It is the oldest tx by a significant margin.

"1 double spends"

must be this one

<s​packle_xmr:matrix.org> Interesting. Thank you for the quick response.

<r​ucknium:monero.social> sech1: Does that mean that your node was at the "boundary" of the network topology where some of the nodes you connected to sent you one of the double spend txs, and one or more of the other nodes sent you the other double spend tx? Your node would not relay both of the double spends, right?

xmrchain node was too

No, it's more like this tx was in mempool already, but someone mined a block with a competing tx directly included

maybe someone tried to scam some merchant who accepts 0-conf

<r​ucknium:monero.social> Ok. monerod keeps the tx in the mempool in case there is a block re-org and it becomes valid, right?

That's my theory

yes, it keeps it because it can become valid