Old unconfirmed Dust tx's won't go away

[HELP.org]

I have a couple of those unconfirmed tx's from those 1Sochi 1Laxo addresses and they are more than a month old.  Gavin posted this about the QT wallet

That is a feature of Bitcoin-Qt. Unconfirmed dust transactions don't enter the memory pool, so they are not relayed, not included in blocks being mined, and not displayed by the wallet.

If I recall correctly, if they DO get mined into a block by somebody then they are displayed. Ignoring them and not adding them to the wallet in that case might be a nice feature, although today's dust might be tomorrow's treasure if prices rise another couple orders of magnitude.

Why do these tx's show up on the Armory wallet at all and why are they there more than a month later?  Normally they disappear after a couple days.  Does it mean they are being rebroadcast or is it some other reason?

[1713569319]

1713569319

[1713569319]

1713569319

[1713569319]

1713569319

[1713569319]

1713569319

[1713569319]

1713569319

[etotheipi]

Armory has a memory pool file that persists between loads.  However, you can manually clear it using Help->Clear All Unconfirmed

If they show up again, then Bitcoin Core is rebroadcasting them (perhaps to try to get them mined?).

[HELP.org]

Armory has a memory pool file that persists between loads.  However, you can manually clear it using Help->Clear All Unconfirmed

If they show up again, then Bitcoin Core is rebroadcasting them (perhaps to try to get them mined?).

That worked.  if Bircoin-qt is not relaying why did they show up in the first place?

[etotheipi]

Armory has a memory pool file that persists between loads.  However, you can manually clear it using Help->Clear All Unconfirmed

If they show up again, then Bitcoin Core is rebroadcasting them (perhaps to try to get them mined?).

That worked.  if Bircoin-qt is not relaying why did they show up in the first place?

Bitcoin-Qt was relaying them (I had some of that dust, too).  It but it wasn't re-relaying them, so clearing the mempool made them go away. 

It's possible, if you restart Core, that its memory pool will clear allowing them to be re-relayed again if someone rebroadcasts, but I think the newer versions of Core should reject them as non-standard and not relay them.

[HELP.org]

Armory has a memory pool file that persists between loads.  However, you can manually clear it using Help->Clear All Unconfirmed

If they show up again, then Bitcoin Core is rebroadcasting them (perhaps to try to get them mined?).

That worked.  if Bircoin-qt is not relaying why did they show up in the first place?

Bitcoin-Qt was relaying them (I had some of that dust, too).  It but it wasn't re-relaying them, so clearing the mempool made them go away. 

It's possible, if you restart Core, that its memory pool will clear allowing them to be re-relayed again if someone rebroadcasts, but I think the newer versions of Core should reject them as non-standard and not relay them.

I think that is it.  they got into Armory's memory pool before I had upgraded Bitcoin-QT and it didn't go away until I cleared it.  thx