fix(release): transfer v3 and unshield v3 keys from a release ceremony (0.17.1)

[nol4lej]

Summary

Releases circuits 0.17.1: transfer v3 and unshield v3 keys from a release ceremony. 0.17.0 shipped keys from the development ceremony (default beacon, no public randomness) and must not be registered on-chain.

Only ceremony outputs change. Circuits, wasm, r1cs, and every v1, v2 and shield artifact are byte-identical to 0.17.0.

Ceremony

Powers of tau	pot16_final.ptau (Hermez), blake2b-512 verified against the published hash
Contribution	Single contributor, fresh random entropy (SETUP_CEREMONY=release)
Beacon	Orbinum testnet finalized block #1190708 0x63dca3b61d162679b1acad67bbd7276bfb235a40972792e377fe1ba62910f81f, 2^10 iterations
vk_hash transfer v3	0x04e05d74b320601fe1630ffa5b07c617117340c71d9f8d7b639a479f621a769a
vk_hash unshield v3	0x24fb6a97b53300b2cf2effa83547ac5a913c0b83f99788dd428ce54498f4e9f8

Anyone can check the beacon against the published zkeys:

npx snarkjs zkey verify build/transfer_v3.r1cs ptau/pot16_final.ptau keys/transfer_v3_pk.zkey | grep "Beacon generator"

It should print the block hash above, without 0x. Same for unshield_v3.

Changes

• package.json and manifest.json → 0.17.1.
• manifest.json: transfer v3 and unshield v3 get new zkey, vk_json, ark and vk_hash. Their wasm and r1cs are unchanged, and so is every other version and circuit.
• CHANGELOG.md:
  • new [0.17.1] entry with the ceremony record;
  • [0.17.0]'s keys marked as development-ceremony, superseded, do not register.

Test plan

• snarkjs zkey verify of both v3 zkeys against main's r1cs: ZKey Ok, beacon as above
• Manifest diff: only v3 ceremony outputs and package_version changed
• pnpm check (lint, typecheck, prettier, lint:circom with --inspect)
• pnpm test:strict: 307 passing
• pnpm release:verify: every manifest artifact matches the local files