Luke Dashjr

@ryanofsky There already is, why are you ignoring it? #19463

>What if user wants to add another A and B outputs (that is to have two A outputs and two B outputs for whatever reason)? `$ bitcoin-cli bumpfee '{"outputs": {"A":...

>Maybe have one argument outputs to specify a set of outputs and another argument like output_mode=add/output_mode=replace (choose better names though) to switch between different ways to handle them. The add...

This is already part of #7533 At the very least, please try to use the short rejection reasons therein...

https://github.com/bitcoin/bitcoin/pull/7533/commits/c59e7166253e962043b5fdccd5de8a21969d21e0

Might be better to have the index at the end, not sure.

Why do you want to limit it to debug output? Reasons should be in the reason field.

Prefer to use the existing `bad-txns-input-script-unknown`, `bad-txns-input-scriptsig-failure`, `bad-txns-input-scriptcheck-missing`, and `bad-txns-input-scriptcheck-sigops`

How does this handle resolvers? eg, static glibc 2.33 applications break on systems with glibc 2.34...

> (and less important)... Not really an issue for Bitcoin Core, Yes, it is absolutely a very important issue. We are not going to rely on non-free software.