Input and proof #19
Open
Input and proof #19
Conversation
This file contains 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
DanielKrawisz
force-pushed
the
input_and_proof
branch
from
84061b8 to
0e87d2b
Compare
|
Is it fair to say @DanielKrawisz that this branch is too far out of date to merge, and the PR should be closed? |
|
@katrinaas can this be updated to be mergeable, have these features already been merged, or shall it be closed? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 types Input and Proof. Input represents a complete boost input in a transaction. Redeem represents the boost script and has parameters for txid, vin, spentVout, and spentTxid that are optional. In Input, these parameters are not optional. Proof is an Input and an Output together, and represents a complete Boost purchase with proof of work that can be read.