Allow OP_RETURN with two PUSHDATA #6396

pull haraldh wants to merge 1 commits into bitcoin:master from haraldh:opreturn2 changing 3 files +53 −3

haraldh commented at 5:03 AM on July 8, 2015: none

Having two PUSHDATA allows the use of a marker for SPV bloom filtering.

This avoids having two transactions, where the first one triggers the bloom filter.
jgarzik commented at 5:05 AM on July 8, 2015: contributor

See #5075 and #5079

Allow OP_RETURN with two PUSHDATA

Having two PUSHDATA allows the use of a marker for SPV bloom filtering.

This avoids having two transactions, where the first one triggers the
bloom filter.

caa3ca36df

haraldh commented at 5:42 AM on July 8, 2015: none

Sure #5079 is more flexible.
paveljanik commented at 6:56 AM on July 15, 2015: contributor

So can we close this PR because of it?
luke-jr commented at 7:07 AM on July 15, 2015: member

@petertodd told me he doesn't plan to fix #5079 (it fails unit tests at least)
petertodd commented at 3:28 PM on July 17, 2015: contributor

@luke-jr See #6424, which hopefully I can convince @jtimon to finish for me. :)
laanwj added the label TX fees and policy on Jul 17, 2015
laanwj commented at 8:43 AM on July 21, 2015: member

#5079 indeed looks liks it is more general. Why two? not three, four, as long as the total scriptPubKey size isn't exceeded
laanwj closed this on Jul 21, 2015
gtklocker referenced this in commit d267eea052 on Sep 24, 2018
DrahtBot locked this on Sep 8, 2021

Contributors

Labels