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
        • 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
  • Overview
  • What Is the "IsAHuman" Attestation?
  • Why It’s Flawed
  • Comparison to Robust Attestations
  • Why It Matters
  1. Fundamentals
  2. Security
  3. Attestations

The "IsAHuman" Attestation: Purpose and Limitations

PreviousAttestationsNextZipwire’s Master Attester Wallet Address and Public Key

Last updated 4 days ago

Overview

The "IsAHuman" attestation is a simple verification tool used in Ethereum wallets to indicate whether a wallet holder is likely a human, not a bot. Issued by services like Zipwire, it plays a role in enhancing trust in decentralized systems but has notable limitations due to its lack of detailed identity data. This page explores its functionality and flaws compared to more robust attestations.

What Is the "IsAHuman" Attestation?

The "IsAHuman" attestation is a boolean (true/false) claim added to an Ethereum wallet after a basic verification process, such as an ID check via Zipwire. For example:

  • A user submits an ID to Zipwire, which verifies it and issues the attestation to the user’s wallet address.

  • The attestation is recorded on the Base blockchain, viewable via EAS Scan .

Its simplicity makes it useful for quick checks, such as filtering bots in dApps or social platforms.

Why It’s Flawed

While "IsAHuman" helps combat bots, its minimal data makes it less reliable for establishing true identity:

  • No Identity Linkage: The boolean value (true) doesn’t tie to specific identity details, like a name or document number, so it can’t confirm who the human is.

  • Lack of Proof Mechanism: Unlike attestations with a Merkle root hash (e.g., for a passport), "IsAHuman" offers no way for the holder to present a Merkle proof to verify specific attributes securely. Learn more about Merkle proofs in .

  • Vulnerability to Transfer: If the wallet is sold or stolen, the attestation remains, potentially misleading others about the new holder’s identity.

Comparison to Robust Attestations

Contrast "IsAHuman" with an attestation of a passport:

  • Passport Attestation: Includes a Merkle root hash of document details (e.g., name, passport number). The holder can provide a Merkle proof to verify specific data without revealing everything, ensuring privacy and trust.

  • Stronger Verification: Such attestations link to verifiable identity data, making them harder to misuse.

Why It Matters

The "IsAHuman" attestation is a lightweight tool for initial trust but shouldn’t be relied upon alone. Platforms and users must combine it with other checks, like transaction history or additional attestations, to ensure a wallet’s legitimacy. For guidance, see .

🛡️
https://base.easscan.org/
Understanding Merkle Trees and Proofs
Verifying Attested Wallets