Skip to main content

Compute

Real GPU rental checks.

Every six hours, Covenant attempts a real GPU rental: fund, connect, inspect, close and verify cleanup. The results show what completed and what still needs attention.

Retrieving rental-check report…

Loading rental checks

No current rental result can be confirmed until the reporting service responds.

Rental-check report (JSON) ↗

What each check covers

  1. 01

    Fund and rent

    Use the released buyer client to fund and request a real GPU lease within the pilot budget.

  2. 02

    Connect and inspect

    Authenticate the SSH host identity, open a connection and inspect the GPU exposed to the rented instance.

  3. 03

    Close and reconcile

    Close the lease, verify the settlement on Solana and reconcile the buyer’s charge and unused escrow credit.

  4. 04

    Confirm cleanup

    Check that the provider no longer has the rented instance. An unresolved instance keeps the run from passing.

A passed run confirms that one rental completed these checks at the recorded time. It does not measure all available GPUs, guarantee a future rental or establish hardware attestation.

Read the result in context

Passed
The rental completed every required check, including settlement, balance reconciliation and provider cleanup.
In progress
The run has started. A final result has not been confirmed.
Blocked
A requirement such as capacity, configuration or available budget prevented a complete check. The recorded reason explains the limit.
Failed
The run recorded a check that did not succeed. Any remaining settlement or cleanup is tracked separately.
Recovery complete
Outstanding settlement or cleanup was resolved after an interruption. This does not turn an incomplete rental into a passed GPU check.
Report overdue or unavailable
The reporting heartbeat is stale or cannot be read. The current state is unknown; historical results keep their original verdicts.
Paused
New rentals are intentionally stopped, including when the rolling daily allowance or total pilot budget is exhausted.

Pilot limits

The schedule is six-hourly, with new rental commitments capped at $2 in a rolling 24-hour window and $20 for the pilot. An insufficient budget pauses new rentals. Outstanding reservations continue to count until they are reconciled.

Three consecutive missed or unsuccessful windows trigger an operational alert. A missed window is not a completed rental, and an empty capacity response is not proof of a service outage.

The reporting heartbeat and the rental schedule are separate. A fresh report can contain an older rental result; every result keeps its own timestamp. All displayed times use UTC.