Coin Brief ENDE

BIP 375 now rejects segwit v2+ inputs given in the non-witness field for silent payments

The BIPs repository merged pull request 2310 on 7 November, a change to BIP 375, the draft specification for sending silent payments with partially signed Bitcoin transactions. BIP 375 adds fields and role duties to PSBT version 2 so that a silent payment output, whose script cannot be computed until every input is known, can be carried, computed and verified by the parties signing a transaction.

One of its eligibility rules is that a transaction paying a silent payment output must not spend inputs with a segwit version greater than 1. The reference validator enforced this only when an input's previous output was supplied through the PSBT_IN_WITNESS_UTXO field. An input described instead through PSBT_IN_NON_WITNESS_UTXO, which carries the whole previous transaction, was not checked.

The commit, written by the contributor zjubiology and dated 26 September, rewrites the check in validate_psbt.py so that the script is tested for a segwit version of 2 or higher whichever field it came from. It also adds a test vector to bip375_test_vectors.json and a matching row to the specification's list of tests: a PSBT that supplies a segwit v2 input through the non-witness field together with a silent payment output, which a correct implementation must reject. In total the commit adds 23 lines and removes 7 across three files.

BIP 375 now rejects segwit v2+ inputs given in the non-witness field for silent payments
BIP 375 now rejects segwit v2+ inputs given in the non-witness field for silent payments — Coin Brief

What it means

Wallets and signers implementing BIP 375 should run the new vector. A validator that inspects only one of the two ways a PSBT can describe an input lets the same forbidden spend through the other, which is exactly the kind of gap test vectors exist to close.