Compute rental.

Compute rental is not a separate role with its own bond. A node that serves AI already declares the capability; renting out compute rides the same serving role and the same stake. One node can serve inference and rent capacity at once, and a single stake covers both — accounted through one shared coverage tracker.

A consumer books capacity for a fixed term. Booking locks the consumer's exposure (price_per_epoch × total_epochs) and registers the provider's obligation against its stake. Booking fails if the stake cannot cover the new obligation on top of everything else the node owes — storage included.

book_rental(renter, provider, asset_id, price_per_epoch, total_epochs)

Each epoch the provider settles with an availability proof. The outcome is one of three: Settled (the proof was valid; one slice moved), Missed (no proof; no value moved and the consumer keeps the slice), or Closed (term reached, coverage lost, or the miss threshold crossed).

settle_epoch(rental_id, proof_valid) -> EpochOutcome

A rental is not paid up front. The consumer locks the full term, but value releases one epoch-slice at a time as the provider proves availability. Unspent term stays the consumer's until it is earned.

Both compute rental and per-byte storage bill against a renter's prepaid TNZO balance rather than debiting the on-chain account every epoch. A deposit debits the renter's real balance once and credits the prepaid ledger; each epoch streams a slice out of that ledger to the provider, or refunds it on a miss. A withdraw returns the unspent remainder. Every deposit, stream, and refund writes through to CF_SETTLEMENTS and hydrates on restart, so a locked deposit and any accrued provider credit survive a node restart mid-term.

# RPC
tenzro_prepaidDeposit
tenzro_prepaidWithdraw
tenzro_prepaidBalance

The provider chooses how its rate is set. Fixed names a flat rate per epoch. Network-dynamic tracks utilization through an EIP-1559-style controller over a smoothed signal — denominator 8 (per-step move bounded ±12.5%), 50% target, smoothing window 4. Consumers see the effective rate before they book.

The invariant is uniform across the network: the consumer pays from their TNZO balance; the provider earns into theirs. There is no separate settlement path for compute — it uses the same balances the rest of the network settles against.

# RPC
tenzro_computeBookRental
tenzro_computeSettleEpoch
tenzro_computeGetRental
tenzro_computeSetPricing
tenzro_computeStatus

# CLI
tenzro node compute status
tenzro node compute book-rental --asset <id> --epochs <n>
tenzro node compute settle-epoch --rental <id>
tenzro node compute set-pricing --mode <fixed|dynamic>