Validator DAO Restructuring: Everything You Need to Know

Validator Dao Committee

The Umee Validator DAO is governed by the Umee Validator DAO Committee, responsible for making delegation decisions on a quarterly basis.

In addition to the quarterly delegation decisions, the committee may also present and assign ad hoc task requests for validators. Selected validators will be granted additional delegation by the committee.

The committee is composed of 5 members, selected through a community voting process on the CommonWealth thread. Provided there are no issues, the same committee may serve multiple quarters.

The restructured Validator Dao Committee will have 5 members.

The committee’s responsibility involves two things:

1. Evaluate validator node performance (timely upgrade, all modules running correctly, no downtime, no slashing, high governance participation)
2. Review Validator Requests (VR) and assign Requests to validators

Validator Delegation Rules

Validator delegation is made based on node performance and validator contributions based on requests.

Delegation made based on NODE PERFORMANCE follows three tiers:

• Tier I: meet 95% of the performance requirements (see below for details)
• Tier II: meet 80% of the performance requirements; receive 70% of Tier I delegation
• Tier III: new validators; can receive eg 35% of Tier I delegation

Delegation made based on VALIDATOR REQUESTS follows the below guideline:

• The Validator Committee proposes new validator requests on an as-needed basis
• Validator Requests can be allocated retrospectively if a contribution is considered valuable and is outside of the announced Validator Requests 

Node Performance Guideline

The node performance is evaluated based on the below categories:

• 0 jail if 80% of validators have not incurred a jail event; in extreme circumstances, 1 jail if 80% of validators have incurred a jail event
• Healthy Peggo and Price Feeder
• Finish all network upgrades on time as needed
• Frequent voting
• Submit delegation application

Validator Requests

The initial scope for validator requests are the following:

Perpetual requests include:

•  Archival RPC nodes for mainnet: 2. 
• Pruned RPC nodes for mainnet: 2.
•  Archival RPC nodes for Canon2: 2.
•  Pruned RPC nodes for Canon2: 1.
•  Snapshot service: 2.
•  Testnet explorer: 1.
•  Relayers: Target networks and # of relayers:

3 each for the below networks:

Cosmos Hub; Axelar; Osmosis; Stride;

2 each for all the rest of the networks that have their native tokens listed on Umee

• Peggo health checker/bot: 2.

• Price feeder health checker/bot: 2.

• IBC checker/bot: 2.

Validator monitoring and evaluation tool: 2 

Ad hoc requests based on needs.

Note: perpetual requests will not be modified often; validators assigned with perpetual requests are not expected to be changed often.