VMC Options
Decide where to deploy the Validator Manager Contract and understand the trade-offs
With Avalanche's validator-management upgrades, validator set management is handled by smart contracts called Validator Manager contracts and this contract can be deployed and manage your validator set from any chain in the Avalanche Ecosystem.
This is possible via the P-Chain, which keeps a registry of all of the validators in the Avalanche network. The Validator Manager Contract can be deployed on three different chains:
1. On Your L1 (Default)
This is the simplest option. The VMC is deployed directly on the L1 it manages.
- Pros: Self-contained validator management; no dependency on C-Chain; no AVAX-on-C-Chain requirement for management actions
- Cons: Management is only available when your L1 is running; if the L1 goes down, you can't manage validators through the contract
2. On the C-Chain
The VMC can be deployed on Avalanche's C-Chain while managing validators for a different L1.
- Pros: A failsafe if your L1 is down; C-Chain's high availability and proven stability; better integration with existing DeFi and tooling; easier multi-sig support through existing Safe/Ash wallet infrastructure
- Cons: Relies on C-Chain availability; requires AVAX on C-Chain for management actions; more cross-chain operational dependency
3. On Another L1
You can also deploy the VMC on a completely separate L1.
- Pros: Separation of concerns between management chain and operational chain; can have different security properties for the management chain
- Cons: Most complex setup; cross-chain dependencies
Deployment Architecture
Which Option Should You Choose?
| Factor | On L1 | On C-Chain | On Another L1 |
|---|---|---|---|
| Simplicity | Simple | Moderate | Complex |
| Multi-sig Support | Limited | Excellent | Depends |
| Resilience | Tied to L1 | Independent | Independent |
| Tooling | Growing | Mature | Varies |
Once you deploy your Validator Manager contract, you can upgrade its logic (via proxy patterns), but you cannot move its location from your L1 to C-Chain (or vice versa) without redeploying.
Why This Matters More for PoS
PoA is usually managed by a small set of known operators (often one owner/multisig), so keeping the VMC on the L1 can be clean and contained.
If you plan to move to PoS, you'll generally care more about robustness, permissionless onboarding, and long-term flexibility — which is why deploying the VMC on C-Chain is often the better default.
For This Course
In the permissioned L1 chapters, we'll deploy the VMC on the L1 (PoA context) so you can manage the validator set directly. Later in the multi-sig chapter, you'll see how the C-Chain deployment option enables easier multi-sig governance.
Is this guide helpful?
