TL;DR

With zkTLS, DAOs can require members to hold attestations proving unique human identity across multiple Web2 platforms (X, Discord, Farcaster) without revealing usernames, handles, or follower counts. This stops Sybil attacks and vote farming while upholding strong privacy guarantees and zero centralized dependencies.

1  Problem Space

• Sybil voting plagues token‑weighted governance: whales split tokens across many wallets, while bots farm airdrops with disposable social accounts.
  
• Existing “Verified Twitter” or “Proof of Discord” plugins leak handles publicly and are easy to spoof because single‑source proofs are cheap to fabricate.
  
• DAOs need a multi‑dimensional identity check that is:
  
  1. Privacy‑preserving (no doxxing)
     
  2. Combinable (AND/OR logic across sources)
     
  3. On‑chain verifiable (no off‑chain oracle trust)
     

2  zkTLS Multi‑Source Social Proofs

zkTLS lets users generate independent zero‑knowledge attestations from each Web2 API endpoint. Orange Protocol’s registry can aggregate those attestations into a single “Uniqueness Composite” NFT that smart contracts can query with one call.

Example rule (DAO config):

Wallet must own ≥ 3 unique Orange Social Attests among {X‑followers > 10, Discord membership in ≥ 1 server, Farcaster account age ≥ 30 days}.

The proof logic lives in the client SDK; the DAO never handles raw social data.

3  Integration Architecture

graph 

    subgraph User Device

      A[Wallet\n+ zkTLS SDK]

    end

    A — ZK proofs –> B(Orange Attestation Registry)

    B — ERC721 Composite NFT –> C(DAO Governor Contract)

    C — vote() allowed? –> A

Composite NFT = ERC‑721 with tokenURI pointing to Merkle root of underlying attestations. Governor only sees the root + bitmask flags, never the private data.

4  Implementation Walkthrough

Integrating the zkTLS service provided by Orange is really simple which does not require importing an SDK. Developers simply install the Orange Pass Extension to access the methods needed for verification.

Install Orange Pass Extension from this link: https://chromewebstore.google.com/detail/orange-pass/belclhbabjnajafdinionmjhpnedbobi

After installing, you only need a few lines of code to initiate validation, including defining schema ID, recipient address, and other parameters. Orange Pass will automatically execute the validation program.

You can currently reach us via Discord (https://discord.com/invite/y5zFgm5MTs) to customize your Schema ID, eg. X, Discord, farcaster. In the future, we will launch a developer portal, enabling users to directly configure required templates, including data source URLs, APIs to call, verification conditions, and fields.

After verification, the Orange Notary backend will verify whether the attestation is officially released and return the result to the frontend.

More implementation details please view our doc: https://docs.orangeprotocol.io/developer-guides

5  Comparative Advantages

6  Risk & Mitigations

• Simultaneous Bot Farms → Raise threshold to 3‑of‑4 sources; include exchange KYC attestation layer.
  
• Proof Expiry → Require root timestamp < 90 days inside tokenURI.
  
• Revocation → Orange Registry supports revoker role; DAO can slash NFTs if fraud discovered.
  

7  Deploy in 15 Minutes

1. Upgrade governor contract with isHuman() modifier.
   
2. Airdrop mint gas to contributors.
   
3. Publish guide; add Connect Wallet & Prove widget (provided in Orange React kit).
   

8  Beyond Humans: Reputation Weighting

Future SDK releases will allow weighting votes by staked OHS and Delegated Social Score, enabling DAOs to move from one‑person‑one‑vote to proof‑of‑meritocracy — still privacy‑safe.