Build, artifact, runtime image, policy, configuration and state commitments.
Every cryptographic launch leaves an evidence trail.
Genesis creates a portable Proof Pack for every launch attempt — successful, denied, failed, aborted, or dry-run — documenting the observed cryptographic state, measured benchmarks, usage evidence, governance decision, receipts, and verification lineage.
Crypto Proof Pack
Know exactly what happened. Not a promise of an outcome. A verifiable record of what the Genesis runtime actually observed, measured, authorized, executed, denied, or failed to verify.
p50 / p95 / p99, throughput, sample counts, payload sizes, failures and measurement context.
Bridge profile, algorithm, provider, security floor, key reference, freshness and verification.
Observed operation counts and bytes from an authoritative runtime source. Never inferred.
Request, authority and execution/denial receipts linked through evidence lineage.
Recomputable hashes and instructions for checking the recorded evidence.
Before you launch
Genesis will create a Proof Pack for this launch attempt when the live runtime path actually performs one. It records the cryptographic state, benchmarks, usage evidence, receipts and verification results that were actually observed. This page does not claim that a launch occurred merely because the surface is available.
- Unknown or unmeasured values remain UNKNOWN/PENDING.
- Secrets and private key material are never placed in the Proof Pack.
- A direct public surface does not grant execution authority; consequential effects still require the existing Genesis authority path.
- You remain responsible for evaluating whether and how to use the service and its outputs and for consequential decisions you make or authorize, subject to the governing Genesis agreement and applicable law.