Skip to content
SIGNET
[ Docs ]

Short, because the
product is small.

There is one artifact to understand and four things you do with it. Read the format page and you can write your own verifier in an afternoon, in any language with a SHA-256 and a secp256k1 library.

Quickstart

open →

Seal something and check it, in about a minute, with or without a wallet.

Receipt format

open →

Every field, the canonical encoding, the signing rule, and how a run head is computed.

[ API ]

Two routes, both optional.

Everything on this site works without calling either one. They exist so a signature can come from a key you do not control, which is the only thing that makes a verifier interesting.

GET /api/notaryAsk whether this deployment holds a key, and which address it is.Live
POST /api/notarySend a digest, get back a signed receipt. The body carries no content.Live