How it works
Prove what was agreed. Enforce what must be agreed.
Two products on one record. Pick the one you need — each step is shown below, and every animation can be paused or stepped through.
01
Publish
The organization publishes an exact version. Its fingerprint goes on Solana.
02
Accept
The user reads that exact text and accepts with a passkey or a wallet.
03
Record
The signature over that version is recorded with a time — the evidence.
04
Verify
Anyone checks the receipt against Solana, without asking the company.
Stele Proof — how evidence is madeIllustration
Companypublishes v3
FingerprintSHA-256 on Solana
User acceptspasskey · wallet
Stele evidencesignature + time
Verificationby anyone, later
Terms of ServiceVersion 3
1/6The organization publishes Terms of Service, version 3.
Why it matters
A database flag can't say what was accepted. Evidence can.
The same acceptance, before and afterIllustration
Without Stele
acceptances ───────────── user_id: 284 accepted: true
With Stele
- DocumentTerms of Service — version 3
- FingerprintSHA-256 9f2c 41aa 07de 5b13…
- Signaturethe user's passkey or wallet
- TimestampSolana slot 312,448,901
- Receiptstele-receipt-….json
1/4Without Stele, the record of an agreement is a row in the company's own database.