diff options
author | Suhas Daftuar <sdaftuar@gmail.com> | 2020-07-29 11:07:23 -0400 |
---|---|---|
committer | Suhas Daftuar <sdaftuar@gmail.com> | 2020-08-04 13:29:40 -0400 |
commit | 7989901c7eb62ca28b3d1e5d5831041a7267e495 (patch) | |
tree | 776c823c913377bcd1ddd3093f5952f35f400199 /test | |
parent | a41ae68053387567414021228995a485e29ad611 (diff) | |
download | bitcoin-7989901c7eb62ca28b3d1e5d5831041a7267e495.tar.xz |
Add txids with non-standard inputs to reject filter
Our policy checks for non-standard inputs depend only on the non-witness
portion of a transaction: we look up the scriptPubKey of the input being
spent from our UTXO set (which is covered by the input txid), and the p2sh
checks only rely on the scriptSig portion of the input.
Consequently it's safe to add txids of transactions that fail these checks to
the reject filter, as the witness is irrelevant to the failure. This is helpful
for any situation where we might request the transaction again via txid (either
from txid-relay peers, or if we might fetch the transaction via txid due to
parent-fetching of orphans).
Further, in preparation for future witness versions being deployed on the
network, ensure that WITNESS_UNKNOWN transactions are rejected in
AreInputsStandard(), so that transactions spending v1 (or greater) witness
outputs will fall into this category of having their txid added to the reject
filter.
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions