OP RETURN - Revision history

Furunodo at 12:54, 27 June 2020

2020-06-27T12:54:00Z

← Older revision		Revision as of 12:54, 27 June 2020
Line 2:		Line 2:

	== Is storing data in the blockchain acceptable? ==		== Is storing data in the blockchain acceptable? ==
	Many members of the Bitcoin community believe that use of OP_RETURN is irresponsible in part because Bitcoin was intended to provide a record for financial transactions, not a record for arbitrary data. Additionally, it is trivially obvious that the demand for external, massively-replicated data store is essentially infinite. Despite this, OP_RETURN has the advantage of not creating bogus UTXO entries, compared to some other ways of storing data in the blockchain.		Many members of the Bitcoin community believe that use of OP_RETURN is irresponsible in part because Bitcoin was intended to provide a record for financial transactions, not a record for arbitrary data. Additionally, it is trivially obvious that the demand for external, massively-replicated data store is essentially infinite. Despite this, OP_RETURN has the advantage of not creating bogus [[UTXO]] entries, compared to some other ways of storing data in the blockchain.

	From [https://bitcoin.org/en/release/v0.9.0#opreturn-and-data-in-the-block-chain Bitcoin Core release 0.9.0]:		From [https://bitcoin.org/en/release/v0.9.0#opreturn-and-data-in-the-block-chain Bitcoin Core release 0.9.0]:

Belcher: /* OP_RETURN applications */ Fix link to ECDH address page

2020-03-24T16:30:54Z

OP_RETURN applications: Fix link to ECDH address page

← Older revision		Revision as of 16:30, 24 March 2020
Line 12:		Line 12:

	== OP_RETURN applications ==		== OP_RETURN applications ==
	OP_RETURN can be used for digital asset proof-of-ownership, and has at times been used to convey additional information needed to send transactions (see [[~~stealth~~ address]]).		OP_RETURN can be used for digital asset proof-of-ownership, and has at times been used to convey additional information needed to send transactions (see [[ECDH address]]).


	{{DISPLAYTITLE:OP_RETURN}}		{{DISPLAYTITLE:OP_RETURN}}

Dionyziz: The recommendation for BIPs is outdated. No such BIPs exist and the practice has been discouraged on the mailing list.

2018-09-20T15:30:23Z

The recommendation for BIPs is outdated. No such BIPs exist and the practice has been discouraged on the mailing list.

← Older revision		Revision as of 15:30, 20 September 2018
Line 14:		Line 14:
	OP_RETURN can be used for digital asset proof-of-ownership, and has at times been used to convey additional information needed to send transactions (see [[stealth address]]).		OP_RETURN can be used for digital asset proof-of-ownership, and has at times been used to convey additional information needed to send transactions (see [[stealth address]]).

	~~== OP_RETURN prefixes ==~~
	Often, OP_RETURN transactions include a prefix to identify which "protocol" they belong to. Protocols wishing to claim OP_RETURN prefixes should use the standard [[Bitcoin Improvement Proposals]] process. Not all OP_RETURN transactions use prefixes.

	{{DISPLAYTITLE:OP_RETURN}}		{{DISPLAYTITLE:OP_RETURN}}

Luke-jr: Restore edits

2018-08-06T02:00:08Z

Restore edits

@@ Line 1: / Line 1: @@
-'''OP_RETURN''' is a [[script]] opcode used to mark a transaction output as invalid. Since the data after OP_RETURN are irrelevant to Bitcoin payments, arbitrary data can be added into the output after an OP_RETURN. Since any outputs with OP_RETURN are provably unspendable, OP_RETURN outputs can be used to [[Proof of burn|burn]] bitcoins.
+'''OP_RETURN''' is a [[script]] opcode used to mark a transaction output as invalid. Since any outputs with OP_RETURN are provably unspendable, OP_RETURN outputs can be used to [[Proof of burn|burn]] bitcoins.
 == Is storing data in the blockchain acceptable? ==
-Many members of the Bitcoin community believe that use of OP_RETURN is irresponsible in part because Bitcoin was intended to provide a record for financial transactions, not a record for arbitrary data. Additionally, it is trivially obvious that the demand for external, massively-replicated data store is essentially infinite. Despite this, the use of OP_RETURN continues unabated: while there is no global miner consensus to stop people from embedding arbitrary data in the blockchain if they want to, OP_RETURN is somewhat more efficient in terms of [http://i.imgur.com/VAGZWBK.png data bytes stored as a fraction of blockchain space consumed]. Compared to some other ways of storing data in the blockchain, OP_RETURN has the advantage of not creating bogus UTXO entries. [https://github.com/bitcoin/bitcoin/pull/5286 Discussion on GitHub pull request]
+Many members of the Bitcoin community believe that use of OP_RETURN is irresponsible in part because Bitcoin was intended to provide a record for financial transactions, not a record for arbitrary data. Additionally, it is trivially obvious that the demand for external, massively-replicated data store is essentially infinite. Despite this, OP_RETURN has the advantage of not creating bogus UTXO entries, compared to some other ways of storing data in the blockchain.
 From [https://bitcoin.org/en/release/v0.9.0#opreturn-and-data-in-the-block-chain Bitcoin Core release 0.9.0]:
@@ Line 16: / Line 12: @@
 == OP_RETURN applications ==
-OP_RETURN is used for writing human-language messages, digital asset proof-of-ownership, and storing data. Its use has been proposed for P2P application discovery. See the "prefixes" table below.
+OP_RETURN can be used for digital asset proof-of-ownership, and has at times been used to convey additional information needed to send transactions (see [[stealth address]]).
 == OP_RETURN prefixes ==
-Often, OP_RETURN transactions include a prefix to identify which protocol they belong to. There is no standardized method of claiming OP_RETURN prefixes, and not all OP_RETURN transactions use prefixes. At the time of writing, this wiki page is probably the most complete list of OP_RETURN prefixes. Note that this table is an attempt to catalog OP_RETURN prefixes that are already in use, *not* a system for reserving OP_RETURN prefixes! Protocols with no prefix do not use a prefix in OP_RETURN transactions.
+Often, OP_RETURN transactions include a prefix to identify which "protocol" they belong to. Protocols wishing to claim OP_RETURN prefixes should use the standard [[Bitcoin Improvement Proposals]] process. Not all OP_RETURN transactions use prefixes.
 {{DISPLAYTITLE:OP_RETURN}}

Apekato: Undo revision 62559 by Midnightmagic (talk)

2018-07-17T00:15:41Z

Undo revision 62559 by Midnightmagic (talk)

@@ Line 19: / Line 19: @@
 == OP_RETURN prefixes ==
-Often, OP_RETURN transactions include a prefix to identify which "protocol" they belong to. There is no standardized method of claiming OP_RETURN prefixes, and not all OP_RETURN transactions use prefixes. Protocols with no prefix do not use a prefix in OP_RETURN transactions.
+Often, OP_RETURN transactions include a prefix to identify which protocol they belong to. There is no standardized method of claiming OP_RETURN prefixes, and not all OP_RETURN transactions use prefixes. At the time of writing, this wiki page is probably the most complete list of OP_RETURN prefixes. Note that this table is an attempt to catalog OP_RETURN prefixes that are already in use, *not* a system for reserving OP_RETURN prefixes! Protocols with no prefix do not use a prefix in OP_RETURN transactions.
 == External resources on OP_RETURN ==

Apekato: Undo revision 62560 by Luke-jr (talk)

2018-07-17T00:15:22Z

Undo revision 62560 by Luke-jr (talk)

← Older revision		Revision as of 00:15, 17 July 2018
Line 1:		Line 1:
	'''OP_RETURN''' is a [[script]] opcode used to mark a transaction output as invalid. Since any outputs with OP_RETURN are provably unspendable, OP_RETURN outputs can be used to [[Proof of burn\|burn]] bitcoins.		'''OP_RETURN''' is a [[script]] opcode used to mark a transaction output as invalid. Since the data after OP_RETURN are irrelevant to Bitcoin payments, arbitrary data can be added into the output after an OP_RETURN. Since any outputs with OP_RETURN are provably unspendable, OP_RETURN outputs can be used to [[Proof of burn\|burn]] bitcoins.

			Currently, the default Bitcoin client relays OP_RETURN transactions up to 80 bytes [https://github.com/bitcoin/bitcoin/search?utf8=%E2%9C%93&q=MAX_OP_RETURN_RELAY], but does not provide a way for users to create OP_RETURN transactions.

	== Is storing data in the blockchain acceptable? ==		== Is storing data in the blockchain acceptable? ==
	Many members of the Bitcoin community believe that use of OP_RETURN is irresponsible in part because Bitcoin was intended to provide a record for financial transactions, not a record for arbitrary data. Additionally, it is trivially obvious that the demand for external, massively-replicated data store is essentially infinite. Despite this, OP_RETURN has the advantage of not creating bogus UTXO entries~~, compared to some other ways~~ of ~~storing data~~ in the ~~blockchain~~.		Many members of the Bitcoin community believe that use of OP_RETURN is irresponsible in part because Bitcoin was intended to provide a record for financial transactions, not a record for arbitrary data. Additionally, it is trivially obvious that the demand for external, massively-replicated data store is essentially infinite. Despite this, the use of OP_RETURN continues unabated: while there is no global miner consensus to stop people from embedding arbitrary data in the blockchain if they want to, OP_RETURN is somewhat more efficient in terms of [http://i.imgur.com/VAGZWBK.png data bytes stored as a fraction of blockchain space consumed]. Compared to some other ways of storing data in the blockchain, OP_RETURN has the advantage of not creating bogus UTXO entries. [https://github.com/bitcoin/bitcoin/pull/5286 Discussion on GitHub pull request]

			The creation of OP_RETURN outputs also destroys Bitcoins used in the outputs of OP_RETURN transactions, which contributes to future deflationary pressures.

	From [https://bitcoin.org/en/release/v0.9.0#opreturn-and-data-in-the-block-chain Bitcoin Core release 0.9.0]:		From [https://bitcoin.org/en/release/v0.9.0#opreturn-and-data-in-the-block-chain Bitcoin Core release 0.9.0]:
Line 12:		Line 16:

	== OP_RETURN applications ==		== OP_RETURN applications ==
	OP_RETURN ~~can be~~ used for digital asset proof-of-ownership, and has ~~at times~~ been ~~used to convey additional information needed to send transactions (see [[stealth address]])~~.		OP_RETURN is used for writing human-language messages, digital asset proof-of-ownership, and storing data. Its use has been proposed for P2P application discovery. See the "prefixes" table below.

	== OP_RETURN prefixes ==		== OP_RETURN prefixes ==
	Often, OP_RETURN transactions include a prefix to identify which "protocol" they belong to. ~~Protocols wishing to claim~~ OP_RETURN prefixes ~~should~~ use ~~the standard~~ [~~[Bitcoin Improvement Proposals~~]] ~~process~~. ~~Not all OP_RETURN~~ transactions ~~use prefixes.~~		Often, OP_RETURN transactions include a prefix to identify which "protocol" they belong to. There is no standardized method of claiming OP_RETURN prefixes, and not all OP_RETURN transactions use prefixes. Protocols with no prefix do not use a prefix in OP_RETURN transactions.

			== External resources on OP_RETURN ==
			=== Viewing OP_RETURN ===
			* [http://coinsecrets.org/ coinsecrets.org]: An OP_RETURN transaction explorer]
			* [http://bitcoinstrings.com/ bitcoinstrings.com]: A site showing raw strings in Bitcoin transactions

			=== Explaining OP_RETURN ===
			* [https://github.com/coinspark/python-OP_RETURN python-OP_RETURN]
			* [http://bitcoin.stackexchange.com/questions/29554/explanation-of-what-an-op-return-transaction-looks-like StackExchange: Explanation of what an OP_RETURN transaction looks like]
			* [http://www.slideshare.net/coinspark/bitcoin-2-and-opreturns-the-blockchain-as-tcpip Metadata in the Blockchain: The OP_RETURN Explosion]
			* [http://wlangiewicz.com/blog/2014/10/24/how-to-put-custom-messages-into-bitcoin-blockchain-op-return/ How to Put Custom Messages Into Bitcoin Blockchain - OP_RETURN]
	{{DISPLAYTITLE:OP_RETURN}}		{{DISPLAYTITLE:OP_RETURN}}

Luke-jr: Remove garbage encouraging spam

2017-05-07T02:17:43Z

Remove garbage encouraging spam

← Older revision		Revision as of 02:17, 7 May 2017
Line 1:		Line 1:
	'''OP_RETURN''' is a [[script]] opcode used to mark a transaction output as invalid~~. Since the data after OP_RETURN are irrelevant to Bitcoin payments, arbitrary data can be added into the output after an OP_RETURN~~. Since any outputs with OP_RETURN are provably unspendable, OP_RETURN outputs can be used to [[Proof of burn\|burn]] bitcoins.		'''OP_RETURN''' is a [[script]] opcode used to mark a transaction output as invalid. Since any outputs with OP_RETURN are provably unspendable, OP_RETURN outputs can be used to [[Proof of burn\|burn]] bitcoins.

	Currently, the default Bitcoin client relays OP_RETURN transactions up to 80 bytes [https://github.com/bitcoin/bitcoin/search?utf8=%E2%9C%93&q=MAX_OP_RETURN_RELAY], but does not provide a way for users to create OP_RETURN transactions.

	== Is storing data in the blockchain acceptable? ==		== Is storing data in the blockchain acceptable? ==
	Many members of the Bitcoin community believe that use of OP_RETURN is irresponsible in part because Bitcoin was intended to provide a record for financial transactions, not a record for arbitrary data. Additionally, it is trivially obvious that the demand for external, massively-replicated data store is essentially infinite. Despite this, the ~~use~~ of ~~OP_RETURN continues unabated: while there is no global miner consensus to stop people from embedding arbitrary data in the blockchain if they want to~~, ~~OP_RETURN is somewhat more efficient in terms of [http://i.imgur.com/VAGZWBK.png data bytes stored as a fraction of blockchain space consumed]. Compared~~ to some other ways of storing data in the blockchain~~, OP_RETURN has the advantage of not creating bogus UTXO entries. [https://github.com/bitcoin/bitcoin/pull/5286 Discussion on GitHub pull request]~~		Many members of the Bitcoin community believe that use of OP_RETURN is irresponsible in part because Bitcoin was intended to provide a record for financial transactions, not a record for arbitrary data. Additionally, it is trivially obvious that the demand for external, massively-replicated data store is essentially infinite. Despite this, OP_RETURN has the advantage of not creating bogus UTXO entries, compared to some other ways of storing data in the blockchain.

	~~The creation of OP_RETURN outputs also destroys Bitcoins used in the outputs of OP_RETURN transactions, which contributes to future deflationary pressures~~.

	From [https://bitcoin.org/en/release/v0.9.0#opreturn-and-data-in-the-block-chain Bitcoin Core release 0.9.0]:		From [https://bitcoin.org/en/release/v0.9.0#opreturn-and-data-in-the-block-chain Bitcoin Core release 0.9.0]:
Line 16:		Line 12:

	== OP_RETURN applications ==		== OP_RETURN applications ==
	OP_RETURN is used for ~~writing human-language messages,~~ digital asset proof-of-ownership, and ~~storing data. Its use~~ has been ~~proposed for P2P application discovery. See the "prefixes" table below~~.		OP_RETURN can be used for digital asset proof-of-ownership, and has at times been used to convey additional information needed to send transactions (see [[stealth address]]).

	== OP_RETURN prefixes ==		== OP_RETURN prefixes ==
	Often, OP_RETURN transactions include a prefix to identify which "protocol" they belong to. ~~There is no standardized method of claiming~~ OP_RETURN prefixes~~, and not~~ all OP_RETURN transactions use prefixes. ~~Protocols with no prefix do not use a prefix in OP_RETURN transactions.~~		Often, OP_RETURN transactions include a prefix to identify which "protocol" they belong to. Protocols wishing to claim OP_RETURN prefixes should use the standard [[Bitcoin Improvement Proposals]] process. Not all OP_RETURN transactions use prefixes.

	~~== External resources on OP_RETURN ==~~
	~~=== Viewing OP_RETURN ===~~
	* [http://coinsecrets.org/ coinsecrets.org]: An OP_RETURN transaction explorer]
	* [http://bitcoinstrings.com/ bitcoinstrings.com]: A site showing raw strings in Bitcoin transactions

	~~=== Explaining OP_RETURN ===~~
	* [https://github.com/coinspark/python-OP_RETURN python-OP_RETURN]
	* [http://bitcoin.stackexchange.com/questions/29554/explanation-of-what-an-op-return-transaction-looks-like StackExchange: Explanation of what an OP_RETURN transaction looks like]
	* [http://www.slideshare.net/coinspark/bitcoin-2-and-opreturns-the-blockchain-as-tcpip Metadata in the Blockchain: The OP_RETURN Explosion]
	* [http://wlangiewicz.com/blog/2014/10/24/how-to-put-custom-messages-into-bitcoin-blockchain-op-return/ How to Put Custom Messages Into Bitcoin Blockchain - OP_RETURN]
	{{DISPLAYTITLE:OP_RETURN}}		{{DISPLAYTITLE:OP_RETURN}}

Midnightmagic: /* OP_RETURN prefixes */ -- eliminating commercial spam encouraging the use of OP_RETURN

2017-05-07T02:05:38Z

OP_RETURN prefixes: -- eliminating commercial spam encouraging the use of OP_RETURN

@@ Line 19: / Line 19: @@
 == OP_RETURN prefixes ==
-Often, OP_RETURN transactions include a prefix to identify which protocol they belong to. There is no standardized method of claiming OP_RETURN prefixes, and not all OP_RETURN transactions use prefixes. At the time of writing, this wiki page is probably the most complete list of OP_RETURN prefixes. Note that this table is an attempt to catalog OP_RETURN prefixes that are already in use, *not* a system for reserving OP_RETURN prefixes! Protocols with no prefix do not use a prefix in OP_RETURN transactions.
+Often, OP_RETURN transactions include a prefix to identify which "protocol" they belong to. There is no standardized method of claiming OP_RETURN prefixes, and not all OP_RETURN transactions use prefixes. Protocols with no prefix do not use a prefix in OP_RETURN transactions.
 == External resources on OP_RETURN ==

Midnightmagic: /* Is storing data in the blockchain acceptable? */

2017-05-06T23:31:59Z

Is storing data in the blockchain acceptable?

← Older revision		Revision as of 23:31, 6 May 2017
Line 4:		Line 4:

	== Is storing data in the blockchain acceptable? ==		== Is storing data in the blockchain acceptable? ==
	~~Some~~ members of the Bitcoin community believe that use of OP_RETURN ~~violates the contract of Bitcoin,~~ because Bitcoin was intended to provide a record for financial transactions, not a record for arbitrary data. Despite this, use of OP_RETURN ~~may continue~~ unabated ~~because~~ there is no ~~easy way~~ to stop people from embedding arbitrary data in the blockchain if they want to, ~~and~~ OP_RETURN is ~~reasonably~~ efficient in terms of [http://i.imgur.com/VAGZWBK.png data bytes stored as a fraction of blockchain space consumed]. Compared to some other ways of storing data in the blockchain, OP_RETURN has the advantage of not creating bogus UTXO entries. [https://github.com/bitcoin/bitcoin/pull/5286 Discussion on GitHub pull request]		Many members of the Bitcoin community believe that use of OP_RETURN is irresponsible in part because Bitcoin was intended to provide a record for financial transactions, not a record for arbitrary data. Additionally, it is trivially obvious that the demand for external, massively-replicated data store is essentially infinite. Despite this, the use of OP_RETURN continues unabated: while there is no global miner consensus to stop people from embedding arbitrary data in the blockchain if they want to, OP_RETURN is somewhat more efficient in terms of [http://i.imgur.com/VAGZWBK.png data bytes stored as a fraction of blockchain space consumed]. Compared to some other ways of storing data in the blockchain, OP_RETURN has the advantage of not creating bogus UTXO entries. [https://github.com/bitcoin/bitcoin/pull/5286 Discussion on GitHub pull request]

			The creation of OP_RETURN outputs also destroys Bitcoins used in the outputs of OP_RETURN transactions, which contributes to future deflationary pressures.

	From [https://bitcoin.org/en/release/v0.9.0#opreturn-and-data-in-the-block-chain Bitcoin Core release 0.9.0]:		From [https://bitcoin.org/en/release/v0.9.0#opreturn-and-data-in-the-block-chain Bitcoin Core release 0.9.0]:

Midnightmagic: /* OP_RETURN prefixes */

2017-05-06T23:27:11Z

OP_RETURN prefixes

← Older revision		Revision as of 23:27, 6 May 2017
Line 17:		Line 17:

	== OP_RETURN prefixes ==		== OP_RETURN prefixes ==
	Often, OP_RETURN transactions include a prefix to identify which protocol they belong to. There is no standardized method of claiming OP_RETURN prefixes, and not all OP_RETURN transactions use prefixes. At the time of writing, this wiki page is probably the most complete list of OP_RETURN prefixes. Note that this table is an attempt to catalog OP_RETURN prefixes that are already in use, not a system for reserving OP_RETURN prefixes! Protocols with no prefix do not use prefix in OP_RETURN transactions.		Often, OP_RETURN transactions include a prefix to identify which protocol they belong to. There is no standardized method of claiming OP_RETURN prefixes, and not all OP_RETURN transactions use prefixes. At the time of writing, this wiki page is probably the most complete list of OP_RETURN prefixes. Note that this table is an attempt to catalog OP_RETURN prefixes that are already in use, not a system for reserving OP_RETURN prefixes! Protocols with no prefix do not use a prefix in OP_RETURN transactions.

	{\| class="wikitable"		{\| class="wikitable"