A potential solution under consideration involves limiting the funding transaction to exclude any unconfirmed inputs, creating a more straightforward A → B → {C, D, CPFP bump} structure. This approach aims to mitigate complexities; however, it raises concerns because it may inhibit the common practice of chaining unconfirmed splices, an essential feature for some users.

Moreover, while the system can function adequately if the funding transaction confirms independently or through the Child Pays For Parent (CPFP) method—assuming B has a change output—the necessity of a change output is not ideal. The current workaround involves incorporating a change output in the funding or splice transaction on B's side to enable the application of CPFP as a defensive measure against transaction pinning. Although not optimal, this method is a continuation of existing strategies and does not present new challenges specifically introduced by v3. This strategy suggests that while v3 brings certain improvements, it also retains some of the limitations of previous iterations that require workarounds like the use of CPFP for transaction confirmation.