summaryrefslogtreecommitdiff
path: root/bip-0158.mediawiki
diff options
context:
space:
mode:
authorOlaoluwa Osuntokun <laolu32@gmail.com>2019-02-12 19:57:51 -0800
committerOlaoluwa Osuntokun <laolu32@gmail.com>2019-02-12 19:57:51 -0800
commit1330853c3e9e248d4003cd08ac192076b42c4521 (patch)
tree6018d3b7db2097b5c910527edd8f93a8516f110a /bip-0158.mediawiki
parentdd3948b4742eaad13872a85691347dc77cce09f0 (diff)
downloadbips-1330853c3e9e248d4003cd08ac192076b42c4521.tar.xz
BIP-0158: clarify OP_RETURN handling for filters
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.
Diffstat (limited to 'bip-0158.mediawiki')
-rw-r--r--bip-0158.mediawiki8
1 files changed, 4 insertions, 4 deletions
diff --git a/bip-0158.mediawiki b/bip-0158.mediawiki
index 535ffd9..a745995 100644
--- a/bip-0158.mediawiki
+++ b/bip-0158.mediawiki
@@ -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.
-We exclude all <code>OP_RETURN</code> outputs in order to allow filters to
-easily be committed to in the future via a soft-fork. A likely area for future
-commitments is an additional <code>OP_RETURN</code> output in the coinbase
-transaction similar to the current witness commitment
+We exclude all outputs taht start with <code>OP_RETURN</code> in order to allow
+filters to easily be committed to in the future via a soft-fork. A likely area
+for future commitments is an additional <code>OP_RETURN</code> output in the
+coinbase transaction similar to the current witness commitment
<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
between the commitment, and the item being committed to.