Haven1
  • Get started
    • 🧑‍🚀Welcome Havenauts!
    • 📄Haven1 Litepaper
    • 🧮H1 Tokenomics
  • Foundations of Haven1
    • 📐Architecture & network design
    • 🔐Network-level security
    • 📚Haven1 Core protocols
    • 💱Best in class liquidity
    • 👮Network Guardians: Firewall on Haven1
    • 🌉hBridge: Intro to Haven1 Bridge
  • Learn
    • 💵What does Haven1 solve?
    • 💡Haven1: Use Cases
    • 📚Understanding GoQuorum
    • 🔤Haven1 Blockchain basics
    • 🛂KYC policies on Haven1 blockchain
    • Security at Haven1
    • 🔓What is esH1?
    • ⚖️Dispute resolution mechanism
    • 🛣️Haven1 Roadmap
    • 🖥️Haven1 is EVM compatible
  • Products
    • 🔃hSwap - Spot DEX on Haven1
    • 📍hsETH on Haven1
    • Earn on Haven1
    • 🛡️2FA Wallet Shield
    • 🧊Haven1 block explorer
    • 🏛️Governance & veH1
    • 🆔hPassport - Key to Haven1
      • Advantages of having ID verification at a network level
      • Understanding the ID Verification Process
    • 💼Vesting esH1 - Converting esH1 to H1
    • 📍Staking H1 & esH1 - Earning rewards on your H1 holdings
      • Flexible Staking
      • Locked Staking
  • hPerpetuals - Perps DEX on Haven1
  • Haven1 Guides
    • 🔗Quick links
    • ✅Haven1 onboarding Guide
      • 🪪KYC Guide
      • Business KYC(KYB) Guide
    • Adding multiple wallets to a hPassport
    • 🌉Simple Bridging Guide on Haven1 network
    • 🏠Haven1 Portal - Your Gateway into Haven1
    • 🔑2FA Set up Guide
    • 🤑Haven1 Airdrop: Claim Process and Strategies
    • Claim Process Walkthrough on Team Finance
    • 📄Contract Addresses
  • Build
    • 📖Getting started
    • 🌐Haven1 Network information
    • 🍦Novel developer benefits on Haven1
    • 📑High level guide for secure deployment
    • ⚙️Detailed deployment Guide
    • 🧰Developer tools
      • 👛Haven1 Gnosis Safe wallet
      • 🛠️Haven1 SDK
        • 🔌@haven1/sdk-api-client
          • Class: Haven1SDK
          • Class: AuthModule
          • Class: SdkModule
        • ⛓️@haven1/blockchain-sdk
          • Contracts
        • 🧰@haven1/wagmi-sdk
          • Constant Module
            • Variable: haven1Devnet
            • Variable: haven1Testnet
            • Variable: H1
          • Contract Module
            • ProofOfIdentity
            • ProofOfIdentityV2
            • NativeAppFee
          • Utility Module
            • bigIntMax
            • formatBigint
            • bigintFromDecimals
          • Hook Module
            • useWatch
            • useBalance
            • useApproveERC20
            • useContractWrite
        • ⚛️@haven1/react-sdk
          • useHaven1SDK
          • useAuth
          • useIdentity
          • useNotifications
          • useOTP
          • useSignIn
        • 📜Use cases & Examples
          • Adding the Notification Component to Your React UI
          • Check Proof of Identity (POI) Status
      • Oracles on Haven1
      • Subgraph on Haven1
      • Haven1 block explorer
      • Web3 libraries and tools
    • Development frameworks
    • 🔐Using hPassport in Your dApps
      • Integrating hPassport into Your dApp
      • Implementing Identity Checks in Smart Contracts
        • Country codes
      • Sample Application - Country ID
      • Sample Application - Composable verification level
      • Sample Application - User type
      • Repository Information
    • ⛽Application fees
      • FeeContract.sol
      • Example FeeContract Interactions
      • Case Studies
    • 👷Builders grants program
  • Additional resources
    • 📚Haven1 terminology
  • Quick Links
    • Website
    • Twitter
    • Blog
    • Telegram
    • Customer Support
Powered by GitBook
On this page
  1. Products
  2. hPassport - Key to Haven1

Advantages of having ID verification at a network level

This page explains how Haven1 unique network design provides a safe and best in class user experience to users engaging on chain.

Grasping the difference between user verification conducted at the application level versus the comprehensive, network-level approach adopted by Haven1 is key to appreciating the robust value offered by hPassport.

The table below contrasts these approaches, highlighting the innovative approach adopted by Haven1.

Feature
Application/Protocol Level
Haven1 Network Level

Integration Complexity

  • Requires bespoke code

  • More challenging to change or update.

  • Simple universal SDK.

  • More flexibility in updating or changing the KYC process.

Universality of Standards

  • Multiple standards can co-exist, leading to fragmentation.

  • Different applications will have different levels of KYC/KYB scrutiny.

  • One standard for the entire network.

  • Ensures uniformity.

User Experience

  • Tedious: Users will need to undergo KYC processes for multiple applications separately.

  • Smooth: Once verified, users can interact with any application on the chain without re-verification.

Protection from Exploits

  • Protection varies by application.

  • Inconsistencies in defense mechanisms across apps.

  • Fragmentation in design enhances surface attack area

  • Centralized control offers a unified defense mechanism, but a flaw affects the entire network.

  • Rapid response possible for widespread issues.

Regulatory Compliance

  • Different applications will have varying levels of compliance, leading to regulatory risks for users.

  • Easier to enforce compliance across the entire network.

  • Attractive to institutional players.

Adoption Barriers

  • Allows for rapid growth as applications can choose to have laxer or stricter KYC norms.

  • Establishes a foundational trust layer by requiring upfront verification, which streamlines future interactions and enhances network security for all users.

Operational Costs

  • Costs are borne by individual applications

  • Cost borne by network

Audit and Oversight

  • Requires overseeing numerous applications individually, which could be resource-intensive.

  • Centralized oversight is more straightforward.

Privacy Concerns

  • Decentralized KYC approaches may offer varied privacy benefits but also introduce potential risks for data breaches across multiple points.

  • Centralizes user data within a secure, unified framework, using advanced encryption to protect privacy and minimize exposure.

Soulbond Tokens Security

  • Tailored security per application

  • Risks will be localized to specific applications, but inconsistencies in security measures across different applications can exist.

  • No recourse mechanic in the event of failure application failure

  • Standardized security ensures consistent protection.

  • Consistent level of protection against theft, duplication, or unauthorized transfers.

  • Network level recourse mechanic provides a failover solution

PrevioushPassport - Key to Haven1NextUnderstanding the ID Verification Process

Last updated 9 months ago

🆔