From requirement to verified delivery
V0.1 runs this process with human verification at every step. There is no automated matching engine and no automated settlement.
Who submits demand
Institutional buyers with a genuine compute requirement — not a price enquiry.
- AI companies and model developers
- Enterprise AI teams
- Telecom operators
- Cloud platforms
- Institutional buyers and integrators
Who submits capacity
Operators with installed accelerators they can actually deliver against.
- Data centres
- GPU infrastructure operators
- Cloud infrastructure providers
- Compute providers and resellers
The six steps
Each step produces a record with a status. Nothing advances on its own.
RFQ
A buyer submits a requirement: GPU, quantity, region, start date, term, network, SLA and target price. It enters the demand book as New RFQ.
Capacity
A provider submits available infrastructure. It enters the capacity book as Reported and stays there until MACOMX confirms it.
Match
MACOMX pairs demand with capacity on quantity, region, timing, network, SLA and price spread. Pairing is manual.
Quote
A quote is issued with quantity, term, GPU-hours, currency and an expiry time. It is Indicative until both sides confirm, then Firm.
Delivery
Capacity is reserved, contracted and provisioned against the agreed specification.
Verification
Delivery is verified and reported before any settlement instruction is issued.
Capacity verification status
A capacity record carries exactly one of these. A badge is applied only after internal approval — never inferred from how a provider describes itself.
Submitted by the provider
The provider has stated the capacity. MACOMX has not yet contacted them about it.
Contacted and confirmed
MACOMX has reached the provider and confirmed the basic information in the record.
Technically verified
Technical or documentary verification of the capacity has been completed.
Reserved
Reserved for capacity connected to the MACOMX Compute Verification Protocol. Not in use at V0.1.
MCVP — Compute Verification Protocol
A standardised way to verify that compute capacity exists and that service was actually delivered, across providers who each run different systems.
Provider infrastructure
The cluster, its power and its network as operated today.
Existing systems
DCIM, DCGM, monitoring, scheduler and API — MCVP reads what is already there.
MCVP
Different providers' telemetry expressed in one comparable form.
Verified GPU-hour
A delivery record both sides can rely on, and a verification report.
MCVP is a verification protocol under development by MACOMX. It is not an official standard and not a government certification. It is designed to work alongside a provider's existing monitoring and management systems rather than replace them.
Transaction assurance
The sequence a future transaction is intended to follow. None of it is automated at V0.1.
Funds secured
Held by an appropriately licensed institution, never by MACOMX.
Capacity reserved
The provider takes the capacity off the available book.
Compute delivered
Provisioned to the contracted specification.
Delivery verified
Reported against the agreed measure of delivery.
Settlement released
Instruction issued to the licensed institution holding the funds.
Regulated payment, escrow and settlement services, where applicable, will be provided by appropriately licensed financial institutions. MACOMX does not hold client funds and does not provide these services itself.
The process only starts when something real enters it.
One firm ask from an operator, or one genuine requirement from a buyer.