A compute claim should make a delivery obligation legible to a buyer or software agent. The unit and acceptance criteria matter more than a ticker symbol.
Standardized terms
A useful schema names accelerator class, memory, region, reserved quantity, start and end times, workload limits, evidence requirements, and dispute route. Two claims with different terms should not appear fungible merely because both say H100.
Capacity backing
The provider commitment must be measured against usable capacity after maintenance, prior reservations, and oversubscription buffers. A cap in code constrains accounting; it does not verify that a machine exists.
Transfer and redemption
Transferability is useful when a buyer procures capacity for another team. Redemption should lock a portion of the pool before dispatch, expose status to the buyer, and prevent double spending.
Failure handling
An expired, unavailable, or partially fulfilled claim needs defined refund and remedy rules. The prototype does not yet include all operational enforcement required for commercial delivery.
Questions, answered.
Can a claim be resold?
The proposed Sui object may be transferable, but actual resale permissions, liquidity, and legal restrictions depend on implementation and jurisdiction.
Does a token guarantee GPU access?
No. Access depends on an attested provider, working scheduler, valid delivery window, and enforceable failure remedies.
Compare the contract, not just the GPU.
These pages explain a proposed infrastructure design. Browse the reference marketplace without assuming a listing is available to buy.
Explore marketplace →