Zipwire Documentation
Visit Zipwire
  • πŸ‘‹Welcome to Zipwire
  • Overview
    • πŸ’‘What is it?
    • πŸ™‹β€β™€οΈWho can use it?
    • ✨Our Features
    • πŸš—Can I test drive it?
      • πŸ“¦Setting up Zipwire Approve
      • πŸ“₯Setting up Zipwire Collect
    • πŸ”‘Logins & Invitations
    • 🐒Zipwire Collect: Rapid Onboarding, Effortless Compliance
    • πŸ’ΎData Ownership in Zipwire
  • Zipwire Approve
    • πŸ…How Zipwire Approve is radically different and speeds up pay day
    • β›”Why we don't track start and end times
    • πŸ“¦Unboxing key concepts
      • πŸ“œAccounts
      • ⏲️Timesheets
      • πŸ‘·Senders
      • 🚦Approvers
      • πŸ‘‘Processors
      • ‡️Workflows
      • 🏷️Assignments
      • πŸ“Billing Plans
      • πŸ’±Rate Plans
      • πŸ“¬Teams & Inboxes
      • 🏒Workplaces
      • πŸ›‘οΈClients
      • ✍️The Journal
      • 🀸Activities
      • πŸ’ΈPayment Methods
    • πŸ”²Logical structure
    • πŸ› οΈSet up your workplace
    • πŸš₯Processing stages
    • πŸ’΅Understanding invoicing
    • 🏷️Using assignments
      • πŸ–οΈHoliday assignment
  • Zipwire Collect
    • πŸ—„οΈEffortless Document Collection for Any Need
    • 🟒Get Started
    • 😭IDSP, IDVT, KYC, KYB and AML
      • 🀳Selfie Checks Powered by Yoti
      • ⛓️Blockchain Attestations
    • πŸ“„Using Packs
    • πŸ€–Machine Vision
      • 🀷Failure to Recognise
      • πŸͺͺDocument Types
    • ✍️Manual Entry for Streamlined Information Gathering
    • ✨Creating a Collection with AI
    • πŸ‘€What the Respondent Sees at Their End
    • ♻️Lifecycle of a Collection
    • 🚚Bulk Upload
    • πŸ”Document Inspection
  • Fundamentals
    • πŸ›‘οΈSecurity
      • πŸ“²Authenticator mobile apps
      • πŸ”Two factor in Zipwire
      • Wallet Connections
      • Sign-in with Ethereum
      • Attestations
        • The "IsAHuman" Attestation: Purpose and Limitations
        • The "Private Data" Attestation: Merkle Roots
        • Zipwire’s Master Attester Wallet Address and Public Key
      • Wallet Verification Guide
        • Introduction to Sleeper Wallets and Blockchain Legends
        • How Sleeper Wallets Are Created
        • Verifying Attested Wallets
        • The Market for Selling and Buying Attested Wallets
        • Holistic Evaluation of Ethereum Wallets
        • The Future of Attestations and Wallet Verification
        • Verifying Zipwire’s Merkle Root Attestations for Developers
      • Understanding Merkle Trees and Proofs
  • Use Cases
    • 🎭Identity Checks - Right to Work
    • πŸͺͺCompliance - Know Your Customer
    • 🎨For Senders
      • πŸ’¬Sending journal updates via WhatsApp
      • πŸ€Έβ€β™‚οΈNaming activities
      • ✍️Tracking time in your Journal
      • ⏲️Send your first timesheet
    • πŸ“±Tracking time via WhatsApp
    • πŸ–₯️For Approvers
      • πŸ’¬Approving timesheets via WhatsApp
  • Troubleshooting
    • πŸ”€Tangled Identities
Powered by GitBook
On this page
  • Understanding Private Data Attestations
  • How It Works in Zipwire
  • Privacy in Action
  • Benefits
  • For You
  • For Platforms
  • Common Use Cases
  • How to Get Started
  • Technical Details
  • Learn More
  1. Fundamentals
  2. Security
  3. Attestations

The "Private Data" Attestation: Merkle Roots

This page explains how identity documents can be securely and privately checked and stamped on a blockchain and introduces the concept of a Merkle Root Hash.

Understanding Private Data Attestations

Think of it like this: When you get a document notarized, the notary doesn't keep a copy of your document. Instead, they create a unique seal or stamp that proves they saw the real document. The seal doesn't contain any of your personal information, but it proves the document was verified.

A Merkle root hash is like that seal, but even more secure. It's like a unique fingerprint of your document - but it's a one-way fingerprint. Just like you can't reconstruct a person from their fingerprint, you can't reconstruct your document from its hash.

The hash is only useful when paired with a special cryptographic proof document, otherwise it is just a random number. Proofs are generated when you want to prove a fact from the original document, allowing you to choose which specific data to reveal. It's like saying, "Here's my date of birth from my passport, and here's proof on the blockchain that Zipwire witnessed me with that very document."

How It Works in Zipwire

The Process

  1. Document Submission: You provide your identity document to Zipwire

  2. Verification: We verify the document's authenticity

  3. Hash Creation: We create a Merkle root hash (like a digital fingerprint) of your document

  4. Attestation: We attest to this hash on the blockchain

  5. Proof Generation: When needed, you can generate cryptographic proofs to verify specific attributes

Privacy in Action

When we attest to your document's hash on the blockchain, it's like the notary putting their seal on a record of your document's fingerprint. The blockchain only stores this fingerprint, not your actual document.Later, if you need to prove something about your document, you can use a special cryptographic proof. This is like having a receipt that shows your document matches the fingerprint that was attested to, without revealing the document itself. It's similar to how you might prove you own a house by showing a deed, without revealing your bank statements or other private information.

Benefits

For You

  • Complete Privacy: Your actual document never leaves your control

  • Selective Disclosure: Prove specific facts without revealing everything

  • Universal Verification: The attestation can be verified anywhere

  • No Repeated Checks: Avoid going through ID verification multiple times

For Platforms

  • Trusted Verification: Can verify your information without seeing it

  • Regulatory Compliance: Meet requirements while respecting privacy

  • Fraud Prevention: Cryptographic proofs ensure data hasn't been tampered with

Common Use Cases

Age Verification

Prove you're over 18 by revealing the date of birth from your passport, without revealing any of your other passport information

Nationality Verification

Confirm your nationality without sharing your full name or address

Professional Credentials

Verify qualifications without exposing personal details

Proof of income

Show your salary coming into your bank account without showing any other lines from the statement

How to Get Started

  1. Connect Your Wallet: Link your Ethereum wallet to Zipwire

  2. Submit Document: Provide your identity document for verification

  3. Wait for Verification: We'll verify your document

  4. Claim Attestation: Add the attestation to your wallet

  5. Generate Proofs: Create specific proofs when needed

Technical Details

For those interested in the technical aspects:

  • The Merkle root hash is created using a cryptographic hash function

  • The attestation is recorded on the Base blockchain

  • All attestations are viewable on EAS Scan on the Base blockchain

Learn More

PreviousThe "IsAHuman" Attestation: Purpose and LimitationsNextZipwire’s Master Attester Wallet Address and Public Key

Last updated 11 days ago

πŸ›‘οΈ
Understanding Merkle Trees and Proofs
Verifying Attested Wallets
EAS Explorer on Base