Support legacy BPF loaders (v1/v2) in get-program-hash#230
Open
meumar-osec wants to merge 1 commit intoEllipsis-Labs:masterfrom
Open
Support legacy BPF loaders (v1/v2) in get-program-hash#230meumar-osec wants to merge 1 commit intoEllipsis-Labs:masterfrom
meumar-osec wants to merge 1 commit intoEllipsis-Labs:masterfrom
Conversation
meumar-osec
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #216
Programs deployed with BPF loader v1/v2 (e.g, SPL Token
TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA) store executable in the program account's data. Whereas an upgradeable loader (loader-v3) stores the executable in a separate program data account.Previously,
get-program-hashonly supported the upgradeable loader (loader-v3) and would fail when called on programs deployed with legacy loaders (v1/v2). Now handling both cases: