Generated — do not edit. Source of truth: abstract/re-zerve/crate/product-docs/vocs/how-it-bolts.mdx. Edit there, then run pnpm sync:product-docs.

How it bolts to Akash

Akash is already a marketplace. A deployer describes a workload in SDL. That deployment opens an order. Providers bid. A lease places the workload on a cluster.

The first demonstration adds a market on Terp, uses Penumbra validator sidecars as FROST signers, and runs a custom Akash provider. See First demonstration.

Public Akash stays the default when the private path is off.

Public Akash

Public Akash marketplace: deployer, deployment, bid with price on the book, lease with JWT, provider cluster

SDL, the order, the bid engine, the JWT on a public lease, and the cluster operators are ordinary Akash.

Private path, same process

Two lanes in one provider-services binary: public Akash on top, sealed bid and commitments below, sharing the same order

The order is still public. Anyone can read the SDL and resources.

The bid is sealed and sent to the deployer. Price is not written on the order book. The chain-shaped record stores a commitment (a hash), then the bid engine allocates only after that commitment matches.

The lease is still a lease. The credential that opens the private endpoint is a derived access bearer, not the public ES256K JWT.

When the private path is off, provider-services behaves as it does today on public Akash.

What stays, what the private path adds

What stays on Akash versus what the private path adds

On Akash	Public path	Private path
SDL / deployment / order	Unchanged	Same public order
Bid	Price on the book	Sealed envelope. Hash on the record.
Allocate	Bid engine as today	After the commitment matches
Lease	Agreement + ES256K JWT	Same agreement. Derived bearer at the gateway.
Payment	AKT / USDC escrow	Shielded notes. The contract records a grant; it does not send bank coins.
Process	`provider-services`	The same binary. Configuration selects the path.
Hostname / inventory	Unchanged	Unchanged
Image	Public Akash provider image	Private path ships as a `provider-services` build with PIR support

How the pieces sit on a lease

Provider image, CosmWasm VM, ZAP1 IBC v2, and FROST sidecars mapped onto the lease

Piece	Role	Relation to Akash
Provider image	Allocate, serve, stop	Same `provider-services` binary as the public bid engine
CosmWasm	Commitments, proof verify, close grant	A record beside the order. It does not pay the notes.
ZAP1 IBC v2	Pay inclusion	Attests a hosting payment. It is not the Crosslink header client.
FROST holders	Spend authority	The provider is one of three signers on the note that closes the lease

The provider is still an Akash provider. On the private path they are also a signer on the funds.

A private lease

The deployer posts a public deployment and order.
The provider sends a sealed bid to the deployer.
Only commitments appear on the public record.
The bid engine allocates after a match.
The winner opens the endpoint with the derived bearer. Anyone else is refused.
Close splits the shielded note: earned to the provider, remainder to the deployer.

Sealing, proofs, and spend math are on How it works and Dependencies.

This path runs locally today. It is not the default on the public Akash network.