AesirX Features: Residency Check

Jurisdiction-based access rules are increasingly common, but most residency checks still rely on IP detection, VPN heuristics, or centralized country databases. These methods are unreliable and introduce privacy risks for organizations. IP-based systems generate location logs that reveal where and when residency checks occur, and those logs can be linked across services over time. This quietly turns jurisdiction enforcement into location tracking and increases compliance exposure under data protection laws.

Zero-knowledge proofs alone do not solve this problem. While they limit what the verifier learns, they do not prevent issuer backchannels, wallet telemetry, SDK calls, or network metadata from exposing verification contexts. The real risk is not just the country attribute, but the system surrounding the proof.

AesirX CMP Residency Check addresses this by separating proof privacy from system privacy. Using Concordium ID, the residency predicate is proven locally inside the wallet. The website interacts only with AesirX CMP as a first-party component and receives a simple yes or no. No IP data, location logs, or identifiers are collected. Each result is bound to a domain-specific pseudonym, preventing cross-site linkability by design and allowing organizations to enforce jurisdiction rules without building surveillance infrastructure.