zkTLSProofs by Blind Witness

Gatekeeping, with math.

Bots and larpers are taking over the internet. Anti-Larp lets people into your site or chat only after they mathematically prove what they claim, from any website, without revealing anything else.

Example gates
Your gate
What visitors see Try the button

Some of the things people can prove. Pick one to try it in the gate.

Or seal a note.

Post the link anywhere. Only people who can prove they qualify will be able to read it. The note is encrypted on your device, the key travels inside the link, and our server only releases the locked copy after a valid proof.

Example note. Click to edit.

Opens for anyone who can
What your followers see

Nothing to fake.
Nothing to leak.

Anti-Larp runs on zkTLS. It turns the padlock in your browser into a proof anyone can check, so every website you can sign in to becomes a source of truth.

  1. 01

    The padlock already proves it

    Every HTTPS site proves to your browser that a page really came from it. That's what the padlock means. But the proof stays in your browser. You can't hand it to anyone else, and a screenshot proves nothing.

  2. 02

    A blind notary joins the connection

    With zkTLS, Blind Witness takes part in the encrypted connection, holding half of the session key. It never sees the page, and you can't alter what the site sent, because neither of you holds the whole key.

  3. 03

    Zero knowledge, one fact

    Your browser turns the notarized page into a zero-knowledge proof of one statement, like FACEIT level 10. Anyone can check it. Nobody sees the rest of the page.

  4. 04

    Any site is a source of truth

    No API, no partnership, no integration. If a site shows it to you when you're signed in, it can be proven.

Questions

Can't someone just fake it?

No. A proof is made from what the site actually sent over its encrypted connection, signed by the notary and tied to the site's own TLS certificate. Editing the page in your browser, a doctored screenshot or an AI‑generated image can't produce one.

What do I learn about the people I let in?

Only the claims you asked for, that they're true, and when they were checked. Not their username, their exact numbers or anything else on the page.

Does Anti-Larp or Blind Witness see anyone's data?

No. The Blind Witness notary holds only half of the session key and never sees the page. The visitor's browser builds the proof, and Anti-Larp only receives the claim.

Can a pass be shared or reused?

Not by anyone else. Visitors keep their proofs in their own extension and can use them at any gate, but every check starts with a fresh challenge from your gate that only their extension can answer, so copying someone else's proof doesn't work. Turn on One pass per account in the builder and one source account can't let in a crowd.

Which sites can people prove things from?

Any site they can open over HTTPS and sign in to. The site doesn't need an API, a partnership or to know it happened. The presets in the builder are a starting point; a custom proof is just a page and the field you care about.

What do visitors need?

The Anti-Larp browser extension. The first time it's a few clicks: prove, sign in to the source site as usual, done. The proof then stays in their extension, so the next gate that asks for it takes one click. Proofs are made in a desktop browser for now. In Discord and Telegram, the access they earn works on every device.

What happens if a source site changes?

Existing passes are unaffected, because a proof records what the page said at that moment. If a site redesigns, its preset gets updated.

Don’t take their word for it.

Put a gate on your site or chat, or get the extension and bring your own proofs.