Issuer identity
You want people to know who sealed a page, not just that a seal exists. You do not need to run a webserver. You need three things:
- An Ed25519 keypair (private key stays offline)
- A public issuer document at a durable HTTPS URL
- That absolute URL in every signed claim as
issuer.key_url
Anyone can paste a house name in a bio. Identity is the key fingerprint, not the slug.
Microsites that mix hand-written pages with generated reference (HELIX's pattern) SHOULD use two keys in one issuer document (ADR-004):
| Role | What it seals | Where the private key lives |
|---|---|---|
| human | human-authored and mixed sources in git | 1Password or a local PEM. Never GitHub. |
| build | model-primary / generated: true sources | GitHub Actions secret INNSIGLE_BUILD_KEY |
The human key endorses the build key (innsigle endorse --subject-key-id … --purpose build-signing). The build key MUST NOT endorse the human key. A CI compromise then cannot mint a mixed seal.
Rendered HTML quotes the source attestation. The signature covers the markdown, not the HTML bytes.
Create keys
innsigle keygen --out-dir ./keys
innsigle keys template \
--issuer-id my-house \
--issuer-name "My House" \
--public-key "$(cat keys/ed25519.pub.raw.b64url)" \
--key-id "$(cat keys/key-id.txt)" \
--out issuer.json
Keep ed25519.priv.pem offline. Never put it in a gist, bio, or site tree. From a clone without install, use node src/cli.mjs instead of innsigle.
Publish the issuer document (no server admin)
Upload public issuer.json (or keys.json) somewhere HTTPS and stable:
| Option | How |
|---|---|
| GitHub Gist / raw file | Create gist → raw URL → use as key_url |
| GitHub / Codeberg Pages | Repo with issuer.json; Pages or raw link |
| Static free host | Neocities, Netlify Drop, Cloudflare Pages |
| Your existing site | Optional /.well-known/innsigle/issuer.json |
That HTTPS URL is what you pass to claim build --key-url …. It is frozen inside the signature. Changing the host later does not rewrite old seals.
Embed on social profiles
Profiles are for discovery, not crypto. Prefer a maker profile URL in the website / link field (plain seals, no keys required). If you also publish keys, you MAY add a short issuer card:
Innsigle · My House
key ed25519:56a6f2f799318d5153b3ba9b5e955d3b
keys https://gist.githubusercontent.com/you/…/raw/issuer.json
| Field | Put |
|---|---|
| Bio / about | Issuer card (fingerprint + keys URL) |
| Website / link | Same key_url (or shortlink that resolves to it) |
| Avatar-adjacent | Optional seal mark PNG |
Do not treat a bio as a seal. Anyone can paste someone else’s fingerprint. Verify seals with the CLI; pin fingerprints you care about.
Platform notes
| Platform | Pattern |
|---|---|
| X | Link field → keys URL; bio → key ed25519:… |
| GitHub | Profile README or pinned gist with full card + raw JSON |
| Bluesky / others | Website field → keys URL; description → fingerprint |
Seal content with your issuer
innsigle claim build \
--content ./page.html \
--colo ./colo.json \
--issuer-id my-house --issuer-name "My House" \
--key-id "$(cat keys/key-id.txt)" \
--key-url "https://…/issuer.json" \
--out claim.json
innsigle sign --claim claim.json --key keys/ed25519.priv.pem --out att.json
--key-url must be absolute https://… (relative paths are rejected).
Check it
What we claim: relative key URLs cannot enter a claim.
innsigle claim build \
--content ./page.html --colo ./colo.json \
--issuer-id my-house --issuer-name "My House" \
--key-id "$(cat keys/key-id.txt)" \
--key-url "/.well-known/innsigle/keys.json"
Expect: failure (exit 5), with a message about absolute key_url.
Trust and others’ keys
| Question | Answer |
|---|---|
| How do others trust me? | They pin your fingerprint, and/or follow key-endorsements (published statements that name another key’s fingerprint) |
| How do I verify them? | Content + attestation + their issuer document (key_url in the signed claim); innsigle verify |
| Duplicate house names? | Fine: identity is the key, not the slug |
Spec
Issuer URL and web of trust · Verify
Innsigle seal: mixed by Innsigle (human key)
Signature covers the markdown source of this page, not these HTML bytes. This render quotes that seal.
- Composition
- mixed
- Issuer
- Innsigle
innsigle - Signing key
ed25519:15c6242b6ef825413847e221267959c9(human key)- Signed source
docs/website/content/curated/use/issuer.md- Signed
- 2026-09-30T20:46:37Z
- Content digest
sha256:3761c5f0…9501e079
Human-controlled key. Signature is not a detector and not a truth guarantee.
Raw attestation JSON
{
"payload": {
"innsigle": "1",
"type": "https://innsigle.dev/claim/colophon/v1",
"issued_at": "2026-09-30T20:46:37Z",
"issuer": {
"id": "innsigle",
"name": "Innsigle",
"key_id": "ed25519:15c6242b6ef825413847e221267959c9",
"key_url": "https://documentdrivendx.github.io/innsigle/.well-known/innsigle/keys.json"
},
"subjects": [
{
"uri": "https://documentdrivendx.github.io/innsigle/use/issuer/",
"digest": {
"alg": "sha256",
"value": "3761c5f0d3c4cf750a203288ec34930410797c244c795503642e2b0e9501e079"
}
}
],
"colophon": {
"schema_version": "1",
"composition": "mixed",
"ingredients": [
{
"kind": "human",
"name": "operator",
"role": "outline"
},
{
"kind": "model",
"name": "Claude",
"role": "expand"
},
{
"kind": "human",
"name": "operator",
"role": "final-edit"
}
],
"notes": null
}
},
"payload_encoding": "json",
"signatures": [
{
"key_id": "ed25519:15c6242b6ef825413847e221267959c9",
"alg": "ed25519",
"sig": "4J2ZGEuSEbvORGy1MLbByXc9Nj5HB3JIkp1eoTDvI1WjopIgd7t54KEaqKpIQIZ7kheQD5oeLorFV8gvu0NpAA",
"signed_at": "2026-09-30T20:46:37Z"
}
]
}