What is the reason behind this PR?
There is a logic that needs to work if the TX is send.

What is the reason behind this PR? There is a logic that needs to work if the TX is send.

Do you mean check if tx is already confirmed? It's just to avoid meaningless operation. No one wants to pay fee to cancel an already existed transaction. And if it's existed, no need to execute the rest code.

I mean the cancel command

Can the node current cancel a normal tx with command?
That is why I'm asking about the conflict. Why this "feature" is really needed? In particular, manually.

Can the node current cancel a normal tx with command? That is why I'm asking about the conflict. Why this "feature" is really needed? In particular, manually.

Cancel tx when it's not on-chain yet.(In mempool)

I mean the cancel command

It's for use Conflicts attribute.

Cancel tx when it's not on-chain yet.(In mempool)

Why do not add this feature to any tx in this case as well? Why just the ability to cancel conflict (if not on-chain)?

Cancel tx when it's not on-chain yet.(In mempool)

Why do not add this feature to any tx in this case as well? Why just the ability to cancel conflict (if not on-chain)?

It's any tx, just in a new transaction attribute called Conflicts

Thanks, @superboyiii ,I will check code and test here as well.

@superboyiii format update please

@superboyiii format update please

Done