Verification has a side. effect nobody talks about. every time a system confirms who you are, it also learns something. that you accessed this service at this time. That you hold this credential. that you were present in this context. over time, these verification events build a profile — not intentionally, but structurally. the system was never. designed not to track.
Sign Protocol's attestation framework is built. around a specific counter to this. unlinkability. is not a privacy policy. — it is a technical property. of the system. cross-context tracking of identity usage is prevented at the infrastructure level. using your attestation to access a government service. cannot be correlated with using it to access a financial service. the events happen, The verifications succeed, and no profile accumulates across them.
the attestation framework itself has five distinct capabilities. authorized entities — governments, institutions — issue cryptographic. attestations about any subject. multiple verification pathways confirm the authenticity and validity of those attestations. Revocation infrastructure removes attestations when necessary — an expired license, this fraudulent document, this changed status. expiration management handles time-bound attestations with automatic expiration, so the system does not carry stale. credentials indefinitely. and selective disclosure allows. partial disclosure of attestation content — only what the specific verification requires, nothing beyond it.
the cross-chain dimension is what separates. this from standard attestation systems. Sign Protocol attestations work across both blockchain. infrastructures inside the SIGN Stack. — the private Hyperledger Fabric. X CBDC system and the transparent public stablecoin chain. a single digital. identity attestation provides access to both. zero-knowledge proofs enable identity verification on the public chain without exposing the sensitive personal data stored on the private. CBDC infrastructure. and AML/CFT compliance runs. consistently across both environments. through the same attestation — so a government does not need separate compliance mechanisms for each system.
minimal disclosure. is the third layer. it is technically enforced — the system is designed to. request and transmit only what verification requires, not what would be. convenient to collect. this is not a setting that can be turned off. it is how the attestation layer is built.
what this produces is. a verification infrastructure where the act of being verified. does not become data about you. the credential confirms what it needs to confirm. the compliance check runs. the access is granted. and nothing about the event persists in a way that can be used to build a profile of your behavior across contexts.
most systems treat privacy as something added after verification works. Sign Protocol treats unlinkability as a design requirement that verification must work within.
if every verification. system was built this way — what would be different about how you interact with digital services today?