Four moves, one line
of text at the end.
Signet is small on purpose. It stamps, it signs, it chains, and it checks. Every surface below carries the state it is in. When every row reads green, a list has stopped carrying information.
11 surfaces · 9 running on this deployment today
Stamp
Hash it where it already is.
Your browser reads the bytes and computes a SHA-256 digest. The content stays in the tab that holds it, which is why no page here has a field for a prompt or a file. There is nothing to send, so nothing is sent.
Type into the box on the home page with the network panel open. The digest moves; the only request is a block height.
Sign
A key vouches for the digest.
Either your own wallet signs it or the notary key does. Both produce the same thing: an EIP-191 signature over the payload bytes, packed with the payload into one line that starts with sgn3.
Seal anything and read the line. Everything inside it decodes to text you can inspect.
Chain
Receipts fold into a run.
Each receipt carries the head of the one before it, and its own head folds that in. Change an earlier receipt and every head after it stops recomputing, which is the only mechanism doing any work here.
Seal two things, then recompute the chain on your ledger page.
Check
Recover, compare, decide.
The verifier recovers an address from the signature and compares it with the one the receipt names. Recovery on its own means nothing: feed random bytes to secp256k1 and an address falls out. Only the comparison earns a green result.
Change one character in a sealed line and watch the verifier refuse it.
Runs on your machine, with one branch that has to ask the chain.
One route, one key, no database.
On the list so the gap stays visible. Written in the future tense, because that is where it lives.
Works on this deployment right now. Open the page and use it.
The code is written and tested; the deployment has to supply a key before it does anything.
Nobody has built it. It sits on the list so the gap stays visible, written in the future tense.