VirtEngine Module Reference

Every piece of protocol behavior lives in a Cosmos SDK module under x/ in the virtengine repository. This section documents each of the 27 modules in depth: what it stores, the messages it accepts, the queries it exposes, and how it talks to the rest of the protocol.

For the grouped overview with one-line purposes, see the On-Chain Module Map. Module APIs are defined in each module’s types/ package — when these pages and the code disagree, the code and its tests are authoritative (see Clients & SDKs).

Marketplace & workloads

The exchange itself — orders, bids, leases, provider registration, resource definitions, and the HPC job marketplace.

Module	Purpose
x/market	The order, match, and lease state machine at the center of the marketplace.
x/marketplace	Marketplace coordination and offering surfaces layered over the core exchange.
x/deployment	Tenant deployment specifications and groups — what tenants ask the marketplace to run.
x/provider	Provider registration and the on-chain attribute record tenants filter against.
x/resources	Shared resource-unit and capacity definitions used across the marketplace.
x/hpc	The HPC job marketplace for scheduler-backed supercomputing clusters.

Identity & security

VEID identity scoring, the identity registry, multi-factor authentication, certificates, encryption, enclave attestation, fraud enforcement, and access control.

Module	Purpose
x/veid	Identity verification and trust scoring — the patented core of the protocol.
x/veidregistry	The registry of identity records and scopes that other modules resolve against.
x/mfa	On-chain multi-factor authentication policies for sensitive operations.
x/cert	TLS certificates for mutual authentication between providers and tenants.
x/encryption	Public-key encryption so sensitive on-chain data is readable only by intended recipients.
x/enclave	Confidential-compute and enclave attestation for sensitive workloads.
x/fraud	Fraud reporting and enforcement hooks that police marketplace conduct.
x/roles	Role-based access control shared across the protocol’s modules.

Economics & settlement

Escrow-backed payments, governed settlement fees, validator transaction fees, VEID-led issuance, staking, delegation, and oracles.

Module	Purpose
x/escrow	Funds held on-chain against active leases, released only by settlement rules.
x/settlement	Converts signed usage records into billable line items and provider payouts.
x/take	Governed marketplace settlement policy; validator transaction fees remain separate.
x/bme	Burn-and-mint equilibrium mechanics linking token supply to marketplace demand.
x/staking	Validator staking extensions over Cosmos SDK staking, tuned for the dual validator role.
x/delegation	The full delegation lifecycle for token holders and staking partners.
x/issuancepolicy	Governed controls over how and when new tokens are issued.
x/oracle	External price and data feeds brought on-chain for pricing and policy.

Quality & governance

Auditor-signed attributes, hardware benchmarks, reviews, support and dispute intake, and governed chain configuration.

Module	Purpose
x/audit	Auditor-signed provider attributes that upgrade self-claims into attestations.
x/benchmark	On-chain hardware benchmarking records that ground offers in measured performance.
x/review	Tenant–provider reviews building portable, tamper-evident reputation.
x/support	Support and dispute intake flows for marketplace participants.
x/config	Governed chain-level configuration — including the approved-client list.

Related reading

• Architecture — how the modules fit together in the node.
• How the Marketplace Works — the order → match → lease → usage → settlement lifecycle these modules implement.
• Clients & SDKs — exploring module APIs from the CLI, Go and TypeScript.