Support transaction batch signatures #179
Draft
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 signature scheme for batch signatures.
There will be a KIP for this soon, and we will link to it from this PR.
Batch signatures are a type of signature that can be assigned to multiple transactions at once. One part of the signature (the root) is shared across all transactions. Another part (the proof) is specific to each transaction in the batch.
Batch signatures are implemented with Merkle trees. The root of the signature is a Merkle root of all the transactions in the batch, hashed with Blake2b_256. Each transactions proof is a Merkle proof of that transaction's inclusion in the batch.
PR checklist:
Additionally, please justify why you should or should not do the following: