Creating a proof

A proof session runs entirely in the side panel and a provider sign-in tab. Nothing is uploaded except the final cryptographic proof.

The steps

1. Launch. An integrated app opens the Keyring side panel, showing the app’s name and logo and the policy being verified.
2. Entity type. Choose whether the verification is for an individual or a business.
3. Data source. Pick a provider from the list available for the policy (see data sources).
4. Permission. Grant the extension access to that provider’s site for the duration of the session.
5. Sign in. The provider’s own sign-in page opens in a new tab. Sign in as usual; credentials are entered on the provider’s page, never in the extension.
6. Capture. While the provider session is active, the extension observes it and collects the specific fields the proof requires. This step is automatic.
7. Proving. The extension generates the proof locally. This typically takes between 30 seconds and two minutes; the side panel shows progress.
8. Verification. The proof is submitted to Keyring for verification and rule evaluation.
9. Completion. On success, the side panel confirms and the credential is issued for the connected wallet. The provider site access granted in step 4 is revoked automatically.

If something fails

Every failure in the flow offers a retry, and most causes are local (a VPN interfering with the session, a sign-in that timed out, or a provider account missing required information). The catalogue of errors and fixes is in troubleshooting.

After completion

The requesting app detects the result on its own; there is nothing to copy or paste. The wallet now passes the app’s compliance check until the credential expires, as described in credential lifecycle.