Safle
  • SafleID
    • About SafleID
      • Core Technical Components (1/3)
      • Core Technical Concepts (2/3)
      • Core Technical Concepts (3/3)
    • What SafleID does?
    • For Chains
      • Technical Breakdown (1/2)
      • Technical Breakdown (2/2)
    • For dApps
    • For Wallet Providers (Exchanges and independent wallets)
      • Why Integrate SafleID (1/2)
      • Why Integrate SafleID (2/2)
    • SafleID's Technology
      • Data Flow and Interactions
      • Resolving Functionalities (RegistrarMain Contract)
      • Auction Functionalities (Auction Contract)
    • Conclusion
    • Terminology
    • Technical Documentation
  • Safle Wallet
    • Onboarding
    • Buy Crypto with Fiat enabled via Transak
    • Safle Swaps
    • Transaction processing on multiple Chains
    • Annexure: Encryption Sequence
  • Safle Vault
    • Features
    • Blockchains Supported
    • Installation & Initialisation
    • Encryption/Decryption Module
    • Controllers
Powered by GitBook
On this page
  1. SafleID

SafleID's Technology

Architecture

The architecture of SafleID is designed to provide a robust and decentralised naming infrastructure through the use of smart contracts. The system comprises two primary smart contracts:

Components:

  1. RegistrarMain: This contract serves as the main interface for user interactions. It manages user registrations, fee collection, and the overall registration and update processes. It is the entry point for all operations related to SafleID.

  2. RegistrarStorage: This contract acts as a decentralised data store, maintaining essential information about registrants, SafleIDs, and related data. It provides storage and retrieval services to the RegistrarMain contract, ensuring data integrity and security.

  3. Auction: This contract defines the functionalities for an auction system where users can auction their SafleID.

System Interaction Actors

  1. Admin

    • Responsibilities: The admin is responsible for deploying and maintaining the contracts. Key roles include setting registration fees for Registrars and SafleID users, as well as configuring the wallet address for fee collection.

    • Functions: The admin sets up the fee structures and ensures that the system runs smoothly by managing the deployment and maintenance of the contracts.

  2. Registrar

    • Definition: A Registrar can be any dApp or developer that wishes to integrate SafleID naming infrastructure into their application. By doing so, they can offer their users a streamlined onboarding process and improved user retention.

    • Functions:

      • addRegistrar: Registers themselves as a Registrar by paying a registration fee.

      • set/update SafleID: Associates or updates a user's SafleID with their public address.

      • mapCoins: Creates mappings for other coin addresses.

      • register/update Coin Address: Links or updates wallet addresses on other blockchains to SafleID.

  3. User

    • Definition: The end-users of a dApp who benefit from the SafleID naming infrastructure, enjoying simplified interactions and enhanced usability.

PreviousWhy Integrate SafleID (2/2)NextData Flow and Interactions

Last updated 10 months ago