Solutions · Validators
Run a Validator: Consensus, VEID & Rewards
VirtEngine validators do more than order blocks. The same bonded set that secures CometBFT consensus also operates the VEID Network — decrypting encrypted identity scopes, scoring them with shared ML models, and committing trust scores by consensus. Two duties, one stake, layered rewards.
Who this is for: Professional node operators and infrastructure teams considering the validator role.
At a glance
The short version for validators
-
Mandate
Consensus plus the VEID Network
The same bonded set that orders blocks also decrypts identity scopes, scores them with shared ML models, and commits trust scores by consensus.
-
Moat
Patented identity consensus
The validator identity-scoring method is covered by granted Australian patent AU2024203136B2, in force until 12 May 2044.
-
Voice
Governance is operational duty
Validators vote on parameters, upgrades, and the approved-client list controlling which interfaces may submit identity data.
The problem
The context: consensus alone is commoditized
Generic proof-of-stake validation is a race to the bottom on commission. Differentiated networks give validators real work with real reward streams attached — and demand real operational competence in exchange.
In one view
Audience-specific visual
Each solution gets its own explanatory figure — not the same template art.
VALIDATOR
/ \
CONSENSUS VEID
blocks verification bond → duties → rewards → slashing
The mechanism
How the protocol carries it
How VirtEngine addresses it
Grounded in what the protocol actually does
Duty one: consensus
Propose and validate blocks under CometBFT, with bonded stake weighting voting power. Uptime and correctness earn block rewards; double-signing and extended downtime are slashable.
Duty two: the identity network
Validators hold encryption keys that identity scopes are sealed to, run the shared machine-learning scoring models, and commit VEID trust scores by consensus — the patented method (AU2024203136B2) at the heart of the protocol. Compensation is governed by the conservative staking and issuance policy; no fixed VEID pool is promised.
Duty three: governance
Validators vote on parameter changes, upgrades, and chain configuration — including the approved-client list controlling which interfaces may submit identity data. Governance participation is part of the operational mandate.
How it works
The path through the protocol, step by step
Select each step — the panel walks the sequence in order, from first action to settled outcome.
Step 1 · Study
Study the launch posture
TestNet is planned for January 2027 and MainNet for March 2027 after TestNet exit criteria and a separate production approval. Verify formal launch confirmation before operating.
Step 2 · Provision
Provision secure infrastructure
High-uptime hosts plus hardened key management for both consensus keys and VEID encryption keys.
Step 3 · Size
Plan for identity-network duties
ML scoring of encrypted scopes runs alongside consensus — size compute and operations accordingly.
Step 4 · Bond
Bond stake and attract delegation
Self-bond, publish your operational record, and earn delegations. Bonded stake weights voting power.
Step 5 · Govern
Participate in governance
Vote on upgrades and configuration from day one — governance participation is part of the mandate.
Economics
Economics
Validator income remains governance-controlled and conservative relative to the prior model. Staking rewards, commission, unbonding and slashing conditions are protocol parameters, not fixed-return promises; slashing risk applies to delegated stake too.
Getting started
The path in
-
Study the launch posture
TestNet is planned for January 2027; MainNet is planned for March 2027 after TestNet exit criteria and a separate production approval. Verify formal launch confirmation before operating.
-
Provision secure infrastructure
High-uptime hosts plus hardened key management for consensus and VEID encryption keys.
-
Plan for identity-network duties
ML scoring of encrypted scopes runs alongside consensus — size accordingly.
-
Bond stake and attract delegation
Self-bond, publish your operational record, and earn delegations.
-
Participate in governance
Vote on upgrades and configuration from day one.
Questions
Asked about validators
What exactly are the validator's duties?
Three: propose and validate blocks under CometBFT; operate the VEID Network by decrypting sealed identity scopes, running the shared scoring models, and committing trust scores by consensus; and vote on governance — parameters, upgrades, and chain configuration.
How are validators paid for identity work?
Compensation is governed by the conservative staking and issuance policy — validator income remains governance-controlled and conservative relative to the prior model. No fixed VEID pool or fixed return is promised.
What can get a validator slashed?
Double-signing and extended downtime are slashable, and slashing applies to delegated stake too — which is why delegators should choose on operational quality. Unbonding and slashing conditions are protocol parameters, not fixed-return promises.
Related
Continue from here
More solutions