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

Sources

re-zerve is a research product: a public compute deployment / order, an encrypted bid, and a commitment-only chain record. These are the specifications and libraries the stack is built from. Each line is a title, a public link, and why it matters here.

This is not a bibliography of everything we read. If a paper or crate is not on this page, it is not part of the product path (or it is explicitly not this path).

re-zerve is available in the local lab. It is implemented in the crate. It is not on the public network yet as a marketplace.

Market shape

• Akash core concepts — deployer, provider, deployment, order, bid, lease, escrow.
• Akash SDL — Stack Definition Language. The public ask is an Akash-shaped SDL plus resources. The lease key is not the public ES256K JWT. Access is a derived bearer from the out-of-band seal key.
• Deployments & lifecycle — deployment opens an order; providers bid; accept creates a lease; then the manifest goes to the provider.
• Provider service overview — provider-services, bid engine, hostname operator, inventory operator. When PIR env is unset this binary stays on the public marketplace.
• RFC 8439, ChaCha20-Poly1305 — the bid envelope. Associated data binds ask id and nonce. Price and identity stay in the plaintext that never hits the chain.
• RFC 7693, BLAKE2 — ZAP1 leaf and node hashes (NordicShield_ / NordicShield_MRK personalization in zap1-verify).

Pay inclusion (ZAP1 + Halo2)

• Frontier-Compute/zap1 — ZAP1 writes typed lifecycle events into a BLAKE2b Merkle tree. re-zerve uses the HOSTING_PAYMENT event kind. Anchoring a root in a shielded memo is specified by ZAP1; this product does not treat memo-open as inclusion.
• zap1-verify (zap1-verify 0.2.1 on crates.io) — leaf hash and Merkle path check used to build the witness. On-chain execute does not re-walk siblings.
• ZIP 302, Encrypted Memo Format — memo container. Recorded as a tip reference when stamped; not opened as a Zcash state root.
• Bowe, Grigg, Hopwood, Halo and zcash/halo2 — recursive proof composition without a trusted setup. The CosmWasm host verifies Halo2, not a dummy STARK.
• The Pasta curves (pasta_curves) — Pallas / Vesta. re-zerve stores a Pasta circuit (circuit-type 0, curve-type 0, k=17, four public instances). Halo2-axiom KZG on BN256 is a different curve id and is not this circuit.
• CosmWasm zk-wasmvm Path A — store-full-circuit pins the verifying key; the guest calls host proof_instance_verify(zkid, proof, instances). Missing host fails closed.

Custody (FROST + Ironwood)

• Komlo, Goldberg, FROST, eprint 2020/852 — two-round threshold Schnorr. Product custody is DKG among deployer, provider, and resolver, not a dealer.
• RFC 9591, FROST and ZF frost-ed25519 — the ciphersuite this crate signs with. Happy-path sign is deployer + provider. The resolver signs only after a recorded close grant.
• ZIP 32, Shielded Hierarchical Deterministic Wallets — named stand-in for Ironwood spend authority: ZIP-32 of the reconstructed DKG group seed. ZIP-312 RedPallas is not in Zakura.
• ZIP 258, NU6.3 / Ironwood and zcash/ironwood — shielded value is the Ironwood pool (NU6.3 v6, V3 notes). Same action shape as Orchard, distinct tree and nullifiers. Not Sapling. Not Orchard.
• ZIP 317, Proportional Transfer Fee — lab shield fee accounting on Zakura sendrawtransaction (not zcashd).
• Zakura — local Zcash-family node used to create and spend those notes in the lab.

On-chain record (Cosmos)

• CosmWasm — cw-pir-commit (ask/bid hex only), cw-pir-escrow (grant and events, not bank coins), cw-zap1-ibcv2 (AttestHalo2).
• IBC — IBC v2 packet bind (clients, sequence, app-data hash). Crosslink 08-wasm verifies headers. That is a different client and is not pay inclusion. Crosslink is not ZAP1.

How they show up in this product

See How it works, Dependencies, For engineers, and Status.