-
Notifications
You must be signed in to change notification settings - Fork 121
fix: fromVersionedTransaction bug #906
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: fromVersionedTransaction bug #906
Conversation
🦋 Changeset detectedLatest commit: b84a18b The changes in this PR will be included in the next version bump. This PR includes changesets to release 41 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
steveluscher
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BundleMonUnchanged files (130)
Total files change -6B 0% Final result: ✅ View report in BundleMon website ➡️ |
|
Automerge label removed due to a CI failure |
|
Because there has been no activity on this PR for 14 days since it was merged, it has been automatically locked. Please open a new issue if it requires a follow up. |

Problem
fromVersionedTransactioncurrently fails forVersionedTransactionthat use address lookup tables.The reason for this is
fromVersionedTransactiontries to resolve all the accounts for the inputVersionedTransaction, but doesn't have access to the lookup tables involved in the transaction. However if we look further in the function we notice we are only interested in the static accounts, which is where the signers are.Summary of Changes
Use
message.staticAccountKeysinstead ofmessage.getAccountKeys()which tries to resolve all the accounts.