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
  1. Universal Identity Layer
  2. How it works?

Specifications

Fetcch's Identity Layer offers a Unified Address System that merges numerous blockchain addresses into a singular, chain-agnostic identity. By using easily recognizable identifiers like "satyam@metamask", users can effortlessly represent their identities across multiple platforms like Ethereum, Polygon, Solana, and BSC. With a staunch commitment to universal protocols, Fetcch Identities seamlessly integrate with the DID (Decentralized Identifier) standard, ensuring broad recognition and interactivity. Above all, emphasizing user-centricity, Fetcch guarantees full ownership through its non-custodial framework.

Let’s take a closer look on the Idenitifiers:

Identity Structure

Fetcch Identity's construct revolves around three core components:

  • Identifier: Essentially, it's the unique tag picked by users, like "satyam" in "satyam@metamask".

  • Delimiter: Represented by "@", it acts as a bridge between the identifier and the provider.

  • Provider: Refers to the specific blockchain or platform linked with the user, say "metamask" in the provided example.

Address Framework

With Fetcch Identity, users can tie multiple addresses, segmented into:

  • Default: The go-to address for all activities triggered by the user.

  • Secondary: Steps in as a backup, ensuring actions don't hit a roadblock when the default isn't usable.

Identity Configuration

Alongside the address setup, Fetcch Identity boasts an 'Identity Config', enhancing user flexibility:

  • Transaction Paths: Users can set preferred transaction routes. Take "forcedSameChainPayment" - if turned on, it sidesteps bridge routes, tapping into secondary addresses when needed.

  • Token Choice: For cross-chain transactions, the default pick is a stablecoin. Yet, users can tweak this based on their leanings.

In essence, these technical specs of Fetcch Identity are engineered for simplicity and efficiency, ensuring users navigate without a hitch.

PreviousHow it works?NextHow is it stored?

Last updated 1 year ago

🆔
❓
👮