How to delete invalid tx?

+1 vote

we found some txs were not accepted into menpool, how to delete them?  because they  cause CPU usage to more than 100%.


2018-07-06 13:08:17 Tx 5f51acf5a538b0a649e24598602c4d0601d67249ca972ae8e4eaca713690823e was not accepted to mempool, setting INVALID flag
2018-07-06 13:08:17 Tx 6d6efb8262d6f86ed118dcf01e1987a9ed7699671e7b38a23ce0c2db0c721a31 was not accepted to mempool, setting INVALID flag
2018-07-06 13:08:17 Tx 236b33c2df355ca49d58a8b68a199c5a26c194a28f183f457e140302fcbab207 was not accepted to mempool, setting INVALID flag
2018-07-06 13:08:17 Tx 8f78ea4491194f1d936f1099ea8aade03afa89703928c22ded8221ccd222008b was not accepted to mempool, setting INVALID flag
2018-07-06 13:08:17 Tx e93266338a26e512983bbf0fbfe2028cf899035df2c381e23d6cf6af1066017b was not accepted to mempool, setting INVALID flag
2018-07-06 13:08:17 ERROR: AcceptToMemoryPool : inputs already spent
2018-07-06 13:08:17 Tx e23dd9e54bdf995245ee10be89ca7d23278736c3358fcf50bef1ff32159166db was not accepted to mempool, setting INVALID flag
2018-07-06 13:08:17 ERROR: AcceptToMemoryPool : inputs already spent
2018-07-06 13:08:17 Tx 34b1277f6a91519e535adba1096ab44d80882fa8a526a50f561102af7465afed was not accepted to mempool, setting INVALID flag
2018-07-06 13:08:17 ERROR: AcceptToMemoryPool : inputs already spent 

asked Jul 6 by allainzhang2018
Can you please explain where these transactions are coming from? The network? Newly created transactions on this node? Or previously created transactions on this node that are being retransmitted?
I think these are from a "fork". Someday I found the blocks of this node were lower than other nodes , and this node had the "mine" permission.

So I revoked the mine permission , and restarted the node.

Maybe the network error.

How to do with these invalid transcations?

1 Answer

0 votes
These invalid transactions will just be rejected and then be forgotten, so I don't think they should concern you. Based on the other question I don't think they are the cause of the excess CPU load – that is due to the very large number of addresses in the wallet.
answered Jul 10 by MultiChain