bitcoin/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-05-12 12:03:29 +00:00
Code Issues Releases Wiki Activity

BIP-0158: clarify OP_RETURN handling for filters

Browse Source 
In this commit, we clarify how we handle `OP_RETURN` outputs for regular
filters. The prior language was a bit ambiguous, so we hope to make it
as explicit as possible.
This commit is contained in:
Olaoluwa Osuntokun 2019-02-12 19:57:51 -08:00
parent dd3948b474
commit 1330853c3e
No known key found for this signature in database
GPG Key ID: CE58F7F8E20FD9A2
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
bip-0158.mediawiki
View File

@ -281,10 +281,10 @@ following items for each transaction in a block:
Any "nil" items MUST NOT be included into the final set of filter elements. Any "nil" items MUST NOT be included into the final set of filter elements.
We exclude all <code>OP_RETURN</code> outputs in order to allow filters to We exclude all outputs taht start with <code>OP_RETURN</code> in order to allow
easily be committed to in the future via a soft-fork. A likely area for future filters to easily be committed to in the future via a soft-fork. A likely area
commitments is an additional <code>OP_RETURN</code> output in the coinbase for future commitments is an additional <code>OP_RETURN</code> output in the
transaction similar to the current witness commitment coinbase transaction similar to the current witness commitment
<ref>https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki</rev>. By <ref>https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki</rev>. By
excluding all <code>OP_RETURN</code> outputs we avoid a circular dependency excluding all <code>OP_RETURN</code> outputs we avoid a circular dependency
between the commitment, and the item being committed to. between the commitment, and the item being committed to.