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
  • Main Features
  • Compatibility and Application Extension
  1. Core Concepts
  2. Computing Layer

Computing Provider Protocol

Computing Provider Protocol Introduction

The CP Protocol (Computing Provider Protocol) is specifically designed for computing providers (CPs) in the Swan network, aiming to standardize and protocolize the management and invocation of computing resources. A CP can be any third-party individual or organization that provides scalable cloud computing, storage, platform, and application services for enterprises to access on demand.

Main Features

The CP Protocol is divided into two main categories: Standard Protocol and Extension Protocol. Each category is designed to meet specific business and technical needs and covers only the protocol layer. For specific code design, please refer to the corresponding SIP (Swan Improvement Proposal) document.

Standard Protocol

The core focus of the standard protocol is on standardizing the invocation and management of computing resources to ensure effective management. It includes the following key aspects:

  • Create job: Specifies the standardized process for deploying tasks on CP resources.

  • Query job details: Defines the protocol for accessing the execution status and relevant parameters of a task.

  • Renew job: Provides the standard procedure for task renewal.

  • Terminate job early: Sets the protocol standard for early termination of tasks.

  • Query CP resources: Describes how to query and select available computing resources.

Extension Protocol

The extension protocol focuses on enhancing the security, customizability, and flexibility of resources. Specific functions include:

  • Query CP resource pricing: Defines the standard method for querying CP resource pricing information.

  • Query CP whitelist: Specifies how to manage and query a list of specific users.

  • Query CP blacklist: Sets out how to maintain and query a blacklist to prevent malicious users from accessing resources.

  • Multi-chain payment verification mechanism: Describes the verification protocol for using multi-chain payment methods to invoke CP resources.

  • Universal collateral/withdrawal mechanism: Defines a standard protocol for a general collateral and withdrawal process to facilitate the access and management of market providers.

Compatibility and Application Extension

According to the design of the CP Protocol, any type of market provider (MP, Market Provider) can develop and design a computing engine that meets their needs based on this protocol. This flexibility ensures that the CP Protocol is not only applicable to current computing providers but also provides foundational support for various new types of computing service models that may emerge in the future.

By introducing the CP Protocol, the Swan network not only enhances the efficiency and security of resource management but also provides flexible configuration options to accommodate the needs of various business scenarios.

PreviousComputing LayerNextComputing Provider Account

Last updated 11 months ago