U2U Network Documentations
  • Introduction
    • Our Vision
    • Litepaper
      • Overview
        • U2U Network Diagram
        • U2U Network with DEPIN and Web3 Eco System
      • Consensus
  • Services
    • RPC
      • RPC Endpoints
      • Ethereum API Methods
        • eth_blockNumber
        • eth_call
        • eth_chainId
        • eth_estimateGas
        • eth_feeHistory
        • eth_gasPrice
        • eth_getBalance
        • eth_getBlockByHash
        • eth_getBlockByNumber
        • eth_getBlockTransactionCountByHash
        • eth_getBlockTransactionCountByNumber
        • eth_getCode
        • eth_getLogs
        • eth_getProof
        • eth_getStorageAt
        • eth_getTransactionByBlockHashAndIndex
        • eth_getTransactionByBlockNumberAndIndex
        • eth_getTransactionByHash
        • eth_getTransactionCount
        • eth_getTransactionReceipt
        • eth_getUncleByBlockHashAndIndex
        • eth_getUncleByBlockNumberAndIndex
        • eth_getUncleCountByBlockHash
        • eth_getUncleCountByBlockNumber
        • eth_maxPriorityFeePerGas
        • eth_sendRawTransaction
        • eth_subscribe
        • eth_unsubscribe
        • net_version
        • net_listening
        • net_peerCount
        • web3_clientVersion
        • web3_sha3
        • debug_traceTransaction
      • DAG API Methods
        • dag_getEvent
        • dag_getEventPayload
        • dag_getHeads
        • eth_currentEpoch
      • Trace API Methods
        • trace_block
        • trace_get
        • trace_transaction
        • trace_filter
    • Explorer
      • Explorer URLs
      • Explorer API
        • Account
        • Block
        • Contract
        • Logs
        • Stats
        • Token
        • Transaction
      • GraphQL
      • Explorer RPC API
      • Smart Contract Verification
        • Via explorer
        • Via hardhat plugin
      • Testnet Faucet
    • Wallets
      • Metamask
      • Wallet Connect
      • Coinbase Wallet
      • U2U Super App
        • Policy
    • Staking
      • How To Stake?
      • FAQ
    • The Graph
      • Deploy a Graph Node
      • Deploy a Subgraph
    • Bridge
      • Smart Contracts & EOA
    • Oracle
      • Smart Contracts & EOA
  • Network
    • Node Types
    • Requirements
    • Build Dependencies
    • Run Normal Node
      • Mainnet Normal Node
      • Testnet Normal Node
      • Run via Docker
    • Run Validator Node
      • Mainnet Validator Node
      • Testnet Validator Node
    • Run A Local Test Network
    • Troubleshooting
  • SUBNET
    • Overview
    • Subnet Node Type
    • Requirements
    • NFT Digital License
    • Subnet Node Setup
      • Master Node
      • Verifier Node
      • Edge Node CLI
  • For Developers
    • SDK
    • Smart Contract Development
      • What are smart contracts?
      • What is gas?
      • Structure of a smart contract
      • Your first smart contract
      • Test your smart contract
      • Deploy your smart contract
      • Submit your contract to explorer
      • Interact With Your Smart Contract
      • Integrate Your Smart Contract With a Frontend
      • Additional Resources
    • Smart Contract Deployment
      • Deploy with Remix
      • Deploy with Hardhat
Powered by GitBook
On this page
  • Master Node
  • Verifier Node
  • Edge Node (or Contributor Node)
  1. SUBNET

Subnet Node Type

There are two types of Subnet Nodes

Master Node

Master Nodes are integral components of the Subnet infrastructure, performing several critical functions:

Transaction Management:

  • Store all Subnet transactions

  • Validate all Subnet transactions

Data Availability Layer (DAL):

  • Serve as the DAL for all Subnet Decentralized Applications

  • Ensure data accessibility and integrity for the Subnet Ecosystem

Cross-Network Operations:

  • Submit and Verify proofs between the Subnet and Mainnet

  • Data Transmission between Subnet Protocols

Reward Structure: Master Nodes receive compensation for their services through:

  • A portion of Subnet transaction fees

  • Rewards for proof submission and verification between Subnet and Mainnet

By fulfilling these roles, Master Nodes contribute to the security, reliability, and interoperability of the Subnet network, while also maintaining a connection with the main blockchain.

Verifier Node

Verifier Nodes leverage the TEE (Trusted Execution Environment) and FHE (Fully Homomorphic Encryption) technologies, it plays a crucial role for checking quality of service foreach Subnet Protocol, validate data integrity and maintaining the privacy of user's data.

  • Data Versioning: Track changes in data and version control.

  • Cyclic Redundancy Check (CRC): Detect errors in data transmission.

  • Digital signatures: Use public key encryption to verify the origin and integrity of the data.

  • Hash functions: Use algorithms such as MD5, SHA-256 to create a unique fingerprint for the data.

Edge Node (or Contributor Node)

Edge Nodes are specialized components within the Subnet Ecosystem:

Roles: A node bound to specific protocols built on the Subnet Infrastructure

Resource Contribution: Edge Nodes can provide various computational resources to the Subnet, enhance the overall capacity and performance of the Subnet

  • RAM (Memory)

  • CPU (Processing power)

  • GPU (Graphics processing capabilities)

  • Storage (Data retention capacity)

  • Internet bandwidth

Reward Structure:

Edge Nodes earn reward based on their contributed DCU (Distributed Computational Units) both from Network layer and Protocol layer (dual tokens mining)

Protocol Specificity: Each Edge Node is associated with a particular protocol, allowing for specialized functions within the Subnet Ecosystem

By leveraging these Edge Nodes, the Subnet can distribute computational tasks and storage requirements across a network of contributors, potentially improving scalability, resilience, and performance of the overall system.

PreviousOverviewNextRequirements

Last updated 7 months ago