If you lose your credential, recovering it will not expose your original identity. Zero-knowledge proof systems are designed with this in mind.
The worry about "identity exposure" actually has two layers: first, whether your original identity data (name, document number) can be seen; second, whether your wallet address can be linked back to your real identity. The first layer is already technically preventable. The second depends on how you perform the recovery.
Recovery does not expose your original identity — three layers of technical isolation
Layer 1: The original data is not on-chain
In a credential model like zkMe, after you complete KYC, you receive a verifiable credential (VC). It is stored in your wallet and is not put on-chain. The chain only stores a "commitment" — the root of an encrypted Merkle tree. This confirms that your credential exists during verification, but it does not contain any specific personal data.
Layer 2: Recovery verifies the "commitment," not the "data"
The recovery process proves two things: you have the right to recover this credential, and your credential really exists. The whole process only requires submitting a zero-knowledge proof and your new address to the chain. You do not need to show any original identity data.
Layer 3: Recovery exposes only the "proof," not the "content"
During recovery, you submit a Groth16 zero-knowledge proof file. After verification passes, the system allows you to update the address linked to the credential. The verifier can see that "this request is authorized to recover," but cannot see your name, document number, birthday, or other original data.
What recovery actually exposes
A few pieces of information are exposed:
- Your wallet address: The recovery request must come from the linked wallet, or you must specify a new address to receive the credential. Outsiders can see that "some address" made a recovery request.
- The recovery action itself: Recovery involves an on-chain transaction (updating the credential binding status). This transaction is publicly recorded on-chain.
- The credential nullifier: To prevent reuse, the old credential is marked as invalid. This marker is publicly visible.
But "knowing someone is recovering a credential" is different from "knowing who that person is." Your original identity data never goes on-chain, and it is not submitted or decrypted during recovery.
The only possible exposure scenario: manual review
Most zkKYC recovery processes are fully automated: submit proof → verify on-chain → recovery complete. But if you lose not only the credential file but also the private key of the linked wallet, some systems may require a manual review channel. In that case, customer service may ask you to resubmit your documents for identity comparison.
In this scenario, your original identity data is exposed to the platform's compliance team, rather than being verified through technical proof. So if this happens, you do need to accept that manual review will see your documents.
How to check
After recovery is complete, check the binding status in a credential management platform like zkMe. If the system says "credential recovered successfully" or "verification status updated," and your wallet address has been changed to the new address, the recovery process is finished. Also check the transaction hash of the recovery operation in on-chain transaction records. If the transaction status is "Success," the proof passed verification and recovery is complete.
