Phala Network Docs
  • Home
    • 👾Phala Network Docs
  • Overview
    • ⚖️Phala Network
      • 💎Phala Cloud
      • 🥷Dstack
      • 🔐GPU TEE
    • 💎PHA Token
      • 🪙Introduction
      • 👐Delegation
        • Delegate to StakePool
        • What is Vault
        • What is Share
        • WrappedBalances & W-PHA
        • Examples of Delegation
        • Use Phala App to Delegate
        • Estimate Your Reward
      • 🗳️Governance
        • Governance Mechanism
        • Join the Council
        • Voting for Councillors
        • Apply for Project Funding
        • Phala Treasury
        • Phala Governance
        • Setting Up an Account Identity
  • Phala Cloud
    • 🚀Getting Started
      • Create Your Phala Cloud Account
      • Your First CVM Deployment
      • Explore Templates
        • Launch an Eliza Agent
        • Start from Template
    • 🪨TEEs, Attestation & Zero Trust Security
      • Attestation
      • Security Architecture
    • 🥷Phala Cloud User Guides
      • Deploy and Manage CVMs
        • Deploy CVM with Docker Compose
        • Set Secure Environment Variables
        • Deploy Private Docker Image to CVM
        • Debugging and Analyzing Logs
          • Check Logs
          • Private Log Viewer
          • Debug Your Application
        • Application Scaling & Resource Management
        • Upgrade Application
        • Deployment Cheat Sheet
      • Building with TEE
        • Access Your Applications
        • Expose Service Port
        • Setting Up Custom Domain
        • Secure Access Database
        • Create Crypto Wallet
        • Generate Remote Attestation
      • Advanced Deployment Options
        • Deploy CVM with Phala Cloud CLI
        • Deploy CVM with Phala Cloud API
        • Setup a CI/CD Pipeline
    • 🚢Be Production Ready
      • CI/CD Automation
        • Setup a CI/CD Pipeline
      • Production Checklist
      • Troubleshooting Guide
      • Glossary
    • 🔒Use Cases
      • TEE with AI
      • TEE with FHE and MPC
      • TEE with ZK and ZKrollup
    • 📋References
      • Phala Cloud CLI Reference
        • phala
          • auth
          • cvms
          • docker
          • simulator
      • Phala Cloud API & SDKs
        • API Endpoints & Examples
        • SDKs and Integrations
      • Phala Cloud Pricing
    • ❓FAQs
  • Dstack
    • Overview
    • Getting Started
    • Hardware Requirements
    • Design Documents
      • Decentralized Root-of-Trust
      • Key Management Service
      • Zero Trust HTTPs (TLS)
    • Acknowledgement
    • ❓FAQs
  • LLM in GPU TEE
    • 👩‍💻Host LLM in GPU TEE
    • 🔐GPU TEE Inference API
    • 🏎️GPU TEE Benchmark
    • ❓FAQs
  • Tech Specs
    • ⛓️Blockchain
      • Blockchain Entities
      • Cluster of Workers
      • Secret Key Hierarchy
  • References
    • 🔐Setting Up a Wallet on Phala
      • Acquiring PHA
    • 🌉SubBridge
      • Cross-chain Transfer
      • Supported Assets
      • Asset Integration Guide
      • Technical Details
    • 👷Community Builders
    • 🤹Hackathon Guides
      • ETHGlobal Singapore
      • ETHGlobal San Francisco
      • ETHGlobal Bangkok
    • 🤯Advanced Topics
      • Cross Chain Solutions
      • System Contract and Drivers
      • Run Local Testnet
      • SideVM
    • 🆘Support
      • Available Phala Chains
      • Resource Limits
      • Transaction Costs
      • Compatibility Matrix
      • Block Explorers
      • Faucet
    • ⁉️FAQ
  • Compute Providers
    • 🙃Basic Info
      • Introduction
      • Gemini Tokenomics (Worker Rewards)
      • Budget balancer
      • Staking Mechanism
      • Requirements in Phala
      • Confidence Level & SGX Function
      • Rent Hardware
      • Error Summary
    • 🦿Run Workers on Phala
      • Solo Worker Deployment
      • PRBv3 Deployment
      • Using PRBv3 UI
      • PRB Worker Deployment
      • Switch Workers from Solo to PRB Mode
      • Headers-cache deployment
      • Archive node deployment
    • 🛡️Gatekeeper
      • Collator
      • Gatekeeper
  • Web Directory
    • Discord
    • GitHub
    • Twitter
    • YouTube
    • Forum
    • Medium
    • Telegram
Powered by GitBook
LogoLogo

Participate

  • Compute Providers
  • Node
  • Community
  • About Us

Resources

  • Technical Whitepaper
  • Token Economics
  • Docs
  • GitHub

More

  • Testnet
  • Explorer
  • Careers
  • Responsible Disclosure

COPYRIGHT © 2024 PHALA.LTD ALL RIGHTS RESERVED. May Phala be with you!

On this page
  • Why is Delegation needed?
  • Delegation Mechanism
  • Glossary
  • How It Works
  • Lifecycle
  • Rewards
  • How to choose a high-quality StakePool
  • Things to consider before delegating

Was this helpful?

Edit on GitHub
  1. Overview
  2. PHA Token
  3. Delegation

Delegate to StakePool

Why is Delegation needed?

Delegation is the name of the “Stake to Earn” mechanism on the Phala and Khala Network. Staking is currently enabled on both Phala Network and Khala Network.

  • Compute cannot simply be added to the network on its own. To ensure a secure and stable environment, “Proof of Stake” is used. Each worker on the network must be staked with some PHA, which is put at risk, in order to incentivize good behavior.

  • Compute providers and those wishing to provide stake do not have to be the same people. To improve flexibility and efficiency, Phala provides a delegation mechanism that allows delegators to stake to workers they do not control and earn rewards.

  • This mechanism is enabled by a feature we call the StakePool.

  • Overall Delegation incentivizes high-quality compute providers to generate consistent and reliable rewards for their delegators. This in turn ensures the stability of the compute provided.

  • For even more accessibility there is another major feature called Vault. This allows delegators to pass the management of their delegation to individual StakePools to someone else. These Vault operators, for a small fee, bring further efficiency to the ecosystem by driving delegations to the best compute providers. You can read more about Vault here.

Delegation Mechanism

Glossary

Meaning
Type

Delegator

Delegates PHA to StakePools or Vaults

On-chain Account

StakePool

Created and managed by the StakePool Owner. Delegators put PHA into these. Delegated tokens can only be used for staking.

On-chain Object

StakePool Owner

The account that controls the StakePool. Ownership is non-transferable.

On-chain Account

Worker

The StakePool Owner uses delegated funds to stake to a number of workers and therefore provide compute to the network. A worker can only belong to a single StakePool at any one time. The rewards generated will be distributed to the owner and the delegators based on the StakePool and Vault commissions. The mechanism is detailed below.

Physical Machine

Vault

Created and managed by the Vault Owner. Delegators put PHA into these. Delegated tokens can only be used for staking. The Vault Owner manages the delegations to specific StakePools, allowing delegation by proxy.

On-chain Object

Vault Owner

The account that controls the Vault. Ownership is non-transferable.

On-chain Account

How It Works

Lifecycle

1. Delegation

PHA holders delegate tokens into a StakePool or a Vault.

2. Vault distributes (Optional)

The owner of the Vault chooses high-quality StakePools to delegate to on behalf of their delegators.

3. Workers staked and started

The owners of individual StakePools use the delegations provided to stake and start workers and so provide computing power to the network. Over time stable and well-behaved Workers generate rewards.

4. Rewards distributed

Based on the StakePool’s commission rewards earned by Workers are distributed to the owner and the delegators. Owner rewards can be claimed into the owner’s account directly while Delegator rewards will automatically be reinvested into the StakePool. Those delegators using Vault pay a further commission for Vault’s management services.

Delegation represented as an NFT

After you delegate to a StakePool, your tokens will be transferred and locked. As proof of the delegation, you receive a Delegation NFT in return. The Delegation NFT records its owner, the StakePool where the delegation is located, and the share of the corresponding StakePool.

Your Delegation NFT is transferable, and you can also sell it to others on PhalaWorld’s NFT platform.

NOTE When your Delegation NFT is transferred or sold to someone else, the delegated PHA will no longer belong to you, because you have lost the certificate to withdraw it back from the corresponding StakePool or Vault.

Rewards

The moment you delegate, you immediately start to earn rewards.

The delegator rewards distributed each time will be automatically reinvested.

The APR of the pool which is shown on the Phala App is a real-time estimate. The APR calculation is based solely on the delegator’s income, after the pool owner’s commission has been taken.

How to choose a high-quality StakePool

You can find the historical data performance of the StakePool on the pool details page of the Phala App. The common methods for choosing the StakePools are:

  1. Check the historical APR trend performance of the StakePool. The historical APR of a high-quality StakePool must be stable enough.

  2. Check the number of workers in the StakePool, and check the status trend of the workers. Generally, the larger the StakePool, the better the operation and maintenance level of the pool owner, and the better the stability of the mining pool. Historical data will prove that.

  3. Take the initiative to contact the StakePool owner. Contact will be shown on the pool detailed page. The friendly pool owner will be happy to talk with you and guide you on how to delegate to his StakePool.

Note, please don’t be too obsessed with the Pool APR, there are often evil pool owners who only rely on lowering their commission to achieve a high APR, but this will not be sustainable, please be sure to observe the historical trend of APR!

After you have selected the pool and delegated, please also be sure to check the performance of the StakePool regularly. Contact the pool owner when the performance of the pool does not go well.

If you find these methods are too hard for you or you want to check constantly to see if your delegation continues to turn out well. Try to delegate to Vault.

Things to consider before delegating

This section is a short summary of some of the risks related to delegating PHA. Although delegation is non-custodial there are still situations that delegators should know about before committing to delegating to a StakePool or Vault.

  • At present, Slashing is not yet enabled on the Khala Network, however, it will be at some point in the future. For now, you can always get back as much PHA as you delegate. Once Slashing is enabled this will no longer be guaranteed.

  • It may take up to 14 days to withdraw your PHA from a Vault or StakePool.

  • The actual rewards obtained may not be as high as the APR shown at the time of delegation. Current performance does not predict future returns.

PreviousDelegationNextWhat is Vault

Last updated 10 months ago

Was this helpful?

All staked and started workers are rewarded for providing computing power. Every time rewards are distributed 20% goes to the treasury. The remaining 80% is distributed amongst the Vault Owners (optional), StakePool Owners, and delegators. Once the commissions are paid the rewards will be divided equally based on the number of delegations from each delegator. (Please refer to for specific reward details)

Vault is always a simpler and more friendly delegation method. Click to learn more about Vault.

💎
👐
Gemini Tokenomics
here