flywithu/Learning-Bitcoin-from-the-Command-Line
1
1
Fork 0
mirror of https://github.com/ChristopherA/Learning-Bitcoin-from-the-Command-Line.git synced 2025-06-07 16:06:26 +00:00
Code Issues Releases Wiki Activity

Changed name of file from _to_ to _with_

Browse Source
This commit is contained in:
FIRSTNAME LASTNAME 2017-03-06 22:38:40 -08:00
parent e673c0f39c
commit ad08a8fb08
No known key found for this signature in database
GPG Key ID: F8D36C91357405ED
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
3_5_Sending_a_Raw_Transaction_to_an_OP_RETURN.md → 3_5_Sending_a_Raw_Transaction_with_an_OP_RETURN.md
View File

@ -1,8 +1,8 @@
# 3.5: Sending a Raw Transaction to an OP_RETURN
# 3.5: Sending a Raw Transaction with an OP_RETURN
> **NOTE:** This is a draft in progress, so that I can get some feedback from early reviewers. It is not yet ready for learning.
P2PKHs are the simplest sort of Bitcoin recipient ... except perhaps the OP_RETURN. That's because an OP_RETURN is basically a null: an invalid output. Why would you use one? To store data on the blockchain: up to 80 bytes.
A P2PKH transaction is one of the simplest forms of Bitcoin transaction... except perhaps the OP_RETURN. That's because an OP_RETURN is basically a null: an invalid output. Why would you use one? To store data on the blockchain: up to 80 bytes.
This opens up whole new possibilities for the blockchain, because you can embed data that proves that certain things happened at certain times. Though there is some controversy over using the Bitcoin blockchain in this way, various organizations have used OP_RETURNs for proof of existence, for copyright, to color coins, and [for other purposes](https://en.bitcoin.it/wiki/OP_RETURN). Though 80 bytes might not seem a lot, it can be quite effective if OP_RETURNs are used to store hashes of the actual data.
@ -107,7 +107,7 @@ You may note a warning about the data being in an "unknown protocol". If you wer
[Coinsecrets](http://coinsecrets.org/) offers another interesting way to look at OP_RETURN data. It does its best to keep abreast of protocols, so that it can tell you who is doing what in the blockchain. Here's thisour transaction there: [https://www.blocktrail.com/tBTC/tx/ed445dc970bb40b17c207109e19a37b2be301acb474ccd30680c431cb681bce2](https://www.blocktrail.com/tBTC/tx/ed445dc970bb40b17c207109e19a37b2be301acb474ccd30680c431cb681bce2)
## Summary: Sending a Raw Transaction to an OP_RETURN
## Summary: Sending a Raw Transaction with an OP_RETURN
You can use an OP_RETURN output to store up to 80 bytes of data on the blockchain. You do this with the 'data' codeword for a 'vout'. You still have to send money along too, but you just send it back to a change address, minus a transaction fee.

2
README.md
View File

@ -29,4 +29,4 @@ This tutorial assumes that you have some minimal background of how to use the co
* [3.4: Sending a Raw Transaction to a P2PKH](3_4_Sending_a_Raw_Transaction_to_a_P2PKH.md)
* [Interlude: Using JQ for Better Parsing](3_4__Interlude_Using_JQ_for_Better_Parsing.md)
* [Interlude: Writing a Raw Transaction the Easy Way](3_4__Interlude_Writing_a_Raw_Transaction_The_Easy_Way.md)
* [3.5: Sending a Raw Transaction to an OP_RETURN](3_5_Sending_a_Raw_Transaction_to_an_OP_RETURN.md)
* [3.5: Sending a Raw Transaction with an OP_RETURN](3_5_Sending_a_Raw_Transaction_with_an_OP_RETURN.md)