From 1330853c3e9e248d4003cd08ac192076b42c4521 Mon Sep 17 00:00:00 2001 From: Olaoluwa Osuntokun Date: Tue, 12 Feb 2019 19:57:51 -0800 Subject: [PATCH] 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. --- bip-0158.mediawiki | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/bip-0158.mediawiki b/bip-0158.mediawiki index 535ffd9a..a745995a 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 OP_RETURN 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 OP_RETURN output in the coinbase -transaction similar to the current witness commitment +We exclude all outputs taht start with OP_RETURN 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 OP_RETURN output in the +coinbase transaction similar to the current witness commitment https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki. By excluding all OP_RETURN outputs we avoid a circular dependency between the commitment, and the item being committed to.