update multisig signing recipe with unsigned tx creation #666
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
adds a first step to the multisig signing recipe that describes what an unsigned transaction is and how it is generated provides an example of how to create an usigned transaction using the createTransaction RPC and buildTransacton RPC
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
hughy
force-pushed
the
chore/hughy/multisig-recipe-unsigned
branch
from
37843ac
to
3bcb9e5
Compare
NullSoldier
approved these changes
Apr 11, 2024
andiflabs
approved these changes
Apr 11, 2024
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.
What changed?
adds a first step to the multisig signing recipe that describes what an unsigned transaction is and how it is generated
provides an example of how to create an usigned transaction using the createTransaction RPC and buildTransacton RPC
Reminder: If content (docs, blogs, pages) is moved or renamed, please ensure there are no broken links.