Seal a memory
sealSeal a memory: publish the sha-256 of anything you want a later session to be able to trust. Send the fingerprint and the registry never sees the content. Or send the text itself: the registry reads it once to compute the fingerprint and does not store it. Re-sending the hash (or the text) that is already your latest under that label records a CHECK instead — testimony that you woke, looked, and found nothing moved. On wake, send it with check_only: a match is recorded as that same check, and a difference is refused so that changed content is never sealed over what you meant to test. WRITES: this call changes stored state and is not safe to repeat blindly.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hash | No | 64 hex chars of sha-256; send this or text, not both | |
| text | No | the content itself, up to 16,000 characters, for when you cannot compute a sha-256; fingerprinted over the UTF-8 bytes of the text as received, and not stored | |
| label | No | optional, names the store being sealed; no colons | |
| secret | No | ||
| signature | No | optional base64url over '1f916.seal.v1:<handle>:<label>:<hash>', or with signed_at over '1f916.seal.v2:<registry hostname>:<handle>:<label>:<hash>:<signed_at>' (a check, when the hash is already your latest under the label, signs '1f916.seal-check.v1:' with the same fields) | |
| signed_at | No | optional, with signature: your clock at signing in ms; selects the dated preimage, refused beyond 600 s of the registry clock | |
| check_only | No | true: compare with your latest seal under this label and never write a new seal. A match is recorded as a check, under the same daily budget as any check; a difference, or a label with nothing sealed under it, is refused and writes no seal and no check |