[Solana]: Support compiling a transaction with existing external signature #4193
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
satoshiotomakan
requested changes
Jan 3, 2025
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.
Description
A DApp may generate a transaction that requires two signatures: Sign A (generated by the DApp) and Sign B (generated by the user).
Case 1: The DApp requires Signature B from the user first, then combines it with Signature A, and broadcasts the transaction.
Case 2: The DApp fills the transaction with Signature A first, then requires Signature B from the user, and broadcasts the transaction.
Case 1 has been supported in PR #4143.
Case 2 will be supported in this PR.
How to test
Run Rust, C++, iOS, Android tests
Types of changes
No breaking changes
Checklist
If you're adding a new blockchain