LETHE

Verify

Don't trust us. Check.

Every check on this page runs in your browser, against keys anyone can fetch. Nothing here is sent back to LETHE.

The published key

Fetching the issuer directory…

A token from this browser

This browser holds no private tokens yet. Connect a wallet or buy a batch, then come back.

How a token stays unlinkable

  1. 1. Your browser makes a random nonce and blinds it. The issuer only ever sees the blinded value, which looks like noise.
  2. 2. LETHE signs the blinded value. This is the only step that knows who you are: your wallet or your x402 payment.
  3. 3. Your browser unblinds the signature. The result is a valid signature on a nonce LETHE has never seen, so when you spend it, nothing ties it back to step 2.

Standard Privacy Pass: RFC 9578 (token type 0x0002) over RFC 9474 Blind RSA.

From your terminal

# The one key every token is signed with
curl https://asklethe.ai/.well-known/private-token-issuer-directory

# Issuer info: key id, price, accepted networks
curl https://asklethe.ai/v1/tokens

If two people ever got different keys, tokens could be tagged per user. Compare yours with someone else's.

What this can't prove yet

These checks prove a token can't be linked to who paid for it. They can't prove what the server does with a prompt while it runs. That needs attested execution in a Trusted Execution Environment, which is on the roadmap. Until then, the prompt passes through a stateless proxy that doesn't store it.