01 / Explanation
Intelligence needs infrastructure
Agents need processors, memory, storage, network access, and energy. VirtEngine describes a market that connects workloads with independently supplied services. Listings, bids, leases, and usage records make parts of that agreement inspectable; they do not remove physical scarcity.
02 / Explanation
Funds and evidence have different jobs
Escrow secures the funds associated with an agreement. Usage records support billing. Provider benchmarks, attestation, and audit contribute different evidence about quality and execution. A tenant should not treat escrow as proof that a workload ran correctly.
03 / Explanation
Follow the denominations
VE is the native asset (uve); VirtEngine Compute Credit, VCC (uvcc), names the service-accounting unit. Provider policy calls for the full agreed escrow payout with transaction fees separate. The BME conversion handlers currently return pending without executing conversion, while billing transfers coins and defaults to zero fee burn. Naming a credit does not establish an operational conversion, peg, or redemption guarantee. Model every issuance, refund, and remint separately.