feature: Added calltable serialization for TransactionV1, Changing TransactionV1 structure #461
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
…ansactionV1 structure
…ransactionScheduling, TransactionTarget, CalltableSerialization to convert fromBytes to instances, Updated Reservation for BidKind, Added Prepaid for StoredValue, added fromBytesWithType for CLValueParser
…nsactionV1Payload, removed TransactionCategory from Transaction
Comp0te
approved these changes
Nov 29, 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.
Changing
TransactionV1structure. From now on aTransactionV1consists ofhash,payloadandapprovals.payloadis a merge ofheaderandbodyconcepts from before.bodyis not represented in a type-constrained way, instead, we use an amorphic field of typeMap<number, Uint8Array>which is more resistant to future changes.Added calltable serialization for TransactionV1 - Reference of changes