Worked example · production transaction 780301f2393e
A complete selection, from commitment to report
On 4 September 2026, EigenSelect submitted a two-outcome coin selection to the production service. Payment alone was bypassed with a reservation code. The commitment, physical execution, publication and delivery machinery was the same path used for a paid selection.
This transaction was operated by EigenSelect as a production smoke test and has been deliberately designated as a public example. Ordinary customer outcomes and reports remain private to the holder unless the holder chooses to share them.
The selection resolved to
Heads
Bitstring 0 · one shot · one physical execution · no rejected measurements
What happened
- The selection was fixedHeads and Tails were canonicalized as two outcomes. A manifest committed to the outcome set, state mapping, backend, one-shot rule, rejection policy and transpiled circuit.
- The commitment was publishedAt 2026-09-04T14:31:00Z, the manifest digest was published to the DNS proof zone and to public Nostr relays before the processor was contacted.
- The circuit ran onceThe job was submitted at 2026-09-04T14:31:03Z and completed at 2026-09-04T14:31:12Z on QPU-EMERALD-54PQ · IQM Crystal-54. The measured bitstring was 0, which decoded to the in-domain state 0.
- The resolution closed the chainHeads was resolved at 2026-09-04T14:31:13Z. The resolution digest was then published to DNS and Nostr, and the report was rendered from the verified evidence.
The record
| Transaction | 780301f2393e |
|---|---|
| Processor | QPU-EMERALD-54PQ · IQM Crystal-54 |
| Measurement | 0 → state 0 → Heads |
| Manifest digest | sha256:7486c43b688b0b6b5cba8869448653669cf6040ef9d6912c29ff42233e3758dc |
| Resolution digest | sha256:00cb547d00036dc9c6117447a47bc7f9133fef58cf933774897c776cc0ddecfb |
| Circuit digest | sha256:dc059c36453d7bea6041690a778013c2e70264dafb6e3552578fc31a5f9473a3 |
| Report digest | sha256:3e5e3842df100fee42ea92f579841c93e1f717b955d1033f8063fed77bb81b8f |
Reproduce the public chain
The first command reads the digest that was visible before execution. The next two hash the canonical manifest and exact QASM circuit served by the application. Their output must match the manifest and circuit digests above.
dig TXT pre.780301f2393e.eigenselect.eu +short
curl -s https://eigenselect.com/verify/780301f2393e/1/manifest.json | shasum -a 256
curl -s https://eigenselect.com/verify/780301f2393e/1/circuit.qasm | shasum -a 256
dig TXT post.780301f2393e.eigenselect.eu +short