sizuq protocol

1. What this proves

The protocol is exercised across real HTTPS boundaries, not only described in prose. A client can fetch a signed operation history, independently derive the DID state, discover a SizuqResourceService, and retrieve resources while preserving their canonical sq: identifiers.

The machine-readable evidence manifest is published at /.well-known/sizuq/protocol-evidence. The production network self-test is available at /api/reference/evidence/self-test.

2. Live identity

did:sizuq:zBNK1XN8HAhM1buSETkPJRV6dAhR98q27wkunKaqMVoT5

The creation record declares one Ed25519 Multikey verification method and a resource service at https://sizuq.org/api/reference/resource. Its complete signed history is available through the v0.1 directory read profile:

curl -H 'Accept: application/json' \
  'https://sizuq.org/.well-known/sizuq/did/zBNK1XN8HAhM1buSETkPJRV6dAhR98q27wkunKaqMVoT5/operations'

The same signed record and expected digest are downloadable as a machine-readable fixture.

3. Live resources

Canonical identifier	Current HTTPS delivery
`sq:zBNK1XN8HAhM1buSETkPJRV6dAhR98q27wkunKaqMVoT5/profile`	Profile fixture
`sq:zBNK1XN8HAhM1buSETkPJRV6dAhR98q27wkunKaqMVoT5/post/hello-world`	Post fixture

The HTTPS URLs are transport locations. The response body and Link: rel=canonical retain the corresponding sq: identifier.

4. Reproduce the resource request

curl \
  -H 'Accept: application/json' \
  -H 'Sizuq-Resource-URI: sq:zBNK1XN8HAhM1buSETkPJRV6dAhR98q27wkunKaqMVoT5/profile' \
  'https://sizuq.org/api/reference/resource/profile'

A conforming implementation should not trust this response merely because it came from sizuq.org. It first verifies the signed history from the directory endpoint, then uses the service endpoint derived from that verified state.

Implementation authors can also use the Resolver Playground and the conformance cases to exercise rotation, recovery, deactivation, malformed inputs, and parsing behavior.

5. Dependency-free independent resolver

A second resolver implements JCS, base58btc, SHA-256, Ed25519 Multikey verification, authorization, hash chaining, and state transitions in one public ES module. It has no runtime dependencies and imports no code from @sizuq/protocol.

Download the independent resolver · Download the reproducible runner · Read its machine-readable conformance report

6. Public lifecycle pilot

did:sizuq:zGjN5sTV97W2YUKUmpmH7Ap4qbHBZKRW3ceub3zaKHz52

This pilot is persisted in the public reference directory. Its ordered history contains create → update/rotation → recover → deactivate. Each successor is signed by the key authorized by the preceding verified state.

Fetch the live operation history · Compare the fixed lifecycle vector

The final resolution is intentionally deactivated: true, sequence 3, with no active DID Document. All pilot private keys were discarded after the four accepted records were published.

curl -O https://sizuq.org/implementations/sizuq-independent-resolver-v0.1.mjs
curl -O https://sizuq.org/implementations/run-sizuq-conformance-v0.1.mjs
node run-sizuq-conformance-v0.1.mjs

7. Limits and status

The immutable resource fixture and the deactivated lifecycle pilot serve different purposes. The first stays resolvable for dereferencing tests; the second proves historical rotation, recovery, and deactivation across the persistent public directory.

It is not a sizuq.com user identity, and sizuq.com does not yet mint DIDs or use sq: as a canonical product identifier.