Skip to main content
mip.watch
⌘K

MIP-9

Active Set Increase

Withdrawn Standards Track Core GitHub ↗ Forum ↗
Idea Draft Review Last Call Final Living Withdrawn

Increase the `ACTIVE_VALSET_SIZE` from 200 to 300.

Authors
Jackson Lewis (@jacksononchain)
Created
2026-03-19
Updated
Oct 22, 2026

Stakeholder Impact

What this MIP changes for each audience. Severity and action flags are model-derived with deterministic floors per MIP type/category.

TL;DR

This proposal aims to increase the maximum number of active validators from 200 to 300 to enhance participation and decentralization without causing significant changes to the system's performance.

What's Changing

  • Active Validator Set Size: Increasing from 200 to 300 to allow more validators to participate.
  • Consensus Layer Impact: More validators will be involved in consensus rounds, potentially improving decentralization.
  • No Changes to Selection Mechanism: The method for selecting which validators are active remains the same, ensuring stability.
  • No Backwards Compatibility Issues: Existing validators are not affected by this change, making it a smooth transition.
  • Increased Message Complexity: More validators will lead to more messages during consensus, but this is manageable.
⌘

Developers

Smart contract & dapp builders, RPC consumers, tooling authors

This change increases the maximum active validator set size, which may require on-chain contracts that read validator set membership to be reviewed for compatibility. However, there are no ABI changes or new opcodes, and existing contracts do not need to be recompiled or redeployed.

Low
◉

Users

Wallet users, EOA holders, dapp visitors

There will be no direct changes to transaction fees, confirmation speeds, or asset safety for users. No action is required from users regarding their wallets or funds.

Low
◆

Validators

Node operators, RPC operators, delegators

Increasing the active validator set size from 200 to 300 allows for more validators to participate, which could enhance decentralization and security. However, as this MIP is withdrawn, there is no immediate operational or economic impact on validator revenue or requirements.

Low
✦

Foundation

Monad Foundation & Category Labs core devs

The withdrawal of MIP-9 means that there is no longer a need for governance coordination or hardfork activation related to the increase of the active validator set size. This decision simplifies the communication and documentation burden associated with the proposal.

Low

Generated Nov 7, 2026, 5:30 AM · model: gpt-4o-mini

Specification

Cite
Subsystems executionconsensusstakingeconomics

## Abstract

This MIP proposes an increase to the maximum active validator set from 200 to 300.

The current active validator set is capped at 200. Raising the cap expands participation without introducing abrupt load changes to the consensus layer (MonadBFT) or execution pipeline.

## Specification

### Parameters

| Parameter | Current Value | Proposed Value |
|---|---|---|
| `ACTIVE_VALSET_SIZE` | 200 | 300 |

`ACTIVE_VALSET_SIZE` SHOULD be increased from 200 to 300.

### Consensus and Execution Layer Impact

This MIP affects the consensus layer (MonadBFT). The active validator set size directly governs the number of participants in each consensus round. The execution daemon is unaffected unless validator set membership is read by on-chain contracts, in which case any such contracts SHOULD be reviewed for compatibility.

The consensus daemon enforces `ACTIVE_VALSET_SIZE` as an upper bound on the number of validators eligible to participate in block proposal and voting at any given epoch. The selection mechanism for which validators fill the active set (e.g., by stake) is unchanged by this MIP.

## Rationale

An increment of 100 represents a meaningful expansion (~50%) without dramatically altering the message complexity in MonadBFT's voting rounds. Larger single-step increases carry higher risk of unforeseen performance degradation; smaller increments would add process overhead without proportionate benefit.

The increase allows for greater decentralization in the active set, enforcing stronger fault tolerance and economic security.

## Backwards Compatibility

This MIP does not introduce backwards incompatibilities. The change is additive: existing validators in the active set are unaffected. The hard-coded `ACTIVE_VALSET_SIZE = 200` must be updated to `300` to support the new parameter values prior to activation.

## Security Considerations

**Consensus scalability**: Increasing the active validator set increases the number of messages exchanged per consensus round in MonadBFT.

**Sybil risk**: Expanding the set without changes to the stake-based selection mechanism does not meaningfully increase Sybil risk. No additional mitigations are required.

## Copyright

Copyright and related rights waived via [CC0](../LICENSE.md).

Forum discussion

11 posts · 45 likes · 4 months ago
Read more on forum ↗
  1. @Socialforging #1 Mar 30, 2026, 12:12 PM

    mip 9 title Active Set Increase description Increase the `ACTIVE_VALSET_SIZE` from 200 to 300. author Jackson Lewis ( @jacksononchain ) status Withdrawn type Standards Track category Core created 2026-03-19 Abstract This MIP proposes an increase to the maximum active validator set from 200 to 300. The current active validator set is capped at 200. Raising the cap expands participation without introducing abrupt load changes to the consensus layer (MonadBFT) or execution pipeline. Specification Parameters Parameter Current Value Proposed Value ACTIVE_VALSET_SIZE 200 300 ACTIVE_VALSET_SIZE SHOULD be increased from 200 to 300. Consensus and Execution Layer Impact This MIP affects the consensus layer (MonadBFT). The active validator set size directly governs the number of participants in each consensus round. The execution daemon is unaffected unl...

  2. @Socialforging #2 Apr 15, 2026, 7:35 AM

    Please note the details have been adjusted, and the proposed change is to increase active set to 300.

  3. @Kutsal #3 Apr 15, 2026, 11:33 AM

    “As ‘Devnads’ and a potential validator, I support any developments that will help foster the Monad ecosystem.” Thank you for the information @jacksononchain

  4. @cassini #4 Apr 16, 2026, 7:03 PM

    In support of MIP-9, with a suggestion to use testnet more aggressively This MIP is well-scoped. The 50% increment is a reasonable step and the rationale is sound. One observation worth noting: the primary cost of increasing ACTIVE_VALSET_SIZE in MonadBFT is not bandwidth — it is signature aggregation latency at the leader. MonadBFT operates on O(n) message complexity in the happy path; each validator sends a signed vote directly to the next leader, who must aggregate those into a QC before proceeding. At 300 validators and 400ms block times, this is unlikely to be the bottleneck under nominal load. Under sustained peak throughput, however, the relationship between n and round latency has not been empirically characterized at this scale on a live network. A proposal for the testnet phase: rather than validating 300, CONSIDER targeting 500 as the testnet ceiling. Additionally, it wo...

  5. @STAKEME #5 Apr 17, 2026, 3:35 PM

    We agree with the updated proposal and are glad to see the active set increase to 300. We believe this is a positive step for the network, as it strengthens decentralization and broadens validator participation while still keeping the change measured and reasonable from a performance standpoint. We’re happy to support this decision and believe it will benefit the long-term health of the network.