Swan Chain
  • BULDERS
    • Getting Started
    • DApp Developer
      • Deploying Your First Smart Contract with Remix
      • Interacting with Smart Contract on Swan Chain Using Go
    • App Developer
      • Building Docker Images and Deployment file with LDL
        • Lagrange Definition Language(LDL)
      • Deploying with Swan SDK
      • Store and Retrieve a File with Swan Storage
        • 1. Set up the python-MCS-SDK
        • 2.Create and Manage Buckets
        • 3.Upload Files and Folders
        • 4.Retrieve and Download Files
        • 5.Delete Files and Buckets
    • Node Operator
      • Swan Node Snapshots
    • Market Provider
      • Storage Market
      • AI/ML Orchestrator
        • Decentralized AI Marketplace
        • Connect to Orchestrator
      • Web3 ZK Computing Market
        • ZK Auction Engine
        • Sequencer
        • Contribute zk-UBI-task
          • How to Contribute
        • Example
      • Customized Market Provider
    • Computing Provider
      • Fog Computing Provider(FCP)
        • FCP Setup
        • Migrating FCP to Swan Mainnet
        • FCP Funding Operations Guide
        • FCP FAQ
      • Edge Computing Provider (ECP)
        • ECP Setup
        • ECP Funding Operations Guide
        • ECP FAQ
      • FAQ
    • Storage Provider
      • Storage Auction System
    • Developer Tools
      • Swan SDK
        • Python Swan SDK
          • Special Case: Create ssh login instance
          • SWAN Orchestrator SDK - Function and Parameter Reference
        • Go Swan SDK
          • A Sample Tutorial
      • Swan Console
        • Getting Started
        • Blockchain GPU Task Example
        • Custom Blockchain GPU Task Pools
      • Lagrange
      • Swan IPFS Storage
      • Nebula Block Cloud
      • Ecosystem Projects
    • Mission 3.0
      • Get Started
        • For Users
        • For Space Holders
  • NETWORK REFERENCE
    • Network Info
      • Set Up Your Wallet
      • Bridge Token
    • Contract Addresses
    • Fees
  • Core Concepts
    • Introduction to Swan Chain
    • Consensus Layer
    • Peer-to-peer (P2P) Network
    • Payment Channels
    • Service Discovery
    • Market Provider
      • Storage Market
      • AI Computing Marketplace
        • Orchestrator
        • Auction Engine
        • Bidding Task State Machine
      • ZK Proof Marketplace
        • ZK Task
        • ZK Pool
    • Storage Layer
    • Computing Layer
      • Computing Provider Protocol
      • Computing Provider Account
      • Layer3 Computing Protocol
      • Reputation System
      • Dynamic Pricing
    • CDN Layer
    • Tokenomics
      • UBI Allocation Curve
      • Computing Provider Income
      • Computing Provider Collateral
        • Collateral Requirement and Computing Unit
        • DePIN Oracle
      • Governance
        • Treasure DAO
    • Glossary
  • Swan Chain Campaign
    • Swan CP UBI
    • Swan Chain Mainnet
      • Network Information
      • Swan Token
      • Swan Chain Mission
        • Social Mission
        • Onchain Mission
        • Mission: Celestial Bloom
      • Swan Provider Campaign
        • Fog Computing Provider (FCP)
        • Edge Computing Provider (ECP)
        • Market Provider (MP)
      • GALXE Campaign
      • Free Tier and Special Credit Programs
    • Atom Accelerator Race
      • Before You Get Started
        • Set Up MetaMask
        • Claim SepoliaETH
        • Claim testSWAN
      • CP Acceleration Program
      • Builder Acceleration Program
      • On-chain Interaction Race
      • Community Engagement Challenge
      • FAQ
    • Swan Saturn Testnet
      • Before You Get Started
        • Set Up MetaMask
        • Claim Faucet Tokens
        • Bridge Tokens
      • Transaction Drive Program
      • Community and Educational Events
      • Partnership and Integration Program
      • KOL Program
      • Computing Provider Program
        • FAQ
      • Developer Grant Program
      • FAQ
    • Swan Jupiter Testnet
      • How to Participate
      • Before You Get Started
      • Network Early Adopter
      • FAQ
  • RESOURCE
    • Links
    • Brand Kit
Powered by GitBook
On this page
  • Total Income
  • Individual CP's UBI
  • Conditions for CP to Receive UBI
  1. Core Concepts
  2. Tokenomics

Computing Provider Income

Swan Chain is a decentralized network that connects computing providers with users requiring computational resources. To foster early network growth and incentivize CPs to join and contribute resources, a dual compensation mechanism has been designed:

  1. Universal Basic Income (UBI): Provides CPs with a predictable token income when their resources are underutilized.

  2. Paid Jobs: Offers market-priced compensation for computational tasks requested by users.

This mechanism ensures a fair and gradual distribution of tokens to providers, supporting the network's expansion until it reaches a critical mass of user-paid tasks. Importantly, the UBI distribution rate is influenced by the resource usage rate, and CPs earn market-based compensation when engaged in paid jobs.

Total Income

The total daily income I(x) I(x) I(x)for a computing provider on day (x)( x )(x) comprises two components:

  • UBI Income yUBI(x)y_{\text{UBI}}(x)yUBI​(x)

  • Paid Job Income yPaid(x)y_{\text{Paid}}(x) yPaid​(x)

I(x)=yUBI(x)+yPaid(x)I(x) = y_{\text{UBI}}(x) + y_{\text{Paid}}(x)I(x)=yUBI​(x)+yPaid​(x)

Substituting the expressions for yUBI(x) y_{\text{UBI}}(x) yUBI​(x) and yPaid(x)y_{\text{Paid}}(x)yPaid​(x)

I(x)=A⋅xB⋅e−Cx⋅(1−u(x))+Pmarket(x)⋅u(x)I(x) = A \cdot x^{B} \cdot e^{-C x} \cdot (1 - u(x)) + P_{\text{market}}(x) \cdot u(x)I(x)=A⋅xB⋅e−Cx⋅(1−u(x))+Pmarket​(x)⋅u(x)

Resource Usage Rate Impact

  • When u(x)=0u(x) = 0u(x)=0:

    • CP receives full UBI allocation.

    • No income from paid jobs.

  • When u(x)=1u(x) = 1 u(x)=1:

    • All resources are utilized by paid jobs.

    • CP receives full income from paid jobs.

    • No UBI allocation.

  • Intermediate Values:

    • CP's income is a combination of UBI and paid job compensation, proportional to resource utilization.

Individual CP's UBI

To calculate the UBI for a single CP, we consider both the resource usage and completion rates of tasks. UBI allocation is conditional on sufficient resource contribution and performance metrics:

(1) UBI Workload Calculation

  • Calculate the daily completion rate of a single ECP zk-task: PECPP_{\text{ECP}}PECP​

  • Calculate the completion rate of a single FCP sampling task: PFCPP_{\text{FCP}}PFCP​

  • Number of GPUs: NECP(GPUk)N_{\text{ECP}}(GPU_k)NECP​(GPUk​) and GPU types.

  • Calculate the total UBI workload:

UBItotal=UBIECP+UBIFCPUBI_{\text{total}} = UBI_{\text{ECP}} + UBI_{\text{FCP}}UBItotal​=UBIECP​+UBIFCP​
UBIECP=∑i(∑kNECP,i(GPUk)×fk)UBI_{ECP}=\sum\limits_i (\sum\limits_k N_{ECP,i}(GPU_k) \times f_k)UBIECP​=i∑​(k∑​NECP,i​(GPUk​)×fk​)
UBIFCP=∑j(∑kNFCP,j(GPUk)×fk)∗WFCPUBI_{FCP}=\sum\limits_j (\sum\limits_k N_{FCP,j}(GPU_k) \times f_k) *W_{FCP}UBIFCP​=j∑​(k∑​NFCP,j​(GPUk​)×fk​)∗WFCP​

(2) Calculating the UBI for a single CP:

As an ECP:

UBIECP,i(x)=∑kNECP,i(GPUk)×fk×PECP,iUBIECP+UBIFCP×yUBI(x)UBI_{\text{ECP},i}(x) = \frac{\sum\limits_k N_{\text{ECP},i}(GPU_k) \times f_k \times P_{\text{ECP},i}}{UBI_{\text{ECP}} + UBI_{\text{FCP}}} \times y_{\text{UBI}}(x)UBIECP,i​(x)=UBIECP​+UBIFCP​k∑​NECP,i​(GPUk​)×fk​×PECP,i​​×yUBI​(x)

As an FCP:

UBIFCP,i(x)=∑kNFCP,i(GPUk)×fk×PFCP,i×WFCPUBIECP+UBIFCP×yUBI(x)UBI_{FCP,i}(x)= \frac{\sum\limits_k N_{FCP,i}(GPU_k) \times f_k \times P_{FCP,i} \times W_{FCP} }{UBI_{ECP}+UBI_{FCP}} \times y_{\text{UBI}}(x)UBIFCP,i​(x)=UBIECP​+UBIFCP​k∑​NFCP,i​(GPUk​)×fk​×PFCP,i​×WFCP​​×yUBI​(x)


Conditions for CP to Receive UBI

A CP must meet certain conditions to qualify for UBI:

  1. Sufficient Collateral:

CollateralECP=∑kNECP(GPUk)×Cbase×fkCollateral_{ECP}= \sum\limits_k N_{ECP}(GPU_k) \times C_{base} \times f_kCollateralECP​=k∑​NECP​(GPUk​)×Cbase​×fk​
CollateralFCP=∑kNFCP(GPUk)×Cbase×fk×WFCPCollateral_{FCP}= \sum\limits_k N_{FCP}(GPU_k) \times C_{base} \times f_k \times W_{FCP}CollateralFCP​=k∑​NFCP​(GPUk​)×Cbase​×fk​×WFCP​

Where:

  • NECP(GPUk)N_{ECP}(GPU_k)NECP​(GPUk​) represents the number of ECP for GPUkGPU_kGPUk​

  • NFCP(GPUk)N_{\text{FCP}}(\text{GPU}_k) NFCP​(GPUk​)represents the number of GPUk\text{GPU}_k GPUk​ in FCP

  • NECP(GPUk)N_{\text{ECP}}(\text{GPU}_k)NECP​(GPUk​) represents the number of GPUk \text{GPU}_k GPUk​ in ECP.

  • WFCPW_{FCP}WFCP​ represents the FCP resource bonus ratio, currently set at a constant value of 1.2

NOTE: The value of WFCPW_{FCP}WFCP​, 1.2, means that if the same configuration of servers is deployed for FCP, it will generate 20% more earnings than ECP.

  1. Completion of Basic Test Tasks:

  • FCP: Sampling task

  • ECP: ZK task

  1. GPU count and type are also factored into the UBI eligibility.

Exit Mechanism:

  • CP Exit Mechanism If a CP wishes to exit, they must set taskType = 100.

    • The CP will no longer receive any tasks and will not incur any collateral deductions.

  • CPs can request to withdraw their collateral, but this requires a 7-day confirmation period to ensure settlement before the withdrawal is finalized (first requestWithdraw, followed by confirmRequest after 7 days).

PreviousUBI Allocation CurveNextComputing Provider Collateral

Last updated 3 months ago

CbaseC_{\text{base}}Cbase​ is the base collateral, with an initial value of 3533 (this value will be dynamically adjusted based on the daily computing units of the entire network; for specific adjustment rules, check )

The CP will no longer appear on

here
the current dashboard list.