# identity-verified-v1: key ceremony transcript

Everything below is also in `circuit.json` (field `ceremony`). Times are UTC.

| | |
|---|---|
| Circuit | `identity-verified-v1` = zk-kit `equality_n` (equality, {"nonce":true}), 241 constraints |
| circuitId | `0xbbaa81fbe949e6bb2d04a67ab3d30af5dc8558122e51ec926160662bde545a0d` = keccak256("identity-verified-v1") |
| Public signals | `commitment`, `expected`, `nonce` |
| vkHash | `0xab173add5a694de0caa645ae6365a5001923253c4f72d178936dfb2855c3e41d` = keccak256(JCS(verification_key.json)) |
| ceremonyContributions (registry) | 1 |

## Phase 1: public Powers of Tau

The PSE Perpetual Powers of Tau (80 participants, closed with a pre-announced Ethereum randao
beacon), response 0080 prepared for phase 2 and truncated to 2^13.

| | |
|---|---|
| URL | https://pse-trusted-setup-ppot.s3.eu-central-1.amazonaws.com/pot28_0080/ppot_0080_13.ptau |
| Size | 9,530,514 bytes |
| blake2b-512 | `bf0c2d498f1197ad04ec0dbfcdda6df6348cbd793759f1f986e5cdf1a4100842293dfad6b8961f64b7ba35c162b5c821c4c097a52f3a639b55b0e765ec311b44` |
| sha256 | `ccee28086e4b81d81a6e16fdee054d1dbd5276362e2662d4205d31de45cb930f` |
| Header power | 2^13 (read from the file header) |
| S3 ETag | `bb54c403a93fabdabb99520b9fd94f56-2` (last modified Tue, 09 Apr 2024 07:06:01 GMT); multipart ETag recomputed with 8 MiB parts: matches |
| Downloaded | 2026-09-27T02:44:12.606Z |

PSE publishes no hash list for the prepared files, so the checks above are what could be made: the
header, the byte count, and the S3 multipart ETag recomputed from the bytes (a transport check, not
an authenticity check). snarkjs's full powers-of-tau verification was not run: it did not finish in
10 minutes even for the 2^8 file on the build machine. Download the file yourself and compare the
blake2b-512 before you rely on it.

## Phase 2

1. **Initial key** `_0000` = snarkjs `zkey new` of `identity-verified-v1.r1cs` on the phase-1 file. It is
   deterministic; anyone can recreate it (137,892 bytes, blake2b-512
   `11a3f3335fd1aa721f687c7fdc7f710bafc512a0d62796a70ed4450669fea574c7f992dd29f106f9e9213b8e6fbf3ab5fd94d5916a37a29d7d26dba15139bee4`).
2. **Contribution #1: Super Wallet (SeoulLabs) phase-2 contribution**, 2026-09-27T02:44:44.634Z to 2026-09-27T02:44:44.679Z.
   Contribution hash:

   ```
   1209c9cd423de7194d007c1d605fcf59e975de041b7f477ae0ea516d485ed52fe7ac22199c16969f053f285d20e494f2cda1c2310cac69503337f4a57a64cc32
   ```

   Entropy: 64 bytes from the operating system CSPRNG (`node:crypto` randomBytes), passed in
   memory to snarkjs, which mixes in its own random bytes. It was not written to disk, a log or a
   terminal, and the process has exited. All six production circuits were contributed in one run
   that finished at 2026-09-27T02:44:49.737Z.
3. **Beacon.** The rule, fixed in `zk-kit/scripts/production-ceremony.ts` before the run: after
   every contribution has finished, take the latest Xphere mainnet block whose timestamp is later
   than that moment, and apply its hash with 2^10 iterations (snarkjs `zkey beacon`).

   | | |
   |---|---|
   | Chain | Xphere mainnet, chain id 20250217 (read from https://en-hkg.x-phere.com) |
   | Block | 49677068 |
   | Block hash | `0x004d454b466cfbe88eedad46ef160b140124683eab1432b108a54b3111fac37a` |
   | Block time | 2026-09-27T02:44:58.000Z (fetched 2026-09-27T02:44:57.539Z) |
   | Iterations | 2^10 |
   | Beacon contribution hash | `c31c8729b1d238fd14d3f16cbdbc211ee2cd44704e054d869521f8ed8192fe03135634432fa11faddd27b61730743220e356e70ff9fcd49f8ec4519346be9a14` |

   Check the block: `curl -s -X POST -H 'content-type: application/json' --data '{"jsonrpc":"2.0","id":1,"method":"eth_getBlockByNumber","params":["0x2f6030c",false]}' https://en-hkg.x-phere.com`
   and compare `hash`, or open https://xp.tamsa.io/block/49677068.

## What this ceremony does and does not give you

A Groth16 phase 2 is sound if **at least one** contributor destroyed their randomness. This key has
**one** contributor, Super Wallet, so its soundness rests on Super Wallet having done so. The public
beacon makes the final key depend on a value nobody knew when the contribution was made, but it is
public and adds no secret: it does not replace a second, independent contributor. The block number
was not announced in advance; the rule for picking it was fixed in the script, and the block came
after the contribution. The registry records `ceremonyContributions = 1` as it is.

**An institution that wants to add its own contribution** takes `identity-verified-v1.zkey` (this key; the
contribution chain inside it continues), checks it with `zk-kit verify-ceremony`, runs
`zk-kit contribute`, and hands the result back; Super Wallet then applies a new, pre-announced
beacon with `zk-kit finalize`. The result is a new key and therefore a new circuit id,
`identity-verified-v2`, registered alongside this one with ceremonyContributions = 2. A
key is never swapped in under an existing circuit id.

## Result

| | |
|---|---|
| verifyFromR1cs (r1cs + phase-1 file + zkey) | OK |
| Circuit hash (snarkjs) | `9f9fb9ad5cfe775910003dafcbfc743c6d2d585d54d8417327bee1934b2dcbc382a29436fb07b9df171b4840ef2f7c177e557c492c5c72eead56ae7db41fedfd` |
| `identity-verified-v1.zkey` | 138,797 bytes, sha256 `f507b658eb2b583b29a67ede76d811fe92b55d7dbf3158fc924bfde460fa64e5`, blake2b-512 `cf18a1726a63fdfd4682cb942bc5f705f7a4fd89a30dae929b4983d355ab8c353530be5949e1731fcea20c2104a8f7c23bc86d4769d81433208c0a9326664289` |
| `identity-verified-v1.r1cs` | 114,512 bytes, sha256 `58b7b684e363dca1bc0ea4eef5c80e19674730cc48e65414a5076b6ea1696230` |
| `identity-verified-v1.wasm` | 1,748,699 bytes, sha256 `6e8160b3ef64f851fa4f574fbd4396f9e90e2457e7e51a289afdf65874f026d9` |
| vkHash | `0xab173add5a694de0caa645ae6365a5001923253c4f72d178936dfb2855c3e41d` |
| Verifier.sol runtime keccak256 (solc 0.8.24, optimizer 200, paris) | `0x8b5b21a8f328725191064aaa6cd4990e9157011b8d1b883df0c975db8ebffdf6` |

## Check it yourself

```sh
npm install /path/to/zk-kit          # or: npm install snarkjs@0.7.6 and use snarkjs directly
npx zk-kit ptau --power 13 --public --out ppot_0080_13.ptau   # compare blake2b512 above
npx zk-kit verify-ceremony --r1cs identity-verified-v1.r1cs --ptau ppot_0080_13.ptau --zkey identity-verified-v1.zkey
# prints: zkey VALID, then #1 Super Wallet (SeoulLabs) phase-2 contribution: 1209c9cd423de719...
#                             #2 Xphere mainnet block 49677068 beacon [beacon 004d454b466cfbe8..., 2^10 iterations]
```