magicblock-labs / magicblock-labs/magicblock-validator
Sync the validator feature set with the base chain at startup
@bmuddha is already working on this.
Since Sep 4, 2026.
- Dominant language
- Rust
- Stars
- 58
- Forks
- 58
- Avg merge
- 22h 1m
- Merged PRs (30d)
- 53
Description
## Problem
magicblock-processor::build_svm_env currently starts from FeatureSet::default() and activates a hard-coded subset of features. The validator can therefore drift from the configured Solana cluster as features activate. sBPF v3 support, for example, had to be enabled manually in #1338.
#350 tracked the same compatibility goal but was closed because synchronizing before runtime creation was not trivial. Since #1631 established a startup sync pattern for base-chain execution parameters, revisit this as startup-frozen feature synchronization.
## Goal
Before creating the SVM runtime, load the configured Solana cluster feature state and initialize the validator with the matching set of supported, execution-relevant features.
## Acceptance criteria
- Primary startup fetches the supported feature accounts from the configured base-layer RPC before building the SVM runtime environment.
- Restart time is still fast, ideally all RPCs call are cluster in a single getMultipleAccounts
Dynamic feature activation while the process is running is out of scope; changes are picked up on the next validator start.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.