magicblock-labs / magicblock-labs/magicblock-validator

Establish Validator v1 as the production baseline

Open
#1,694 0 comments 0 reactions 1 assignee View on GitHub

@GabrielePicco is already working on this.

Since Sep 17, 2026.

Dominant language
Rust
Stars
58
Forks
58
Avg merge
22h 1m
Merged PRs (30d)
53

Description

## Goal

Release the current validator as a dependable baseline that the team can keep operating if the next major version takes longer to roll out.

## Why

The current validator has known limits under load, occasional stalls, and rare account-lifecycle failures. V1 is not intended to solve all of them. It provides a clearly understood, supportable starting point while the larger architecture change is completed.

## Scope

- Land and verify the pending account-handling fix that blocks release.
- Release the current mainline validator without adding new product features.
- Document known operating limits and conditions that require intervention.
- Confirm upgrade, rollback, restart, and recovery procedures.
- Validate that delegation and undelegation complete safely for release-critical paths.
- Record baseline reliability and performance measurements for comparison with V2.
- Consider the epic complete when the release is published, the operating procedures are exercised, and known limitations are documented.
- Keep new features, V2 architectural work, and RedSuite qualification outside the V1 release gate.
- Roadmap target: late September 2026.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.