☁️
Zus Docs
  • About Züs
  • System
    • Providers and Services
      • Miner
      • Sharder
      • Blobber
      • Validator
      • Authorizer
      • Node Locator (0DNS)
    • Storage
      • Architecture and Data Management
      • Protocol
        • Allocations
        • Reference Objects
        • Challenges
        • Write Markers
          • Chain Hashing
          • Two Commit
        • Blobber Repair Protocol
      • ZS3 Server
        • Backup, Recovery and Replication
        • Encryption and Compression
        • S3FS Setup and Usage
        • Backup & Recovery with Restic on Blimp + ZS3 Server
        • Backup & Recovery with Veeam on Blimp + ZS3 Server
      • File Operations
        • Upload
        • Download
        • File Sharing
        • Partial Error Recovery
        • Streaming
        • Rent a Blobber
    • Smart Contracts
      • Storage S.C.
      • Miner S.C.
      • ZCN S.C.
      • ERC-20 S.C.s
      • Bridge Protocol
    • Blockchain & Consensus
      • Entities
    • User Authentication and Wallet Management System
      • OKTA Integration
      • Key Management System (KMS)
  • APIs
    • 0DNS API
    • JS API
    • Mobile API
  • CLIs
    • Storage CLI
      • Quickstart
      • Configuring the tool
    • Wallet CLI
      • Wallet Configuration
      • Quickstart
      • Configuring the tool
  • SDKs
    • Go SDK
      • GO SDK Microservices
    • JS SDK
  • Tokenomics
    • Staking
    • Reward & Penalty
  • ✨Züs Apps
    • 🗝️Vult
      • Getting Started
        • Web
        • Mobile
      • Vult AI
        • Batch Processing
        • Memory Retention
        • Technical Implementation
        • Architecture Overview
      • Login / Register
      • File Management Pages
      • File Sharing
      • Storage Management Dashboard
      • Storage Maintenance and Troubleshooting
      • Züs Subscription
      • Wallet Management
      • Refer a friend
      • Settings
    • 🏗️Blimp
      • Getting Started
      • Login / Register
      • Configure Storage
        • Create Standard Storage Allocation
        • Create Enterprise Allocation
        • Create S3 Server Allocation
        • Create Cloud Migration Allocation
        • Allocation Maintenance and Troubleshooting
      • File Management Pages
      • File Sharing
      • Manage Allocations
      • Upgrade Storage
      • Blimp Vault
      • Refer a friend
      • Settings
      • Launching ZS3 Server
      • Using CLI to backup files into Blimp + ZS3 Server
    • 🏠Chimney
      • Getting Started
      • Login / Register
      • Create New Deployment
      • Manage Your Deployments
      • Homepage
      • Staking Dashboard
      • Rank Dashboard
      • Monitor Dashboard
      • Stats Dashboard
      • Logs Dashboard
      • Wallet Dashboard
      • Operations on your Deployments
      • Restricted Blobbers
      • Settings
        • Manage Profile
        • Wallet Settings
        • Update Blobber Settings
        • Update Blobber Version
        • Refer a friend
        • Help
    • 🌐Atlus
      • Getting Started
      • Home page
      • Service Providers Page
      • Charts Page
        • Market Charts
        • Network Charts
        • Storage Charts
      • Blockchain Page
      • Server Map Page
      • Storage Explainer Page
      • Details Pages
        • Block Details Page
        • Transaction Details Page
        • Wallet Details Page
        • Miner Details Page
        • Sharder Details Page
        • Blobber Details Page
        • Validator Details Page
        • Authorizer Details Page
        • Allocation Details Page
      • Appendix: Common Components
    • ⚡Bolt
      • Getting Started
        • Web
        • Mobile
      • Login / Register
      • Sign In with external wallet
      • Staking Dashboard
      • Staking/Unstaking a provider
      • Claiming Rewards
      • Send/Receive ZCN tokens
      • Buy ZCN
      • Deposit/Withdraw ZCN tokens
      • Activity Dashboard
      • Refer a friend
      • Settings
  • Releases
    • Hardfork
Powered by GitBook
On this page
  • Economic Model
  • Storage Provider (Blobber) Rewards
  • Client Storage & Cost Model
  • Staking & Delegation
  • 5. Challenge Mechanism & Security
  • 6. Storage Provider Weight Calculation
  • Token Circulation & Demand

Tokenomics

The Züs Network is designed as a decentralized storage ecosystem that incentivizes both clients and storage providers (blobbers) through a token-based economy.

This document details the reward mechanisms, storage pricing models, staking dynamics, and overall economic structure governing the Züs Network.

Economic Model

The Züs Network employs a Proof of Stake (PoS) consensus mechanism, enabling blobbers to earn rewards by providing storage services and staking tokens. The economic model is structured around the following key elements:

  • Blobber Rewards: Based on data storage, retrieval, and staking capacity.

  • Client Costs: Determined by storage duration, read/write operations, and allocation selection.

  • Staking and Delegation: Allows third parties to stake on blobbers for a share of rewards.

  • Challenge Mechanism: Ensures data integrity through random validation.

Storage Provider (Blobber) Rewards

Blobbers earn revenue from multiple sources, ensuring that economic incentives align with storage performance and reliability.

Blobbers earn revenue from four sources:

  1. Proceeds from writes (V_write): Fees collected from clients for data storage.

  2. Proceeds from reads (V_read): Fees collected for data retrieval.

  3. Annual block rewards (V_block): Distributed rewards based on stake and service quality.

  4. Challenge validation rewards (V_validation): Earned by proving stored data integrity.

The total revenue for a blobber is calculated as:

V_blobber = V_write + V_read + V_block + V_validation

Blobbers with high performance, low failure rates, and competitive pricing receive higher rewards over time.

Client Storage & Cost Model

Clients interact with the Züs Network to store and retrieve data. The cost structure includes:

a. Allocations

When storing data, clients create an allocation by selecting N blobbers, where:

  • k blobbers store actual data.

  • m blobbers store parity for redundancy (Erasure Coding).

The higher the m/k ratio, the better the durability and availability.

b. Reading & Writing Costs

Clients pay upfront for storage and retrieval fees are calculated dynamically.

  • The write cost is prepaid for the storage duration (typically one year).

  • The read cost depends on blobbers' pricing models and the presence of free reads.

c. Write Pool & Read Pool

  • Write Pool: Clients deposit tokens upfront for write operations.

  • Read Pool: Clients deposit tokens if blobbers charge for reads.

  • Unused write pool tokens are returned at the end of the allocation period.

Staking & Delegation

The Züs Network allows delegation to blobbers. Delegators can stake tokens, and rewards are distributed proportionally. The service provider's total earnings are:

I_blobber = Commission + (Stake proportion × Total rewards)

a. Blobber Staking Model

Blobbers must stake tokens before providing storage. A higher stake means:

  • Better reputation

  • Higher rewards

  • More allocation requests from clients

b. Delegated Staking

Third-party users (delegators) can stake tokens on blobbers and earn a share of rewards.

Stake Lockup Period

  • Staked tokens remain locked until allocation expiration.

  • Delegators can withdraw unstaked tokens anytime.

5. Challenge Mechanism & Security

Blobbers are periodically challenged to prove they store data correctly. If they fail:

  • Challenge rewards are returned to the client.

  • A portion of the blobber’s stake is slashed and burned.

  • This ensures data reliability and discourages dishonest storage providers.

Challenge Success Rate= Total Challenges Issued / Valid Responses

6. Storage Provider Weight Calculation

Blobber rewards are based on read/write pricing and service quality. The weight formula:

Weight (w) = β × Stake (S)

Where β is influenced by:

  • Read price to write price ratio (p)

  • Data egress ratio (z)

  • Stake and performance history

Token Circulation & Demand

a. Demand Drivers

  • Storage Demand: Clients must lock tokens to store data.

  • Read Fees: Users pay for retrieving data.

  • Governance & Staking: Tokens are used for voting and securing the network.

b. Supply Control

  • Failing blobbers lose staked tokens, reducing circulation.

  • Token burns from slashing reduce supply over time.

c. Economic Balance

The Züs Network fosters competition where blobbers optimize pricing based on demand, leading to fair and stable storage costs.

Equilibrium Price = (Storage Demand / Storage Supply) x Base Price

where:

  • Storage Demand = Total active allocations

  • Storage Supply = Available capacity from blobbers

The Züs Network provides an incentive-driven, decentralized storage economy with competitive pricing, transparent rewards, and secure data integrity mechanisms. The tokenomics model ensures fair compensation for service providers while keeping storage affordable for users.

PreviousGO SDK MicroservicesNextStaking

Last updated 1 month ago