Sigma Auth publishes a certificate-type catalog and trust manifest today. The certificate acquisition and custody contract is implemented, but production issuance and revocation remain disabled until the readiness gate passes.
BRC-100: the standard certificate lifecycle
BRC-100 defines the wallet interface used to acquire, list, prove, and relinquish identity certificates. Sigma's implemented contract uses those standard wallet methods for BRC-52 certificates. It does not require a custom certificate store or a separate key-rotation scheme.
BRC-103 and BRC-104: authenticated HTTP
The implemented certificate flow authenticates wallet sessions with BRC-103 over BRC-104 transport. These standards protect the exchange; they do not replace Better Auth's ownership of user accounts, linked providers, sessions, or account lifecycle.
BRC-52: identity certificates
Sigma implements BRC-52 identity certificates and publishes conformance vectors for the standard wallet lifecycle. Production issuance and revocation are currently disabled, so this is an implemented contract rather than an available production feature. The live certificate-type catalog describes the supported claim fields.
BRC-68: live trust manifest
The auth service publishes its BRC-68 trust manifest at auth.sigmaidentity.com/manifest.json. A wallet can inspect the published certifier key and metadata before deciding whether to trust it.
Live certificate-type catalog
The public certificate-type catalog lists the exact types and fields in the implemented contract. It is a certificate-type catalog, not a directory of approved third-party certifiers.
Production readiness
The public certifier readiness endpoint is authoritative for activation state. It currently reports disabled. Do not present certificate issuance, revocation, billing, or wallet-specific interoperability as live until that endpoint and the release checklist say otherwise.
The catalog, manifest, and conformance vectors make independent testing possible. They do not by themselves prove interoperability with every wallet. If you run the standard lifecycle against another implementation, report both successes and failures through the contact page.