Fetcch
  • 🟠What is Fetcch?
  • 🚅Pull Payments Layer
    • 🔭Overview
    • ❓How it works?
      • 👮Specification
      • 🎒How is it stored?
      • 🌊Pull Payments Flow
    • 🔐Security
      • 🎒Storage
      • ⛓️Cross Chain
    • ⚔️Use Pull Payments
  • 🆔Universal Identity Layer
    • 🔭Overview
    • ❓How it works?
      • 👮Specifications
      • 🎒How is it stored?
      • 🌊Identity Flow
    • 🔐Security
      • 🎒Storage
    • ⚔️Use Fetcch Identity
  • 🏗️Data Structures
    • 📖Address Books
      • 🔭Overview
      • 🎒Storage
  • 💻How to integrate?
    • ✈️Quickstart
    • ⛷️SDK Quickstart
    • 🔓Blockchain
    • ✨Guides
      • 🙇Authentication
      • 😁Identity
        • How to resolve identity?
        • How to create identity?
        • How to update identity?
      • 🤌Transaction Requests
        • How to get transaction requests?
        • How to create transaction request?
        • How to build transaction?
        • How to resolve transaction request?
      • 🫂Address Books
        • How to get address books?
        • How to create address books?
        • How to share address book?
        • How to accept address book request?
      • ⚙️Utility
        • How to sign messages?
          • EVM
          • Solana
          • Aptos
          • EIP-6492 Compatible Signatures
        • How to generate & verify proofs for identity?
    • 📖API Reference
      • ☢️Troubleshooting Errors
      • 🟢OpenAPI Specs
  • 🐧Open Source
    • 📸@fetcch/resolve-names
  • 🥶FAQs
    • FAQs
Powered by GitBook
On this page
  • Provider Workflow
  • User Workflow
  1. Universal Identity Layer
  2. How it works?

Identity Flow

Fetcch Identity Flow simplifies interactions for both DApps and wallets (providers) and users. For providers, it offers an uncomplicated pathway for setup, issuance, and management, while users experience a user-friendly journey for selection, registration, and utilization. Let's delve into these streamlined components for a clearer understanding.

Provider Workflow

  1. Seamless Registration:

    • Providers with verified wallets/dApps seamlessly onboard onto Fetcch.

    • Upon verification, they are granted a unique, alphanumeric namespace.

  2. Tailored Configuration:

    • Providers customize their namespace configurations, including API keys and owner addresses.

    • They craft a user-friendly frontend interface for efficient identity management.

  3. Empowered Identity Issuance:

    • Providers issue branded identities within their designated namespaces (e.g., username@namespace).

    • This process ensures distinct and recognizable user identities.

  4. Effortless Identity Management:

    • Providers effortlessly manage issued identities through chronologically validated owner signatures.

    • This guarantees the integrity and security of each identity's interactions.

User Workflow

  1. Informed Provider Selection:

    • Users make educated choices by evaluating providers based on reputation, chain compatibility, and rich feature sets.

  2. User-centric Identity Registration:

    • Users request personalized identities from their chosen provider.

    • The provider promptly issues bespoke identities nested under its unique namespace.

  3. Seamless Identity Engagement:

    • Users confidently engage with diverse identities from multiple providers.

    • The distinct namespace prefix simplifies the differentiation of identities, enhancing user experience.

PreviousHow is it stored?NextSecurity

Last updated 1 year ago

🆔
❓
🌊