Skip to content

fix: resolve WorldIDVerifier address from environment in proof commands#425

Merged
kilianglas merged 4 commits into
mainfrom
feat/verifier-address-from-environment
Jun 16, 2026
Merged

fix: resolve WorldIDVerifier address from environment in proof commands#425
kilianglas merged 4 commits into
mainfrom
feat/verifier-address-from-environment

Conversation

@kilianglas

@kilianglas kilianglas commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Summary

proof verify and proof test verified proofs on-chain against a single hardcoded WorldIDVerifier address (labeled "default: mainnet"). That address was actually the staging worldIDVerifier proxy.

This resolves the verifier address from the existing global --environment flag instead, via the shared resolve_environment helper that every other command already uses.

Changes

  • walletkit-cli only: per-environment WorldIDVerifier proxies hardcoded in proof.rs, selected by --environment:
    • staging: 0x703a6316c975DEabF30b637c155edD53e24657DB
    • production: 0x00000000009E00F9FE82CfeeBB4556686da094d7
  • proof verify/proof test default the verifier to the address for --environment; --verifier-address remains an optional override (also added to proof test for parity).
  • Addresses sourced from world-id-protocol contracts/deployments/core/{staging,production}.json.

Kept entirely in walletkit-cli (no walletkit-core change) so CLI-tooling addresses don't widen the uniffi / Kotlin / Swift binding surface.

@kilianglas kilianglas changed the title feat: resolve WorldIDVerifier address from environment in proof commands fix: resolve WorldIDVerifier address from environment in proof commands Jun 9, 2026
@kilianglas kilianglas merged commit ee9116e into main Jun 16, 2026
14 checks passed
@kilianglas kilianglas deleted the feat/verifier-address-from-environment branch June 16, 2026 19:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants