Skip to content

Conversation

@steveluscher
Copy link
Contributor

Fixes #3.

buffalojoec

This comment was marked as outdated.

buffalojoec

This comment was marked as resolved.

Copy link
Contributor

@buffalojoec buffalojoec left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me. It's a temporary thing for now, but we likely won't have a real solution to the underlying reason the program ID is different for a while.

For more info, see solana-program/loader-v4#10

TL/DR: The runtime will invoke loader v3 to invoke a BPF program, so if loader v3 itself is a BPF program, it can't also invoke a BPF program in the same way. The runtime needs to split this function out from the BPF Loader builtin, and we'll have to explore doing that before we can use the real program ID to test in here.

@buffalojoec buffalojoec merged commit a7207b4 into main Dec 4, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Program address does not correspond to program address on network

3 participants