Protocol
One chain that runs a cloud marketplace end to end
VirtEngine is a purpose-built blockchain: consensus, identity verification, resource exchange, and payment settlement in a single Go binary. Here is how it fits together.
Architecture
From client to cluster
Four layers: clients sign transactions; the chain orders and executes them by consensus; provider daemons translate leases into running workloads; infrastructure delivers the compute.
Module map
Twenty-seven modules, four domains
Everything the marketplace needs lives in x/ modules on the chain — every module has a dedicated reference page.
Marketplace & workloads
The exchange itself — orders, bids, leases, provider registration, and workload capability surfaces.
-
x/marketOrder, bid, and lease state machine -
x/marketplaceMarketplace coordination and offering surfaces -
x/deploymentTenant deployment specifications and groups -
x/providerProvider registration and attributes -
x/resourcesResource unit and capacity definitions -
x/hpcHPC job marketplace for scheduler-backed clusters
Identity & security
VEID identity scoring, credential registries, multi-factor authentication, and encrypted data handling.
-
x/veidIdentity verification and trust scoring -
x/veidregistryIdentity record and scope registry -
x/mfaOn-chain multi-factor authentication policies -
x/certTLS certificates for provider/tenant mutual auth -
x/encryptionPublic-key encryption for sensitive on-chain data -
x/enclaveConfidential compute and enclave attestation -
x/fraudFraud reporting and enforcement hooks -
x/rolesRole-based access control across modules
Economics & settlement
Escrow-backed payments, zero marketplace commission, validator transaction fees, staking, and VEID-led issuance economics.
-
x/escrowFunds held against active leases -
x/settlementUsage-record settlement into payments -
x/takeZero-rate marketplace settlement policy -
x/bmeBurn-and-mint equilibrium mechanics -
x/stakingValidator staking extensions -
x/delegationDelegation lifecycle management -
x/issuancepolicyToken issuance policy controls -
x/oracleExternal price and data feeds
Quality & governance
Audited attributes, benchmarking, reviews, support flows, and chain configuration.
Lifecycle
Order to settlement, on chain
Every marketplace interaction follows the same five-stage state machine.
- 01 Order
- A tenant posts a deployment order on-chain describing the resources they need — compute, memory, storage, region, and attributes.
- 02 Bid
- Provider daemons watching the chain place competing bids against open orders on behalf of their configured providers.
- 03 Lease
- The tenant's winning bid becomes a lease. Escrow is funded, and the provider daemon instantiates the workload through its orchestration layer.
- 04 Usage
- The provider daemon meters running workloads and submits signed usage records to the chain on a scheduled cadence.
- 05 Settlement
- After a 24-hour dispute window, the settlement module converts usage into billable line items and releases the agreed escrowed funds to the provider with no marketplace commission deducted.
Economics
Tokenomics designed for a self-balancing network
The economic model is validated by an in-repo simulation and audit framework (pkg/economics) covering inflation dynamics, staking rewards, fee markets, distribution fairness, and attack costs.
1B → 10B
Initial supply, hard maximum supply
docs/tokenomics-analysis.md
14 : 1
Eligible humans to Foundation genesis allocation per 15 issued
Proposed policy
Identity-led
Proposed issuance model
Proposed policy
0%
Marketplace commission; validator transaction fees are separate
Proposed policy
Inflation adjusts dynamically: when the staking ratio falls below target, inflation —
and therefore staking APR — rises to attract bonding; above target it falls. The
21-day unbonding period, burn-and-mint mechanics (x/bme), and a
conservative staking rewards round out the incentive design. Details on the
staking page and in the
protocol documentation.
Governance & security