Debug.log - loop ResendWalletTransactions()

+1 vote

Hello, I created a wallet in a node (A) and then I imported the same wallet in a another node (B) (importaddress). Making transactions, I notice only in B this kind of messages:

2019-10-10 10:50:57 Tx d1c23f19b4c1a95c0da2254dc4a1da95454b2726b104d4d218ab68cc5b829f1f was not accepted to mempool, setting INVALID flag
2019-10-10 10:50:57 Tx 70f64c157c5ed3278de7cfd991ae278d132471749c2afc6a22216e49519d6ad5 was not accepted to mempool, setting INVALID flag

….

….

2019-10-10 10:50:57 Tx d1c23f19b4c1a95c0da2254dc4a1da95454b2726b104d4d218ab68cc5b829f1f was not accepted to mempool, setting INVALID flag
2019-10-10 10:50:57 Tx 70f64c157c5ed3278de7cfd991ae278d132471749c2afc6a22216e49519d6ad5 was not accepted to mempool, setting INVALID flag


I think this's a "system problem" but I don't understand why are they write in an undefined loop? Is there a way to stop it?

"version" : "1.0.6",
"nodeversion" : 10006901,

asked Oct 10 by anonymous
Extra info: each transaction had as source and destination the same wallet created in node A and imported in B. Each transaction was sign in the node A.

1 Answer

0 votes
It sounds like you have conflicting transactions in your network, because two transsactions are trying to spend the same UTXOs (previous unspent transaction outputs). Have you been sharing private keys or doing anything else unusual that could cause this?
answered Oct 10 by MultiChain
Yes, it is! I sent "thoughtful" transactions (with the same source and destination wallet). It was just a test…
Sure, doing so It generated conflict in mempool.

Thank a lot
...