Reference implementation · v0.1
Resolver Playground
Run the reference implementation rather than reading pseudocode. The browser imports the same protocol core used by the reference directory endpoint and verifies identity history locally.
One implementation core
Inspect every boundary.
The playground is intentionally transparent: inputs and derived JSON stay visible, protocol failures keep their error codes, and directory responses are verified instead of trusted. Start with the normative vector, mutate its history, then try the network resolver.
JCS, SHA-256, base58btc, Ed25519 verification, DID state derivation, and sq: parsing run directly through Web Crypto and the reference package.
This deployment serves the v0.1 normative identity through the specified /.well-known/sizuq/did/…/operations read profile.
The implementation is evidence and tooling, not a replacement for normative requirements. Divergence is a bug in the implementation.
Protocol package
@sizuq/protocol
The package currently lives in the protocol repository as a private v0.1 package while its external package namespace and public API stabilize. The site imports it through the package name already, so publication later does not require a second implementation.
import {
createDirectoryResolver,
parseSqUri,
resolveDidHistory,
} from "@sizuq/protocol";
const resolve = createDirectoryResolver({ endpoint: "https://sizuq.org" });
const result = await resolve("did:sizuq:z75o3Y...");Workbench
Run the protocol.
All four tools below use the reference package. No product account, sizuq.com database, or application session is involved in identity verification.
Normative vector
Recompute the v0.1 identity root and creation-record digest, verify the published Ed25519 signature, and derive the DID Document using the same package imported by this page.
Run the normative vector to verify the core implementation in this browser.Resolve operation history
Edit the JSON directly. Signature, genesis digest, sequence, predecessor hashes, key authority, and state transitions are checked locally; invalid histories fail closed.
Paste or edit an operation history, then resolve it locally.Parse sq:
Inspect scheme normalization, identity root, resource path, query, fragment, and the canonical primary identifier before any dereferencing occurs.
Parse an sq: URI without making a network request.Live directory resolution
Fetch the interoperable operation-array representation from a directory node, then independently verify it in the browser. Leave Directory endpoint empty to use this deployment’s reference node.
Resolve through the reference directory endpoint over HTTP, then verify locally.