VirtEngine

For validators & staking partners

Stake the network that verifies identity by consensus

VirtEngine validators do double duty: they secure the chain and operate the VEID Network. Delegators and staking partners share the rewards — and the responsibilities.

Validator documentation Mainnet posture

How it fits

Delegated proof of stake, with an identity twist

fig 01 — stake, duties, rewards, and slashing

Economics

Conservative staking, identity-led issuance

Staking rewards remain, but the proposed model substantially reduces their issuance relative to the prior design. Economic parameters take effect only through network governance.

~90% lower

Proposed staking issuance vs. prior model

Proposed policy

14 : 1

Eligible humans to Foundation genesis allocation in each 15-token batch

Proposed policy

50 years

Illustrative identity-allocation horizon

Proposed policy

Quarterly

Illustrative activity check

Proposed policy

The proposed issuance model recognises verified uniqueness rather than treating participation only as capital. When a user reaches the network-defined threshold for a unique verified identity, the protocol may mint tokens to that account over time while the account remains active. The working illustration is a quarterly sign-in check across a 50-year horizon; the threshold, cadence and horizon are protocol parameters, not a promise of an individual entitlement.

Each 15-token VEID issuance batch allocates 14 tokens to eligible active verified humans and 1 token to the Foundation-controlled genesis account. The Foundation token is part of the 15-token batch, not an additional token. That ratio, like all issuance parameters, can be changed by consensus. Validator and delegator staking rewards remain, but are proposed at roughly one tenth of the previous allocation.

Validator duties

Three jobs, one bonded stake

Consensus

Propose and validate blocks under CometBFT. Bonded stake weights voting power; uptime and correctness earn block rewards.

Identity network

Uniquely to VirtEngine, validators can participate in the VEID Network: scoring eligible encrypted identity scopes with shared models and committing trust results by consensus. VEID is decentralised protocol infrastructure, not a Foundation-operated verification service.

Governance

Vote on parameter changes, upgrades, and configuration — including the approved-client list that controls which interfaces may submit identity data.

Requirements

Running a validator

Delegation

Staking without running hardware

Token holders and staking-as-a-service partners can secure the network by delegating to validators they trust.

Delegators

Delegate stake to one or more validators and earn a share of their rewards, net of commission. Your tokens stay in your control — delegation grants voting weight, not custody. Spreading stake across smaller validators strengthens the network's Nakamoto coefficient.

Staking partners

Staking services can operate validators or aggregate delegations for their clients. The delegation module (x/delegation) manages the full lifecycle on-chain. Partners should surface slashing risk and the 21-day unbonding period to their customers plainly.

Risk

Slashing, stated plainly

Staking is not risk-free. Bonded stake — including delegated stake — can be slashed for validator misbehavior such as double-signing or extended downtime. During the 21-day unbonding period your tokens earn no rewards and remain slashable for offenses committed while bonded. The tokenomics framework models slashing penalties explicitly (basis-point penalties in the economic security audit); choose validators on operational quality, not just commission.

Mainnet

Launch posture

Mainnet is planned for the January 2027 launch window. The network and its dependent services should not be described as live before the launch is formally confirmed. See the network page for the current posture and release materials.

Network status & genesis Validator onboarding docs

Go deeper

The economics and the risks, in full