|
Ran
|
Files
114
|
Run time
2s
|
Badge
README BADGES
|
push
github
Merge rust-bitcoin/rust-bitcoin#3643: Account for data pushing opcodes in `is_standard_op_return` <a class=hub.com/rust-bitcoin/rust-bitcoin/commit/<a class="double-link" href="https://git"><a class=hub.com/rust-bitcoin/rust-bitcoin/commit/e0442782c8c04bdc48c2743e70f46e41c507e5f4">e0442782c<a href="https://github.com/rust-bitcoin/rust-bitcoin/commit/3a73a480c82b6d35ec6ba94e4d6e2b65697630a2"> fix(script): account for data pushing opcodes in `is_standard_op_return` (Rob N) Pull request description: While I believe the original commit used 80 bytes for the entire script as the limit, Bitcoin Core as of [this commit](https://github.com/bitcoin/bitcoin/blame/<a class="double-link" href="https://github.com/rust-bitcoin/rust-bitcoin/commit/110183746150428e6385880c79f8c5733b1361ba">110183746</a>/src/policy/policy.h#L68-L72) will relay OP_RETURN outputs as long as the data itself is not above 80 bytes, meaning a script of maximum size 83 bytes should be standard. ACKs for top commit: tcharding: ACK e0442782c8c04bdc48c2743e70f46e41c507e5f4 apoelstra: ACK e0442782c8c04bdc48c2743e70f46e41c507e5f4; successfully ran local tests Tree-SHA512: edd6278068ae67b4bddecbc70aad72ec23b
20086 of 24303 relevant lines covered (82.65%)
18007.53 hits per line
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
|---|