Skip to main content

Local proving and resources

Private operations give a local prover the Note/Credit openings, membership paths and transient authorization needed to bind a proof to the public statement. A service verifying public proofs does not need these witnesses.

RuntimeEntry pointApplication requirements
Node / native services@invisi-labs/prover/nativeMatching BB binary, authenticated circuits/VKs and cache
Browser@invisi-labs/prover/wasmMatching WASM, dynamic chunks, thread environment and CRS
Go / RustCorresponding local proverCompatible witness generation, BB and authenticated resources

Core and Provenance use independent resource sets. Core-only operations do not need the Provenance catalog. Configure it when source proving is needed; missing resources must not silently select a different version.

Configure local resources​

This TypeScript factory configures a backend without proving immediately. Supply the BB executable and authenticated Core directory. The separate provenanceCatalog is needed only when generating source proofs.

import { NativeProver } from "@invisi-labs/prover/native";

export function localProver(bbBin: string, coreCatalog: string, provenanceCatalog?: string) {
return new NativeProver({
bbBin,
resources: {
directory: coreCatalog,
...(provenanceCatalog ? { provenanceDirectory: provenanceCatalog } : {}),
offline: true,
},
});
}

offline: true disables circuit/VK downloads only. It does not make WASM initialization or CRS access offline. Browser applications must separately deploy runtime assets, dynamic chunks and required thread variants.

Execution order​

  1. Freeze network, instance, inputs, outputs and execution mode.
  2. When using Broadcaster, obtain and review the final quote first.
  3. Export Wallet EIP-712 authorization, display its terms and attach the signature.
  4. For operations requiring ZK evidence, call prove() with matching resources and verify the result. Use ready() for Shield and the separate owner-authorization path for Credit revocation.
  5. Attach separate public funding authorization where required, validate submission, then send.

Shield needs no ZK proof. Owner Credit revocation follows its separate authorization path. Direct EVM proofs and recursive members are not interchangeable; proving must match the signed quote’s execution.

Failures​

Report resource hash mismatch, missing VK, incorrect network, proof failure and RPC timeout separately. Reproving must not create a new payment. Preserve the operation, reservations and submission outcome. Do not upload private keys or witnesses to a public service as an automatic fallback.

Caching does not replace trusted resource identity. Package installation also does not establish resource publication. See compatibility.