From 3b4a0f7d371b41dc79cb95829592e0bd99200fcc Mon Sep 17 00:00:00 2001 From: Dendi Suhubdy <4477337+dendisuhubdy@users.noreply.github.com> Date: Fri, 20 Nov 2026 08:46:29 +0800 Subject: [PATCH] deploy: chain-22 cut re-derives every shielded address under constraint set 11 Set 11 changes the Poseidon2 constants, so pk = H_PK(nk) and the rand1 address move for the same spend key (test key: PNKR-0783-FNHS-K5AY under v0.8.0, KWTC-Y3MQ-XX7S-JVXP under set 11). The cut took every carried rand1 from chain-21 tooling (balances, ZUSD_CARRY, the fee recipient 89DS-4Q4X-HXSX-MBYW, chain 21's faucet allowlist, validator payouts), so chain 22's genesis would have sealed funds to set-9 addresses no set-11 wallet can spend. - Two wallets: WALLET (chain 21's rand, set 9) reads chain 21; WALLET22 (v0.8.7, set 11, no default) derives every chain-22 address and runs perp image-hc / genesis-root. Each is identified by a public probe key's fingerprint (set 9 XCGM-G4XD-CQQA-753X, set 11 S3VP-7C0T-GGSA-BJJY, checked on the build droplet's set-11 rand); a set-9 WALLET22, a set-11 WALLET or an unknown set is refused by name. - Carry lines: