Cryptographically verifiable

Sign a referral · H1 INTENT_SIGNED

US-005 · Send a Referral (referrer surface)

Handshake 1 of 4 · US-005
Send a referral

Sign an immutable, time-stamped, hash-chained record that you referred a specific person to a specific partner. This becomes the genesis event on a new causation chain.

Cryptographically signed · H1 INTENT_SIGNED
The Sign button below composes the canonical envelope (RFC 8785 JCS), signs it with the ECDSA P-256 private key stored in your browser's IndexedDB (never on the server), and posts to /chain/v1/*. The server verifies the signature against the SPKI PEM registered in device_keys — EA Rule 1 (court-defensible) fully discharged. If you haven't enrolled a key on this browser yet, go to /devices/enroll first.

Intent

What happens next

  1. The chain endpoint POST /chain/v1/h1 canonicalises this intent, hashes it, and (with a real device key) verifies your signature.
  2. A causation_receipts row is created with a short shareable code (e.g. A4Q9X2K).
  3. The referee gets an SMS deep-link to /verify/<code> (H2 acknowledgement).
  4. If they acknowledge, the partner is notified at /sign/partner/h3a/<code>.

This is a Provable Attribution receipt. Every event below is timestamped, locked, and independently witnessed each month — so no one (including us) can rewrite history.

View the chain →  ·  See the cryptography at work →

Matt's page