VirtEngine

For providers

Lease your capacity into an open marketplace

Datacenter operators, cloud providers, and HPC facilities earn revenue by serving on-chain leases — with metering, billing, and payment handled by the protocol.

Provider documentation Onboarding path

Why provide

What the protocol does for an operator

Monetize idle capacity

Turn unused racks, cloud headroom, or HPC cycles into revenue. The marketplace matches your capacity with tenant demand — you set your own bid pricing strategy.

Settlement without invoicing

Usage is metered, reported, and settled by the protocol. Payment releases from escrow automatically after the dispute window — no accounts receivable, no chasing customers.

Verified counterparties

VEID identity scoring means you know tenants are verified before workloads land on your hardware, and tenants can verify you — cutting fraud in both directions.

Reputation that compounds

Auditor-signed attributes, on-chain hardware benchmarks, and tenant reviews build a portable, tamper-evident track record that wins better-priced leases over time.

Economics

Usage in, payment out

The settlement pipeline connects your running workloads to escrowed tenant funds. Every hop is signed, windowed for disputes, and reconciled.

fig 01 — usage reporting and settlement pipeline (docs/usage-reporting-settlement.md)

Settlement runs on a default one-hour interval. Reported usage sits in a 24-hour dispute window during which either party can raise corrections; anomaly detection flags outliers automatically before they ever reach the chain. After the window closes, line items settle against lease escrow and the agreed funds transfer to your provider account with no marketplace commission deducted. Low validator transaction fees apply only to the on-chain actions involved.

Provider daemon

One daemon between the chain and your infrastructure

The provider daemon is the protocol's on-premises agent. You configure it; it handles the marketplace.

HPC

Supercomputing capacity is a first-class citizen

If you run SLURM, MOAB, or Open OnDemand, the daemon's HPC integration executes on-chain jobs on your cluster — with usage reporting, state recovery, audit logging, and retry built in.

slurm · moab · ood

Scheduler adapters

Native adapters speak to your existing controller — munge or JWT auth for SLURM, with per-partition configuration. No re-platforming of your cluster.

x/hpc

Job lifecycle service

On-chain HPC jobs are polled, dispatched, and tracked with configurable concurrency limits, timeouts, and crash-safe state recovery.

usage · security

Audit trail

Job events, security events, and usage reports are logged to a dedicated audit log, and usage batches flow into the same settlement pipeline as cloud workloads.

Requirements

What you need to bring

Onboarding

Five steps to your first lease

  1. Verify your identity

    Complete VEID verification. Marketplace access is identity-gated so tenants and providers can trust the other side of every lease.

  2. Register on-chain

    Create your provider record with attributes — region, hardware classes, certifications — via the x/provider module.

  3. Deploy the provider daemon

    Install and configure the daemon against your Kubernetes cluster or HPC scheduler; connect your chain key and set bid pricing.

  4. Get audited & benchmarked

    Optional but valuable: auditor-signed attributes and published hardware benchmarks make your offers stand out to tenants that filter on them.

  5. Bid, serve, settle

    The daemon bids on matching orders. Won leases run on your infrastructure, usage settles hourly, and escrow pays out after the 24-hour dispute window.

Start with the provider docs Provider economics, explained Check network status

By operator type

Solutions for your kind of capacity