Both BIPs added a changelog entry on 2026-01-23 referencing the updated
BIP Process meta-BIP with the wrong form:
- bip-0360.mediawiki:404 rendered `[[bip-0003.mediawiki|BIP 003]]`, but
the actual file is `bip-0003.md`. The MediaWiki link therefore failed
to resolve to the BIP 3 page on the bitcoin/bips GitHub wiki render
and on the bips.dev / bip339 style mirrors — readers of the bip-0360
changelog landed on a 404.
- bip-0347.mediawiki:170 wrote the same reference as bare text
`BIP 003` with no link at all, so readers of bip-0347 had no way to
navigate to the BIP 3 they were meant to follow.
Rewrite both entries to use the canonical form `[[bip-0003.md|BIP 3]]`:
- `bip-0003.md` matches the actual filename.
- `BIP 3` matches the display text convention the README (line 40) and
every other BIP in this repository already use when linking to
bip-0003 — "BIP 003" with the three-digit zero-pad appears nowhere
else in the repo for any BIP and is not part of the display style
described in BIP 2.
Also drops the trailing whitespace on the bip-0347 line while we are
there (the `typos` CI tolerates it but it is inconsistent with every
other line in the same changelog block).
Exercises [A, -A, A] input key pattern where the intermediate sum
hits zero after the first two keys, but the final sum is non-zero.
Implementations that validate after each pairwise addition (rather
than summing all keys first) will incorrectly reject this case.
Before this commit it was not clear that non-native SegWit outputs
(e.g. P2PKH or P2SH-P2WPKH) only work if the correct scriptSig is
provided.
This then also makes it more clear why P2SH-P2WPKH outputs are NOT
supported by the "simple" variant.
This commit adds a table that clarifies what script types are compatible
with what signing variant and also makes more clear what the exact
format for the signatures of the different variants are.
Test vectors with labels now use big-endian byte order instead of little-endian, matching BIP-352 specification
Summary of test vector changes:
- psbt structure: missing PSBT_OUT_SP_V0_INFO field when PSBT_OUT_SP_V0_LABEL set
- can finalize: one P2WPKH input / two mixed outputs - labeled sp output and BIP 32 change
- can finalize: two sp outputs - output 0 uses label=3 / output 1 uses label=1
Adds a warning to the "if no matches are found, stop" scanning
step. Without it, wallet developers may be tempted to apply policy
filtering (e.g. dust) before deciding to continue,
causing subsequent outputs for the same sender to be missed.
