feat: add TransactionMessage
class
#27526
Merged
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.
Problem
Lack of a common interface for creating and displaying transactions which supports both legacy and versioned transactions
Summary of Changes
TransactionMessage
class which can be used to construct or decompile legacy and v0 transactions.Message.compile
method to the legacy message class to mirror the equivalentMessageV0.compile
method added in feat: implement message v0 compilation #27524getAccountKeys
method to bothMessage
andMessageV0
classes for use in transaction decompilation and to allow devs to conveniently resolve account indexes with a common interface for legacy and versioned transactionsresolveAddressTableLookups
method toMessageV0
which is used to decompile v0 transactionsFixes #