- we're rewriting some parts of TLSN Extension to make adding new mpc-tls verifications easier to debug and add.
- we're 90% there.
- next steps are to choose verifications schemas which are wide enough so that people can test it and also sybil-resistant proof.
- and we're ready to launch the MVP.
Some ideas for the mpc-tls schemas we currently have:
- at least one uber trip
- at least one Airbnb/Booking.com stay
- at least one device connected to an Apple ID
- completed Binance KYC
If anyone has ideas, please feel free to share here too!
> verifiable privacy via cryptography: MPC-TLS and ZKPs
> no government IDs (self-sovereign)
> no hardware (scalable over Internet)
> pluralistic identity (supports alt accounts)
We considered to launch a proof-of-human NFT. This would make UX and product much easier to integrate. But the problem with a global PoH NFT is that you force users to reuse the same address. This is obv bad for privacy.
So, for the MVP we're going to launch with prove that you're human and claim bring tokens to an address (can be a fresh address). This way each new claim will have unlinkable proofs if you use different addresses to claim.
If you're interested in diving in into low level details:
- With TLS Notary you can establish joint MPC-TLS connection with a target web server and users can selectively disclose and prove part of their web traffic (e.g. user account ownership with some relevant data). They have good docs - https://tlsnotary.org/docs/intro
- With Semaphore you can create zero knowledge proofs of inclusion (afaik this is similar to how Tornado Cash works). In our case, instead of concealing deposit and withdrawal link, we conceal web2 account and proof link -> you can prove that you have one of verified Twitter accounts without disclosing which one. They also have great docs - https://docs.semaphore.pse.dev/
Looking for feedback on the proposal for privacy-focused sybil resistance solution powered via MPC-TLS and Semaphore zero-knowledge group proofs - https://ethresear.ch/t/privacy-preserving-sybil-resistance-via-mpc-tls-and-semaphore-proofs/22722
1/ The Bring token was launched via @clanker on Base in Jan 2025. The goal was to experiment with token distribution and build out a zkTLS-powered airdrop platform.
Introducing technical design for proof of humanity based on online credentials, powered by MPC-TLS (based on @tlsnotary) for private web data authentication and Semaphore inclusion zero knowledge proofs for improved privacy.
More details in the draft paper https://github.com/BringID/whitepaper/blob/main/whitepaper.md
Some Bring updates:
- we're not releasing the early version we already developed because there are certain trust and privacy assumptions for a 3rd party zkTLS provider we're not comfortable with.
- after sharing a testnet version with early users, we discovered that idea of using zkTLS verifications as a proof-of-humanness resonates more than the idea of attracting non-crypto users with targeted airdrops
Some of the key learnings:
- crypto power users hesitant to install a 3rd party extension. Updating the design to add more info about why the extension is required for the zkTLS verification and why zkPass can be trusted (500k+ installs, audited & open-source code, backed by legit VCs, etc)
- less savvy users don't care that much about this issue (they mainly want to claim tokens)
- since we launched the testnet version Reddit has retired the API endpoint we were validating and the zkTLS verificatiion schema no longer works. To mitigate this issue in the future: a. we're adding a way to update the schema for existing drops. b. we will limit timeframe of the drop (e.g. 2 weeks) to lower the chance of API changes within this timeframe
zkBring demo: verify Uber account (at least one trip) and claim tokens.
airdrops for real humans, not bots:
> zkTLS verification via zkPass
> instant gasless onboarding with Coinbase Wallet
> token incentives to get onchain
With zkTLS, any data from any website can become airdrop criteria.
The screenshot shows our current airdrops live on Base Sepolia.
For Mainnet launch and our first zkTLS airdrop, we're designing criteria that:
- are difficult to Sybil
- are relevant to most users (at least one per person)
- showcase zkTLS's full potential
