Verify it
yourself.
Like a wax seal, tampering shows. INKAN’s seal is the maths version: change any sealed record and the check below fails... badge turns red. Run it in your browser. No need to take our word.
Every record is signed with an Ed25519 key over its exact canonical fields. Nothing leaves your browser. If our servers vanished tomorrow, the proof still holds.
Our public key is committed to a public GitHub repository and served as a static file... not handed out only by the app you’re looking at. Fetch it from a source we don’t control at request time, then verify. That closes the “what if the server lies about its own key” gap.
- Algorithm
- Ed25519
- Key id
- 10b13076b0bb3e4a
- Public key (hex)
- 47fa08cc910ee46bb06f595b489d4c2a24e1373086940fb8f47a6e7f96825261
This is the publichalf of INKAN’s key pair. The private seed that creates seals never leaves our server and is never published.
Verification runs entirely in your browser. Nothing is sent to INKAN.
Canonicalise
We re-serialise the record's fields to RFC 8785 canonical JSON. Key order and whitespace can't change the bytes... so the same record always hashes the same way.
Verify the signature
Ed25519 checks the seal against our published public key. Change one comma in the payload and the signature no longer matches... the badge goes red.
Confirm the key
Each seal carries a key id. The tool confirms the published key's fingerprint matches the one that signed the record, so nobody can swap in a different key.
The consent and licensing seal for talent and media.
Seal consent across your roster and licence likenesses to the brands you book.
Protect your roster →Brand?Hold a tamper-proof receipt for every likeness in your AI content.
Verify your licences →Regulator or solicitor?The full audit chain exports as JSONL and verifies without trusting our server.
See the audit chain →