Skip to content

fix: load legacy deployed programs - #99

Draft
bmuddha wants to merge 1 commit into
devfrom
fix/loader-v1-program-loading
Draft

fix: load legacy deployed programs#99
bmuddha wants to merge 1 commit into
devfrom
fix/loader-v1-program-loading

Conversation

@bmuddha

@bmuddha bmuddha commented Aug 27, 2026

Copy link
Copy Markdown
Collaborator

What changed

  • Build the processor's shared runtime as an execution environment so already-deployed legacy ELFs use Solana's lenient loading policy.
  • Preserve strict verification for new deployments through the separately derived deployment environment.

Closes #91

Impact

LoaderV1 programs cloned from the base chain, including Memo v1, can load and execute. Modern programs, public APIs, and persisted data are unchanged.

Reviewer notes

The changed flag only controls execution-time ELF loading. deploy_program continues to force reject_broken_elfs = true before verifying newly deployed programs.

@bmuddha bmuddha added the bug Something isn't working label Aug 27, 2026
@bmuddha bmuddha self-assigned this Aug 27, 2026
@coderabbitai

coderabbitai Bot commented Aug 27, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 7bb65ba6-73a7-425a-929b-95669315158c


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

LoaderV1 programs fail to load on the engine validator (clone succeeds, program load fails)

1 participant