This repository was archived by the owner on Jul 20, 2021. It is now read-only.
Blockcreate tx #514
Draft
Blockcreate tx #514
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
robvanmieghem
force-pushed
the
master
branch
from
9533ecf to
1ff618c
Compare
robvanmieghem
force-pushed
the
master
branch
2 times, most recently
from
58ae02f to
9e641e8
Compare
robvanmieghem
force-pushed
the
master
branch
2 times, most recently
from
f4a600f to
e8e17e0
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a new transaction version 0x02, known as a block create transaction. This transaction has no input or outputs, and fulfills a blockstake output in its extension. The POBS algorithm recognizes this as an alternative for "old" block creation transactions which explicitly respend the blockstakes. Additionally, the extension data also includes a height, this is the height of the block which will have been created by this transaction. If this height does not match, the transaction is invalid. This field is thus unique, and ensures a unique tx ID in case the same blockstake output gets unlocked multiple times