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
  • Login
  • Data configuration on PRBv3 UI
  • StakePool Configuration
  • Pool Operator Configuration
  • Worker Configuration
  • Start running
  • Status check

Was this helpful?

Edit on GitHub
  1. Compute Providers
  2. Run Workers on Phala

Using PRBv3 UI

You can configure StakePool, Pool operator, and worker information by using the PRBv3 UI, and can also check the running status of workers, and perform related error diagnosis there.

Login

Access the PRB UI by going to http://localhost:3000/. Replace localhost with the IP of the PRB Server.

If you are accessing this page from an external network, please note to check the firewall configuration of the PRB server.

Data configuration on PRBv3 UI

StakePool Configuration

Click Pools in Inventory to jump to the StakePool configuration interface.

  • Click Add button

  • Enter PID of the StakePool and your custom name for it

  • Click confirm

This completes the input of StakePool information.

Pool Operator Configuration

Click Pool Operators in Inventory to jump to the Operator configuration interface.

  • Click Set button.

  • Enter PID of the StakePool.

  • Select seed for Account Type.

  • If your operator account does not use the proxy method, enter the mnemonic of the operator in the Account section; leave Proxied Account (SS58) empty.

  • If your operator account uses the proxy method, enter the mnemonic of the authorized gas fee account in the Account section; enter the real pool operator’s account address in Proxied Account (SS58).

  • Click confirm.

This completes the input of Pool operator information.

Worker Configuration

Click Workers in Inventory to jump to the Worker configuration interface.

  • Click Add button

  • Enter your custom name for the Worker and the desired PID for the worker

  • Enter the worker’s endpoint in the format http://{pRuntime-ip}:8000/. Replace {pRuntime-ip} with the IP of the worker.

  • Enter the desired worker staking amount and add 12 zeros after the number. For example, 5000000000000000 means a staking value of 5000.

  • Click confirm

This completes the input of Worker information.

Similar to PRBv2, PRBv3 supports multi-mode worker synchronization.

If you choose the SyncOnly mode, the worker will only participate in synchronization and will not register worker’s information on chain after reaching the maximum height. There is a similar option in StakePool configuration page, and they are the same functions.

Additionally, PRBv3 has added GateKeeper mode, allowing you to deploy GateKeeper with PRBv3.

• The GateKeeper reward function as originally planned in the tokenomics is not yet enabled; Therefore, if you deploy GateKeeper, you will not receive any rewards. • GateKeeper cannot be added to StakePool for computation contributing. • After GateKeeper synchronization is completed, the operator needs to initiate an on-chain proposal and complete GK registration through community referendum before it can start running. The specific registration transaction is:phalaRegistry.registerGatekeeper(gatekeeper)

Start running

After all information is configured, click the reload button in the upper left corner of the page. The new configuration information will be loaded, and PRBv3 will start working.

Status check

Click Workers in Status to check the synchronization status of all workers and manage workers using the restart and re-register buttons.

Click Transactions in Status to check the transaction records sent by the PRB and confirm the details.

PreviousPRBv3 DeploymentNextPRB Worker Deployment

Last updated 1 year ago

Was this helpful?

🦿