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-10-31 10:27:29 +00:00
Code Issues Releases Wiki Activity

Update and rename 3_5_Sending_a_Raw_Transaction_with_an_OP_RETURN.md to 4_3_Sending_a_Raw_Transaction_with_an_OP_RETURN.md

Browse Source
This commit is contained in:
Shannon Appelcline 2017-03-23 14:05:25 -07:00 committed by GitHub
parent cbb2d8e68f
commit 379a3314a4
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
3_5_Sending_a_Raw_Transaction_with_an_OP_RETURN.md → 4_3_Sending_a_Raw_Transaction_with_an_OP_RETURN.md
View File

@ -1,5 +1,7 @@
# 3.5: Sending a Raw Transaction with an OP_RETURN # 3.5: Sending a Raw Transaction with an OP_RETURN
[[maybe put this in a complex transaction section with RBF and child-funds-parent]]
> **NOTE:** This is a draft in progress, so that I can get some feedback from early reviewers. It is not yet ready for learning. > **NOTE:** This is a draft in progress, so that I can get some feedback from early reviewers. It is not yet ready for learning.
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. 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.