Distinguish between bad-txns-inputs-missingorspent about bitcoin

[glozow]

An issue is that we don't actually know if it's missing or spent, we just don't see the UTXO available. Knowing "spent" for certain would require querying whether the UTXO existed at some point in the past...

I would like to fine grain error which informs whether the input is actually spent or if it is an orphan tx. I have logic that wants to do different things whether the parent is confirmed or not.

Not sure if I'm misunderstanding the situation, but a few ideas

• gettxspendingprevout tells you if something has a mempool conflict
• If something is confirmed and bitcoind sees one of its outputs in the UTXO set ("txn-already-known" means "this tx already confirmed" if you want to try looking for that error).
• The wallet has logic to see if its transactions have been conflicted by a block (see "confirmations" in rpc results).
• Consider just resending the parent always? If it's missing, problem solved. If it's in mempool already, no harm done. If it's confirmed and has an output available, "txn-already-known". If it conflicts with something, "bad-txns-inputs-missingorspent".

[sanket1729]

Thanks for the response. This resolves my issue