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
  1. Introduction

Problem Statement

The creation of new blockchains is happening rapidly, resulting in numerous projects that aspire to be adopted by end users. Each blockchain tends to introduce its naming service, leading to fragmentation. This approach makes it progressively challenging for users to keep track of different services and interactions across various platforms since they are incompatible. In this scenario, a user has assets spread across multiple blockchains, each with its unique naming convention. To interact with decentralized applications (dApps), users have to manually copy and paste their wallet addresses, which increases the risk of errors and inefficiencies. However, each blockchain has its own solution to handle naming identity. In that case, it doesn't guarantee that they will work on another blockchain, or it could even lead to using a wrong identity name owned by someone else and their wallet address.

By introducing Rollups as a Service (RaaS), the process of naming services has become increasingly complex. With RaaS, developers can quickly deploy their rollup solutions, leading to an explosive growth of new rollup chains. Although these rollups offer scalability and cost-effectiveness, they add another layer of complexity to the naming service dilemma. This also creates additional friction when adopting new blockchains, which blockchain owners prefer to avoid to attract more users.

Rollups are solutions for scaling on layer 2 that bundle multiple transactions together, thereby reducing congestion and lowering transaction fees on the underlying blockchain.

PreviousWelcome to the SnowballNextVision and Mission

Last updated 5 months ago