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
  1. Core Concepts
  2. Tokenomics

Computing Provider Collateral

Introduction

In the Swan Chain network, Computing Providers (CPs) contribute their computational resources to support the network's decentralized computing infrastructure. To ensure stability and economic security, CPs are required to provide collateral in Swan tokens. This collateral acts as a financial commitment, incentivizing CPs to act in the best interest of the network while also sharing in the economic rewards generated from providing computing power.

Collateral Model

The collateral amount for each CP is determined by an inverse correlation model based on the total computing power contributed by the CP to the network. The formula for calculating the collateral amount is:

Cbase=CtotalCUtotal+bC_{base} = \frac{C_{total}}{CU_{total}} + b Cbase​=CUtotal​Ctotal​​+b
CUtotal=max⁡(∑kNECP(GPUk)×fk+∑kNFCP(GPUk)×fk∗WFCP,CU0)CU_{total} =\max ( \sum\limits_k N_{ECP}(GPU_k) \times f_k + \sum\limits_k N_{FCP}(GPU_k) \times f_k * W_{FCP}, CU_0)CUtotal​=max(k∑​NECP​(GPUk​)×fk​+k∑​NFCP​(GPUk​)×fk​∗WFCP​,CU0​)
{CU0=3000Ctotal=Circulating supply of SWAN×20% b=200\begin{cases}CU_0 = 3000 \\C_{total} = \text{Circulating supply of SWAN} \times 20\%  \\b=200\end{cases}⎩⎨⎧​CU0​=3000Ctotal​=Circulating supply of SWAN×20% b=200​

Where:

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

  • 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.

  • fkf_kfk​ represents the earnings growth factor

Currently, the computing units CUtotalCU_{\text{total}}CUtotal​ in the network are capped at (CU_0 = 3000). If the computing units remain at or below (3000), the base collateral remains constant at:

Cbase=10,000,0003000+200=3533C_{\text{base}} = \frac{10,000,000}{3000} + 200 = 3533Cbase​=300010,000,000​+200=3533

Example: If CUtotalCU_{\text{total}}CUtotal​ increases to 6000

  1. Substitute CUtotal CU_{\text{total}}CUtotal​ = 6000 into the formula:

Cbase=10,000,0006000+200C_{\text{base}} = \frac{10,000,000}{6000} + 200Cbase​=600010,000,000​+200
  1. Perform the calculation:

Cbase=1666.67+200=1866.67C_{\text{base}} = 1666.67 + 200 = 1866.67Cbase​=1666.67+200=1866.67

So, if the computing units (CU) exceed 3000, the base collateral amount will start to decrease. In the example where CU is 6000, the base collateral amount is 1867, which is lower than the 3533 calculated earlier when CU was 3000.

Revenue Sharing and APR Calculation

Once a CP provides collateral, they are eligible to receive revenue generated from both Universal Basic Income (UBI) tokens and paid jobs. The revenue model includes:

  1. UBI Income: CPs receive UBI tokens as a baseline income for their participation, which is inversely related to their collateral and computing power.

  2. Paid Job Income: CPs can earn additional revenue by completing paid jobs, which are offered at a market rate determined by user demand.

The Annual Percentage Rate (APR) for the CPs is calculated separately for both their operating revenue and collateral revenue:

  • Operator APR: The revenue generated by CPs for providing computing power divided by their total operational costs.

  • Collateral APR: Calculated based on the revenue earned by providing collateral relative to the collateral amount itself.

The total APR includes both the operator APR and collateral APR, providing a complete picture of the financial returns for CPs participating in the Swan Chain network.

Slashing Mechanism

To maintain network performance and accountability, CPs are subject to a precise slashing mechanism that penalizes inefficient or unreliable computing services. For each failed task, CPs face graduated penalties:

  • Edge Computing Providers (ECP) lose 0.025% of their current full collateral amount per failed task (approximately 0.88 SWAN for a 3080 GPU), with around 48 tasks processed daily.

  • Fog Computing Providers (FCP) lose 0.1% of their current full collateral amount per failed task (approximately 3.533 SWAN for a 3080 GPU), with around 14 tasks processed daily.

If a CP's collateral amount falls below the required threshold, they become ineligible to receive Universal Basic Income (UBI) tasks. To mitigate the risk of unexpected task exclusion, CPs are advised to maintain a buffer in their collateral amount.

Impact of Collateral Model

The negative correlation between collateral and computing power has several benefits:

  1. Incentivizing Scale: CPs are encouraged to scale up their contributions to the network, as increasing their computing power reduces their collateral requirements.

  2. Risk Mitigation: Collateral serves as a safeguard, ensuring that CPs have a financial stake in the network's success and discouraging malicious behavior.

  3. Economic Participation: By allowing CPs to share in both operator and collateral revenue, the model promotes balanced economic participation, where CPs are rewarded not only for their computational contributions but also for their financial commitment.

PreviousComputing Provider IncomeNextCollateral Requirement and Computing Unit

Last updated 5 months ago