Is there an existing issue for this?

• I have searched the existing issues

Current behaviour

If we receive a transaction which spends from an unconfirmed parent, and that parent is replaced, the child does not get marked as conflicted but rather only as inactive. If the child contains an input from our wallet, that input cannot be reused until the child is abandoned.

See also ACINQ/eclair#2818

Expected behaviour

We should try to detect if a such a child transaction becomes conflicted due to a parent becoming conflicted and mark it as such.

Steps to reproduce

A (failing) test for this behavior can be found at achow101@213fa91

Relevant log output

No response

How did you obtain Bitcoin Core

Compiled from source

What version of Bitcoin Core are you using?

master@128b4a80387d322a7810d8716eccdac95ff9b8cd

Operating system and version

Arch

Machine specifications

No response