Snowball
  • Welcome to the Snowball
  • Introduction
    • Problem Statement
    • Vision and Mission
    • Solution Overview
  • Modular Naming Service (MNS)
    • What is MNS?
    • MetaMask Snaps
      • Knowledge Base
      • FAQ
    • Identity Management System
      • Claiming Identity
      • Claiming Identity (ENS, SNS...)
      • Sub-identity
      • Primary Identity
      • Transferring Identity
      • Extending Identity Registration
      • Selling Identity
    • Identity Data Management
      • Record Type
        • Address Records
        • TXT Records
      • Records CRUD
    • Reputation Scoring System
      • For Users
      • For Projects
      • Data Sources & Inputs
    • Pricing
    • Use Cases
    • Roadmap
  • Programs & Gamification
    • Referral & Affiliate Systems
      • Affiliate Referral System
        • Terms and Conditions
        • How to Refer as an Affiliate
        • Affiliate Leaderboard Program
        • Eligibility & Requirements
        • Affiliate Tiers, Leaderboard Pools and Commissions
      • Referral System
        • How to Refer
        • Referral Leaderboard Program
        • Referral Tiers, Leaderboard Pools and Commissions
        • Terms & Conditions
      • Leaderboard & Monthly Rewards
      • Payoffs
    • Rewards & Gamification
      • What is Flakes?
      • Achievements
      • Daily Tasks
      • Repeatable tasks
      • Leaderboard
  • Decentralized Identity Layer
    • What is DiD Layer?
    • Cross-chain Interactions
    • Architecture
      • Reverse lookup
    • Tokenomics and Value Economics
      • Tokenomics
      • Value Economics
    • Why use dID on Rollup?
    • Deployments
    • Technical Documentation
      • Smart Contracts
        • RegistrarController
        • TransferController
        • PriceController
        • PublicResolver
        • SaleController
        • SnowRegistry
      • Events Documentation
      • Rest API
      • Typescript SDK
      • CAIP2
      • Reverse Lookup
  • About us
    • Team
Powered by GitBook
On this page
  • Managing Primary Identity
  • Clearing the Current Primary Identity
  • Setting a New Primary Identity
  1. Modular Naming Service (MNS)
  2. Identity Management System

Primary Identity

PreviousSub-identityNextTransferring Identity

Last updated 2 months ago

The MNS's Primary Identity feature enables users to set one identity as their primary representation on the blockchain.

  • By default, the first identity claimed is automatically set as Primary

  • At any given time, only one identity can hold the Primary status

Managing Primary Identity

Clearing the Current Primary Identity

1
2

Initiate Set as Primary Transaction

After selecting the identity they wish to set as the new Primary Identity, the user activates the "Menu" or chooses the "Set as Primary" option directly on the Identity page, indicating their desire to assign this identity as Primary.

3

Transaction Request Generation This selection initiates a new transaction request to the underlying smart contracts to update the Primary identity designation.

4

Transaction Signing The user must sign this transaction in the modal wallet window, confirming their intent to assign the selected identity as Primary. This step is essential for executing the changes on the blockchain and typically includes a gas fee.

5

Update Confirmation After the transaction processes, the smart contracts verify and update the records to reflect the new Primary Identity.

6

Blockchain Validation The updated Primary Identity can now be confirmed through blockchain explorers, where it displays as the active identity for all relevant transactions.


Setting a New Primary Identity

1
2

Initiate Clearing Primary Identity

By triggering the "Menu" button of the currently set Primary Identity or selecting the "Clear Primary" option on the Identity page, the user signals the intent to remove the Primary designation from the identity.

3

Transaction Request Generation The action generates a transaction request directed to the smart contracts responsible for managing identity attributes, requesting the revocation of the Primary status.

4

Transaction Signing The user must authenticate this request by signing the transaction in their connected wallet. This step is essential for executing the changes on the blockchain and typically includes a gas fee. The signed transaction is then sent to the blockchain for processing.

5

Confirmation of Action Upon successful execution, the smart contracts update the identity registry, confirming that there is currently no identity marked as Primary.

Access Identity Management Interface The user accesses the to interact with their claimed identities.

Access Identity Management Interface The user navigates to the to view their existing claimed identities.

My Identities page
My Identities page