Tiered Identity Credential — anchored to did:sns
Attestto ID is a progressive identity credential that starts as a platform-verified record and can be upgraded to a fully self-sovereign, on-chain identity. It is anchored to a did:sns decentralized identifier and uses the vLEI Solana Bridge for on-chain attestation.
The credential follows a tiered model where each tier adds stronger guarantees without breaking backward compatibility:
The identity exists as a platform database record. Claims are KYC-verified and resolved through the Attestto platform. The holder is assigned a did:sns identifier but does not yet have on-chain presence.
| Property | Value |
|---|---|
| Storage | Platform database only |
| Proof resolution | Platform-mediated API |
| DID identifier | did:sns:<domain>.<user> |
| On-chain presence | None |
| Revocation | Platform-controlled |
Extends Tier 1 with a wallet attestation: an intermediate credential that proves the wallet belongs to the Attestto ID holder. Proof resolution remains platform-mediated, but the wallet binding adds cryptographic anchoring.
| Property | Value |
|---|---|
| Storage | Platform DB + wallet attestation |
| Proof resolution | Platform-mediated API |
| Wallet binding | Attestation PDA linking wallet to identity |
| On-chain presence | Attestation only (no token) |
| Revocation | Platform-controlled + attestation revocable |
Full self-sovereign identity. A non-transferable Soulbound Token (SBT) is minted on Solana via the vLEI Solana Bridge. Proofs are dual-key encrypted using 2-of-2 Shamir secret sharing, and access is consent-gated.
| Property | Value |
|---|---|
| Storage | On-chain SBT + encrypted vault |
| Proof resolution | Consent-gated, holder-controlled |
| Token | Token-2022 SBT (non-transferable, revocable) |
| Encryption | 2-of-2 Shamir: User Share A (Vault Extension) + Attestto Share B (PII Vault) |
| Revocation | W3C Bitstring Status List + on-chain revocation |
| Attestto dependency | Co-signer only (Share B) |
did:sns identifier remains the same across all tiers. The SNS data buffer flags (HAS_SBT, IS_TIER3) reflect the current tier on-chain.
Attestto ID credentials support per-field selective disclosure using SD-JWT (RFC 9449). Each attribute is individually salted and hashed, allowing the holder to reveal only the claims required by a verifier.
At Tier 3, proof payloads are encrypted with AES-256-GCM. The content encryption key (CEK) is split using 2-of-2 Shamir XOR:
Both shares must combine to reconstruct the CEK. Neither party can decrypt alone. Crypto-shredding (deleting Share B) renders all encrypted objects permanently inaccessible.
Share A is further protected with 2-of-3 Shamir recovery: device sub-share, cloud backup sub-share, and guardian sub-share. Any two of three can reconstruct Share A if the primary device is lost.
| Bit | Flag | Meaning |
|---|---|---|
0x01 | HAS_SAS | SAS attestation linked |
0x02 | HAS_SBT | Soulbound Token minted (Tier 3) |
0x04 | IS_TIER3 | Self-Sovereign ID tier active |
0x08 | HAS_LEI | LEI/vLEI credential linked |
0x10 | HAS_ECIES | ECIES encryption key published |
The Soulbound Token is minted via the vLEI Solana Bridge program using Solana Token-2022 with the non-transferable extension. The token:
A verifier resolves an Attestto ID through the following chain:
did:sns:<domain> via the DID ResolverHAS_SAS: follow the SAS UID to the attestation PDA, verify the issuer signatureHAS_SBT: verify the Token-2022 account exists, is non-transferable, and matches the attestation| Requirement | How Attestto ID addresses it |
|---|---|
| GDPR / Costa Rica Law 8968 (Protección de la Persona Frente al Tratamiento de sus Datos Personales) | No PII on-chain. Dual-key Shamir vault. Crypto-shredding for right-to-erasure. |
| FATF Travel Rule / ISO 20022 | SAS attestation provides issuer-signed identity proof for counterparty verification. |
| W3C DID v1.1 | Anchored to did:sns, a W3C-conformant DID method. |
| GLEIF vLEI | LEI hash stored in attestation. vLEI bridge provides on-chain LEI verification via ZKP. |