Passport registry · v1

Every result, timestamped in public.

Passports are grouped into batches. Each batch is reduced to a single Merkle root, and that root is written to Solana as a memo. Anyone can then prove that a result existed at a given time, without trusting QAISS.

1 batch preparedNot anchored yet · anchoring key pendingNo token involved · fees in SOL

How it works

Passport → leaf → root → memo

The leaf hashes the fields that identify a result: workload hash, output hash, backend, shots, seed and noise. The root goes on-chain as qaiss:registry:v1:<root>:<count>. A memo creates no account, so the only cost is the base fee of 5,000 lamports.

01Passport
A Workload Passport from the Lab or a connector.
02Leaf
SHA-256 of 0x00 plus the canonical JSON of its identifying fields.
03Merkle root
Pairs are hashed as SHA-256 of 0x01 plus left plus right, up to a single root.
04Solana memo
Signed by the published anchoring key and visible on any explorer.

Batches

Published batches

BATCH 0001Prepared · not anchored4 passports · 2026-10-17

376b65912664132126a38bd5b3e6097073881d53668aa963e22ca8297c2706a1

Not on-chain yet. The project anchoring key has not been created; once it is, this batch is anchored with python -m qaiss_cuquantum registry anchor.

Leaf	Backend	Shots	Output hash
5414db88a574e7b0…	cpu.reference.fp64	2048	0f4333419a1da909…
049b91fd76035137…	cpu.reference.fp64	2048	61f7e8a04335409b…
8fe7ff61bc6e85b4…	cpu.reference.fp64	4096	9097b7eee36bfca0…
798d3334f14988b1…	cpu.reference.fp64	1000	dd1947c0eca8176a…

Check a passport

Is it in the registry?

Paste a passport. Your browser computes its leaf, finds it, rebuilds the Merkle proof and checks it against the root. For anchored batches it also reads the memo from Solana. Nothing is uploaded.

Make one in the Lab

Every result, timestamped in public.

Passport → leaf → root → memo

Published batches

Is it in the registry?

Engineering updates,not hype.

Engineering updates,
not hype.