feat(transaction)!: allow multiple signers #1053
Merged
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.
Description
Allow multiple signers for a transaction
Motivation and Context
This enables many use cases including paying for another user's fees (gasless) and invoking two or more components owned by different public keys in the same transaction.
It is possible for a party to remove all signatures but one and still have a valid transaction. In future, we'll add a final signature that includes all signatures in the preimage.
How Has This Been Tested?
Manually. TODO: Multiple signer integration test
What process can a PR reviewer use to test or verify this change?
Submit transactions requiring badges from multiple public keys
Breaking Changes
BREAKING CHANGE: wallet database changed, transaction struct changed