Open protocol · Editor’s draft
Identity that moves.
Links that endure.
sizuq protocol is an experimental, implementation-oriented layer for portable identity and durable resource addressing across independent social applications.
The protocol is intentionally separate from the hosted product at sizuq.com. No single application is required to own a person’s identifier or the address of a resource.
Two layers
Small surface, clear roles.
The protocol begins with two identifiers. did:sizuq establishes cryptographic control. sq: addresses resources beneath that portable identity root.
did:sizuq
A self-certifying DID method with signed, hash-chained operations for creation, resolution, rotation, recovery, and deactivation.
Read method specification →Resource layersq:
A compact URI scheme that binds a durable resource path to a did:sizuq identity root without hard-coding a hosting provider.
Resolution
From a compact link to a verifiable controller.
A conforming client can resolve the identity root, verify its signed history, discover a declared resource service, and then dereference the resource. Alternative resolvers and mirrors remain possible.
sq:<root>/post/<id>
Read did:sizuq:<root> from a conforming directory or mirror.
Validate the signed operation chain and current DID Document.
Use the declared Sizuq resource service; never infer trust from the gateway alone.
Design principles
Protocol before platform.
Version 0.1 deliberately avoids social metrics, ranking, monetization, or application UI. Those are application concerns, not identity primitives.
Rotation and recovery keys are independent from any one app session or database account.
State changes are signed and chained so a resolver can audit how the current document was derived.
Identifiers are not designed to carry names, email addresses, demographics, or other personal data.
Registrations
Written for review, not just presentation.
The specifications expose stable headings, normative syntax, method operations, security and privacy considerations, and ready-to-copy registration material for the relevant registries.
Registry readiness
W3C DID Extensions checklist mapping, IANA RFC 7595 registration template, remaining pre-submission actions, and canonical specification URLs.
Open application workspace →