did:sns Provisional

Alias-anchored DID Method for cross-border identity, privacy & compliance

Version 0.4.0 — Editor: Attestto — Author: Eduardo Chongkan (@chongkan) — 2026-03-12
Conformance: W3C Decentralized Identifiers (DIDs) v1.1

Alias-anchored identity. The did:sns method binds W3C Decentralized Identifiers to human-readable SNS domains (alice.crbank.sol). Web3 native, Web2 transparent — end users interact with readable aliases while the specification guarantees interoperability, privacy, and compliance across institutions, jurisdictions, and blockchains.

Field	Value
Method Name	`sns`
Status	Provisional
Verifiable Data Registry	Solana (SPL Name Service + SAS)
Specification Version	v0.4.0
Reference Implementation	`@attestto/did-sns-resolver`

Use Cases & Trust Model

1

What is did:sns — alias-anchored, Web3 native, Web2 transparent, chain-replicable

2

Focal Use Case, Identity Tiers & Requirements

Multi-issuer regulated identity — the scenario, trust model, Tier 1/2/3/Org, 13 requirements (R1–R13)

3

Trust Model & Hierarchy

Trust principles, Models A–D (institutional, platform, third-party, scammers), cross-domain trust, ecosystem trust anchoring & grading

4

Architectural Rationale

Why aliases over IBANs/SWIFT, SSL CA-inspired trust, identity/keys/transactions separation, ISO 20022, the Living DID

5

Privacy Architecture

7 privacy layers, correlation mitigations, regulatory compliance mapping (GDPR, FATF, CCPA, LGPD, etc.)

Standards Coverage

6

W3C Use Cases & Requirements Coverage

21/22 features covered — feature matrix, benefit alignment grid

Technical Specification

7

ABNF grammar, hierarchy depth, naming strategies

8

Examples (Tier 1/2, Tier 3, Root Domain), verification methods, service endpoints, controller hierarchy

9

CRUD Operations & Lifecycle

Create, Read (Resolve), Update, Deactivate, DID Lifecycle, Root Domains as Organizational DIDs

10

On-Chain Metadata Schema

160-byte v2 buffer layout, flags bitfield

11

SAS Integration (Proof Layer)

SNS↔SAS linking, attestation hierarchy, class key security model

12

Security Considerations

Post-quantum migration, vault key architecture, stateless resolution (no DID Log), schema migration

13

Interoperability

Universal Resolver, SD-JWT, Credo-TS, DIDComm v2, vLEI, DNS discovery

14

W3C, IETF, NIST, Solana, GLEIF, ISO standards

Resources

Implementation Report

186 tests across 4 services — W3C DID Core and DID Resolution conformance

Community Charter

Governance, versioning, contribution guide, and interoperability roadmap

Intellectual property statement — royalty-free commitment, no known patent claims

JSON-LD Context

spec.attestto.com/v1/sns.jsonld — persistent namespace for did:sns documents

W3C Registry Entry

sns.json — method metadata for the W3C DID Spec Registries

Cross-chain compatibility proposals, jurisdiction-specific compliance, community feedback