GitHub account
Control of a stable GitHub account verified by Sigma.
The attestation
Control of a stable GitHub account verified by Sigma.
Sigma-owned schema issued only by Sigma Identity.
How Sigma Identity verified it
A fresh GitHub profile keyed by GitHub's immutable account ID.
Sigma validates the evidence immediately before signing. Field values are encrypted by your wallet; Sigma compares decrypted claims against current authoritative records and returns a signed BRC-52 certificate without receiving your private keys.
Encrypted certificate fields
| Field | Description | Type |
|---|---|---|
Account ID accountId | The provider's stable, immutable account identifier. | identifier |
Username userName | The provider username or handle at verification time. | string |
Profile URL profileUrl | The canonical profile page URL for the linked account. | url |
Profile photo profilePhoto | A URL to the provider profile image captured at verification. | url |
Verified at verifiedAt | ISO 8601 timestamp when Sigma last confirmed the evidence. | timestamp |
Selective disclosure
Certificates remain private in your wallet until you explicitly reveal fields to a named verifier. Applications request proofs through BRC-100; your wallet encrypts each field and returns a keyring only for the fields you approve.
Verifiers see only the fields you disclose. Other encrypted fields stay encrypted. Listing certificates in your wallet does not make them public.
Get this certificate in BSV Desktop
- 1
Import the Sigma trust manifest
In BSV Desktop, add Sigma Identity as a trusted certifier by importing https://auth.sigmaidentity.com/manifest.json and confirming the published public key.
- 2
Complete qualifying evidence
Sign in to Sigma Identity and satisfy the evidence requirement described above for this certificate type.
- 3
Acquire through your wallet
Request acquisition for GitHub account. Your wallet encrypts the field values, authenticates with Sigma over BRC-103/104, and stores the signed certificate locally.
Revocation and reissue
Every Sigma certificate includes a funded revocation outpoint once production issuance is enabled. A verifier that observes the outpoint spent must stop trusting the certificate immediately.
Revoking a certificate does not erase copies already disclosed to verifiers. Local relinquishment removes the certificate from your wallet only. Reissue requires fresh evidence and a new acquisition request when your evidence or account state changes.
Certifier and type reference
Sigma Identity public key
02250905f0383085b53409876aefbf01fc8e7fd841922dc4ce55ae035b31341e6d
Wallet credentials API
Read the certificates API reference for BRC-100 lifecycle, permissions, and endpoint details.
Wwu6i26Za++x25wQ1dbiMIsFMLSZdnmOQ8FlmFp61tc=