Allow the serialization of transaction build parameters. #84
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
2 tasks
batconjurer
reviewed
May 23, 2024
grarco
approved these changes
May 23, 2024
batconjurer
approved these changes
May 23, 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.
Made changes to facilitate the implementation of MASP hardware wallet support with hardware generated randomness. More specifically, the following has been done:
Transactionto be stored in the hardware wallet's format (which uses vectors and discards the random number generator). This was done by creating ato_storedmethod.StoredBuildParamsand its subcomponents. This is done to facilitate test vector creation and the reading of randomness parameters from the hardware wallet.StoredBuildParamsand its subcomponents. This was done to ease the communication of the structure of the randomness parameters.