Add serialized transaction field and return in API #1692
Merged
Conversation
This file contains hidden or 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
This adds a new field to Transaction called serialized which will contain the full base64 encoded transaction of the Ironfish SDK Transaction type. It also returns it in transactions/find API.
NullSoldier
changed the title
patnir
approved these changes
Dec 26, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
This adds a new field to Transaction called serialized which will contain the full base64 encoded transaction of the Ironfish SDK Transaction type. It also returns it in transactions/find API.
This is the followup PR. #1693
Testing Plan
Added test
Breaking Change
No
Transactions will be sent back with null serialized in the case that it was not sent.