Step 02

Mint the
proof.

zkTLS notarization proves you talked to GitHub — without REP ever seeing your password or token.

Connecting → Confirming → Sealing.

Notarize runs the moment you return from GitHub. If it fits the animation budget (~2 s), you never see a spinner — only named stages if it runs long.

Connecting

Prover opens a session with the notary at rep-notary.fly.dev (proxy mode, ~1–2 s).

Confirming

GraphQL POST to api.github.com with your bearer token — selective disclosure, not full export.

Sealing

Notary attests the TLS session. Claim saved: octocat · 1,247 contributions.

Hack 6 · notarize-in-animation

Proof, not exposure.

Expandable “What was proved” shows exactly which fields came back — contribution count, handle, source host. No surprise leaks.

✓ In the claim

GitHub username, contribution count, proof ID, notary public key reference.

✗ Never stored by REP

Password, email, private repos, raw GraphQL response bodies.

Share artifact

Hosted verifier page at flexrep.xyz/p/<id> — recipient verifies cryptographically.

Stack

TLSNotary prover (xcframework) + self-hosted notary allow-listing api.github.com.

Proof minted.

Snappy transition into success. Share button, expandable proof details, done — context list updates on next open.

Proof success
✓ Minted

octocat · 1,247 contributions

What was proved ▾ contributions, account, source: api.github.com
Share