PowerPool
  • powerpool overview
    • PowerPool
      • PowerPool DAO Story
      • Value Proposition
      • Use Cases
      • CVP Token
      • Vision 2027
    • Blockchain Automation
      • Glossary
    • PowerAgent Stats
    • How to contribute
    • Contracts and Links
  • Power Agent
    • đŸŽ¯PowerAgent features
    • đŸ›ī¸Architecture
      • â„šī¸Agent
      • â„šī¸Keeper
      • â„šī¸Job
        • Full Specification
    • 📜User Guides and Instructions
      • ❓I Want to Automate my Tasks
        • Job Registration Guide
      • ❓I Want to Become a Keeper
    • â„šī¸Scenarios
    • ⌛Old Pages
      • Installation Guide (Old)
        • Prerequisites
        • DAppNode Installation
        • Registering in PowerAgent
        • Installing PowerAgent Package on DAppNode
        • Standalone Installation
        • Chain-specific configs
      • Keeper (Old)
        • Keeper Registration and Update
        • Keeper staking, withdrawal, and deactivation
          • Keeper activation and deactivation in PPAgentV2RANDAO
        • Keeper assignment and release in RanDAO realisation
      • Job (Old)
        • Job Registration & Update
        • Job funds deposition and withdrawal
      • Agent (old)
        • Page
        • Execution
      • Technical Implementation (Old)
        • Hooks and helper functions
        • Errors
        • Modifiers
          • Flags
      • Job Registration Guide (Old)
      • 📑Testnet Rules
      • Slashing
        • Copy of Slashing
      • Task Reward and Gas Compensation
        • Fees and income sources
        • Copy of Task Reward and Gas Compensation
  • PowerPool Incentives
    • PowerPool Points Program
  • Security
    • Bug Bounty
    • Security Audits
  • Research
    • Automation Networks Research
      • Approaches on Keeper Selection
      • On-chain Random Number Generation
      • Keeper Weighing
      • 🌊PowerPool & PowerAgent Automation Network
      • Value Proposition-PowerPool
    • PowerAgent v2.1
      • Keeper Selection
      • Hooks
  • Resources
    • Website
    • Twitter
    • Medium
    • Discord
    • Github
    • Telegram
    • Governance Voting
    • Governance Forum
  • Legacy & Deprecated
    • Index Products
      • $YLA: Yearn Lazy Ape
        • Invest (ZAP) in YLA with low fees
        • Instant YLA mint via USDC
        • $CVP Boost Program
        • Redeem YLA
        • YLA Onsen Liquidity Mining [deprecated]
      • $BSCDEFI: BSC DeFi Pool/Index
        • Guide: Mint $BSCDEFI with $BNB
        • Guide: Multi-Asset $BSCDEFI Mint
        • Guide: PancakeSwap LM Farming
        • Add $BSCDEFI to MetaMask.
        • Redeem $BSCDEFI
      • $ASSY: Aave, SushiSwap, Synthetix, and Yearn Index
        • $CVP Boost Program
        • Underlying Token Staking
      • $PIPT: PowerIndex Pool
      • $YETI: Yearn Ecosystem Index
      • Market Price vs Fair Value
      • About ZAP
    • CVP reward program
      • How to create a DCA flow in Partitura
Powered by GitBook
On this page
  • Overview
  • Specification
  • Keeper registration
  • Worker address update

Was this helpful?

  1. Power Agent
  2. Old Pages
  3. Keeper (Old)

Keeper Registration and Update

To participate in PowerAgent network, the user has to register their keeper worker address in the Agent contract.

PreviousKeeper (Old)NextKeeper staking, withdrawal, and deactivation

Last updated 2 years ago

Was this helpful?

Overview

⋅⋅⋅\cdot \cdot \cdot⋅⋅⋅

Specification

Keeper registration

The caller provides worker address (which is used in the off-chain keeper software configuration) and initial CVP deposit for stake.

Each new keeper is assigned an id (id of the previous registered keeper, incremented by 1, starting from 0).

function registerAsKeeper(
    
    //address of the keeper worker account
    address worker_,
    
    //initial CVP deposit amount to stake for this worker
    uint256 initialDepositAmount
    
    //returns id of the newly registered keeper
    ) public virtual returns (uint256 keeperId)
{
    //worker address is not already assigned to any registered keeper in the Agent contract
    _assertWorkerNotAssigned();
    
    //CVP is not less than the minimal allowed CVP stake
    _minKeeperCvpAssertion();
}

A single keeper address can have multiple workers assigned to the same Admin contract.

Once the registration is complete, the keeper is assumed to be up and running. It will start participating in the network as soon as the off-chain software is configured and launched.

Worker address update

Upon successful change of the worker address the function emits

event SetWorkerAddress(
    //id of the keeper for which the worker address was changed
    keeperId_,
    
    //previous worker address
    prev,
    
    //new worker address
    worker
)

If for any reason the keeper wants to change their worker address, a function is used.

The workerKeeperIds and keepers are updated accordingly.

⌛
setWorkerAddress
mappings