Weird TX Still in Mempool with Wrong `supported` Value

[adamkrellenstein]

there seems to be an event in the mempool with underlying tx that was confirmed 2 months ago

hum.. same tx_hash ? sometime there is the same event with another tx_hash.. anyway I think we should add our own expiration system for tx in mempool (for now we wait a remove message from ZMQ)

https://gist.github.com/mattmarcello/ae4bd906c25b97eb65077f735f3d2dd4

[ouziel-slama]

I can't explain or reproduce but I added two sanity checks here https://github.com/CounterpartyXCP/counterparty-core/pull/2217:

• Test that the mempool is properly cleaned after each regtest transaction is confirmed
• Delete mempool events older than 24 hours

[ouziel-slama]

and there is also now a regtest test to check that the mempool is filled