Generated — do not edit. Source: /Users/returniflost/abstract/terp-core/crates/private-inference-rent/product-docs/vocs/how-it-works.mdx. Change the crate/repo, then rebuild this site.

How it works

Four steps. Each keeps a different secret off the public record. This is Akash-shaped — deployer, provider, bid, lease, SDL — plus a dedicated side-market in the same provider-services binary.

A deployer (Akash also says tenant, once) creates a deployment: a public resource request written in SDL (Stack Definition Language). That opens an order. A provider answers with a bid. A lease is the agreement that reserves capacity.

1. Deployment, order, and bid

The public surface is the deployment / order (SDL and resources). The side-market bid is an encrypted envelope sealed with ChaCha20-Poly1305 and delivered out of band. Price is off the public order book. The chain stores commitments only.

See For deployers and For providers.

2. Pay inclusion

A HOSTING_PAYMENT leaf is in the ZAP1 BLAKE2b tree. The prover keeps serial, month, year, and Merkle siblings in the witness. The chain verifies a Halo2 proof against a pinned verifying key. Public instances are 128 bytes: merkle root, FROST group, amount class, payment kind.

An IBC v2 packet binds note, amount, group, and leaf. SpendAuth from a layered quorum credits the FROST pool.

Crosslink headers are a different client. They are not this pay path. Crosslink is not ZAP1.

3. Custody and close

Three parties run FROST DKG: deployer, provider, resolver. Happy-path sign is deployer + provider. The resolver signs only after a recorded close grant.

Value is Ironwood shielded notes on Zakura. Close is two spends: earned to the provider, remainder to the deployer. ZIP-312 RedPallas is not in Zakura; the named stand-in is frost-spend-v1 plus ZIP-32 of the reconstructed DKG group seed.

The CosmWasm escrow module records the grant. It does not pay in bank coins. It does not move uterp as money. There is no viewing key on escrow.

Accrued amount is f(open_height, close_height, rate) from Zakura heights (Halo2 of that function). The closer does not set earned.

4. Lease access

Accept the winning bid. The lease credential on this path is the derived access bearer (from the out-of-band seal key). It is not the public ES256K JWT. A foreign bearer is denied. After close, the winner is denied too.

Related

Dependencies names the provider image, CosmWasm VM, ZAP1 IBC v2, and FROST holders. Status says what runs locally.