Onboarding Web2 Data¶

What is the MPC-TLS + zkProof system?¶

Standard TLS is the mechanism behind all HTTPS websites. It encrypts network traffic so that only you and the server can decrypt what is sent and received. Multi-Party Computation Transport Layer Security (MPC-TLS) adds a third-party verifier to the TLS handshake. The verifier can check that the transmitted data is authentic without learning the data itself. The server is unaware of the MPC mechanism and needs no changes. Once the data is retrieved and its integrity verified, the user and verifier together produce a zero-knowledge proof that convinces the verifier of some fact about the encrypted data, which the verifier cannot see in plain text.

What does this mean for users?¶

Any user can self-attest to the validity of information loaded in their browser. For example, a user can self-attest their bank statement as a cryptographically secure proof of funds with one click.

What Sign Protocol brings¶

With a standardized attestation format and affordable permanent storage, Sign Protocol lets partners and users:

• Onboard MPC-TLS zero-knowledge proof validation results to any chain, and bridge results to any other chain after the initial attestation.
• Encrypt and permanently store the captured TLS session and zero-knowledge proof for archival purposes and future retrieval.
• Make validation results accessible to any smart contract, which can correctly decode and use them.

A sample schema from one of the partners:

{
  "name": "prototype",
  "data": [
    {
      "name": "ProofType",
      "type": "string"
    },
    {
      "name": "Source",
      "type": "string"
    },
    {
      "name": "Content",
      "type": "string"
    },
    {
      "name": "Condition",
      "type": "string"
    },
    {
      "name": "SourceUserIdHash",
      "type": "bytes32"
    },
    {
      "name": "Result",
      "type": "bool"
    },
    {
      "name": "Timestamp",
      "type": "uint64"
    },
    {
      "name": "UserIdHash",
      "type": "bytes32"
    }
  ]
}

Where can I experience this?¶

The launch partners are PADO and zkPass.

PADO¶

PADO, by PADO Labs, is a decentralized zkAttestation and Computation Network for Web3. Users attest off-chain data from internet sources in a privacy-preserving way: they generate attestations, or data proofs, from their private data and share them with third parties, such as dApps on blockchains, without revealing sensitive information. For example, users can prove gaming achievements or professional qualifications without exposing their account details. PADO Labs is developing the PADO extension for user data management, PADO developer toolkits for dApp creation, and node SDKs for the network, including cryptographic nodes for data authentication and evaluation.

zkPass¶

zkPass is a private data protocol for privacy-preserving verification, built on Multi-Party Computation (MPC), Zero-Knowledge Proofs (ZKP), and three-party Transport Layer Security (3P-TLS). Its TransGate lets users selectively and privately validate their data from any HTTPS website to web3. Supported data types include legal identity, financial records, healthcare information, social interactions, work experience, and education and skill certifications. None of these verifications require disclosing or uploading sensitive personal data to third parties.