-
2013, OP_RETURN made standard:
- RFC: empty scriptPubKeys and OP_RETURN for marking unspendable txouts by petertodd
- PR 2738 by jgarzik
- v0.9.0 release notes
2014, OP_RETURN default increased to 80 bytes:
2016, OP_RETURN used for Segwit (witness root hash in coinbase tx):
2023, Remove OP_RETURN restrictions:
- PR 28130 by petertodd, requested by christopherA
- email thread
- petertodd's libre relay requested by lightcoin
2025, Remove OP_RETURN restrictions:
- Dev mailing list thread started by darosior
- PR 32359 by petertodd, requested by darosior
- PR 32381 by darosior
- PR 32406 by instagibbs
- Explanation by instagibbs
- Wuille's public-relations message
- Wuille's public-relations bitcoincore PR
- Wuille's public-relations statement on bitcoincore.org
Some of the earliest bitcointalk mentions of op_return:
- Sep 2010: "I added some information on the "OP_RETURN" bug that triggered the 0.3.5 release" - gavin
- Jan 2012: "ArtForz discovered a bug in July of 2010 (the OP_RETURN bug) that allowed anybody to spend anybody else's bitcoins. It by far Bitcoin's biggest bug and Satoshi's biggest brain-fart." - gavin
- Mar 2013: "I'd encourage you to start a discussion about making OP_RETURN, possibly followed by a small amount of data" - petertodd
- Sep 2013: "Here I assume zero value OP_RETURN outputs are standard" - jl2012
- Dec 2013: "I have an idea that uses OP_RETURN" - locksley
Edited by node runner
Please register or sign in to comment