Difference between revisions of "False Return"
| Line 1: | Line 1: | ||
| − | False Return outputs are [[VOUT|transaction outpoints]] which begin with the script "OP_FALSE OP_RETURN". This script always returns a false when evaluated making the output unspendable and locking any funds attached to that endpoint. | + | False Return outputs are [[VOUT|transaction outpoints]] which begin with the script "OP_FALSE OP_RETURN". This script always returns a false when evaluated making the output unspendable and locking any funds attached to that endpoint. False Return outputs can be used to store arbitrary information such as recorded data, tokens, files and more. False Return outputs are commonly used as vehicles to carry data for [[Second layer protocol|second layer protocols]] inside Bitcoin transactions. |
==OP_RETURN Transactoins== | ==OP_RETURN Transactoins== | ||
| − | Due to changes made by Satoshi in 2010 to prevent people exploiting a bug in the Bitcoin software, prior to the Quasar update any transaction script that reached an OP_RETURN opcode would fail. Until the Quasar Update in early 2019, all | + | Due to changes made by Satoshi in 2010 to prevent people exploiting a bug in the Bitcoin software, prior to the Quasar update any transaction script that reached an OP_RETURN opcode would fail. Until the Quasar Update in early 2019, all transactions requiring attached data items such as tokens and other information was stored in these unspendable outputs. |
| − | Many | + | Many second layer protocols were build using the OP_RETURN framework prior to being migrated to False Return outputs. |
Revision as of 11:28, 1 January 2020
False Return outputs are transaction outpoints which begin with the script "OP_FALSE OP_RETURN". This script always returns a false when evaluated making the output unspendable and locking any funds attached to that endpoint. False Return outputs can be used to store arbitrary information such as recorded data, tokens, files and more. False Return outputs are commonly used as vehicles to carry data for second layer protocols inside Bitcoin transactions.
OP_RETURN Transactoins
Due to changes made by Satoshi in 2010 to prevent people exploiting a bug in the Bitcoin software, prior to the Quasar update any transaction script that reached an OP_RETURN opcode would fail. Until the Quasar Update in early 2019, all transactions requiring attached data items such as tokens and other information was stored in these unspendable outputs. Many second layer protocols were build using the OP_RETURN framework prior to being migrated to False Return outputs.