Generated — do not edit. Source:
/Users/returniflost/abstract/terp-core/crates/private-inference-rent/product-docs/vocs/index.mdx. Change the crate/repo, then rebuild this site.
re-zerve
re-zerve is a capacity side-market on Akash-shaped ops. A deployer (Akash also says tenant, once: the user who creates a deployment) describes resources in SDL (Stack Definition Language). That public request is a deployment; it opens an order. A provider answers with a bid. On the public Akash marketplace the bid price is on the order book. On this side-market the bid is an encrypted envelope — price off that book — and the chain-shaped record holds commitments only.
The lease is the agreement that reserves capacity. The credential that opens it here is a derived access bearer, not the public ES256K JWT.
This path runs locally today. It is not the default on the public Akash network.
First demonstration
First demonstration: additional market on Terp, Penumbra validator sidecars as FROST signers, custom Akash provider. How it bolts to Akash is the public marketplace next to that path.
Who this is for
For deployers
Create a public deployment, keep price and identity off the order book, authorize payment, open the lease with a derived access bearer.
For providers
Public orders, encrypted bids, commit before allocate, derived access bearer at the gateway. Same provider-services binary; public marketplace when PIR env is unset.
For engineers
Shipped types and contracts. Lab crate vs public network. Crosslink is not pay inclusion.
Market shape
The deployer posts a public order. The provider sends an encrypted bid off-chain. The commitment store records hashes only — no price, no identity.
What is public vs private
| Public / committed | Private / off-chain |
|---|---|
| Deployment / order (SDL, resources, inference profile) | Bid price |
| Ask commitment | Bidder identity |
| Bid commitment (hash of the sealed envelope) | Provider endpoint in the plaintext bid |
| Lease open / closed | Seal key and derived access bearer |
On the private path
- a sealed bid (price off the public order)
- a commitment-only public record
- the provider as a FROST signer (with deployer and resolver)
- Ironwood shielded notes at close (the CosmWasm module records a grant; it does not send bank coins)
Pay inclusion is a hosting-payment event in the ZAP1 tree, verified on-chain with Halo2. See How it works, Dependencies, Status, and Sources.