Geode Document Hub
  • Geode Document Hub
  • The Staking Library
    • πŸ”₯The Issue
    • 🧯A Solution
  • Operator Marketplace
    • 🟒A Validator's Lifecycle
    • πŸ”΅Maintenance Fee
    • 🟑Onboarding New Operators
    • πŸ”΄Regulating the Marketplace
      • 🚨Prison
  • Key Concepts
    • πŸͺ™Staking Derivatives
      • G-Derivatives
        • gETH vs gAVAX
    • πŸŒ€Portal
      • πŸ”Isolated Storage
      • 🀝Dual Governance
      • ⚠️Limited Upgradability
    • βš™οΈPermissionless Configurable Staking Pools
      • 🎭Current Interfaces
      • ⛏️Maintainers
    • πŸ›‘οΈWithdrawal Contracts
      • ⛑️Recovery Mode
      • πŸ•—Withdrawal Queue
    • 🌊Bound Liquidity Pools
    • πŸ”­Oracles
      • Telescope Ether
      • Telescope Avax
    • πŸ‘ΎFuture of Geode
      • Better Maintainers (WIP)
      • Synthetic Liquidity (WIP)
      • Dynamic Withdrawals (WIP)
      • Further Decentralization
        • Supporting EIP-4788 (DRAFT)
        • Quadratic Weighted Senate (DRAFT)
        • Degen Operators (DRAFT)
        • Decentralized Telescope (DRAFT)
      • Chain Sync (AVAX) (draft)
  • Ethereum Guides
    • πŸ“—Staking Pool HandBook
      • Initiating a Customizable Staking Pool
      • Managing Your Operator Set
      • Changing Your Pool's Owner
      • Manage Your Maintenance Fee
      • Private Pools and Whitelisting
      • Using a Bound Liquidity Pool
      • Using Maintainers for Your Pool
      • Securing Your Withdrawal Contract
      • Decentralizing Your Pool
    • πŸ“•Operator Handbook
      • Get Onboarded
      • Initiating an Operator
      • Communicating with Portal
      • Creating Validators
      • Changing an Operator's Owner
      • Switching Your Fee
      • Switching Your Validator Period
      • Using Maintainers
      • Optimizing Your Revenue
      • Exiting Validators
    • πŸ“˜Liquidity Pool HandBook
  • Avalanche Guides
    • Staking Pool Handbook
    • Operator Handbook
  • Developers
    • Networks
    • Live Contracts
      • Avalanche v1
      • Ethereum v2
        • gETH.sol
        • Portal.sol
          • globals.sol
          • DataStoreUtilsLib.sol
          • GeodeUtilsLib.sol
          • DepositContractUtilsLib.sol
          • OracleUtilsLib.sol
          • StakeUtilsLib.sol
        • Swap.sol
          • AmplificationUtils.sol
          • MathUtils.sol
          • SwapUtils.sol
          • LPToken.sol
        • WithdrawalContract.sol
        • Interfaces
          • ERC20InterfaceUpgaradable.sol
          • ERC20InterfacePermitUpgradable.sol
    • Audits
    • Bug Bounties
Powered by GitBook
On this page
  • These Automators Are Called Maintainers
  • It Is Safe To Trust Any Maintainers As They Don’t Have Many Permissions
  • Node Operators Can Use Maintainers Too
  1. Key Concepts
  2. Permissionless Configurable Staking Pools

Maintainers

Allowance

The Operator Marketplace works with Allowances and Approvals, like ERC20.

Every 32 ETH represents 1 validator, 1 balance.

Staking Pools can approve any subset of Node Operators for any amount of validators.

Node Operators can create any number of validators for the mentioned pool, up to their allowance.

While simple, and conventional, this task can be a burden for bigger Staking Pools.

Furthermore, this logic can be easily automated and not require any further user interaction.

These Automators Are Called Maintainers

The pool's owner, a script, smart contract, or a third party can be the maintainer of a pool.

Setting a maintainer is easy, and doesn't require anyone's approval other than the Staking Pool Owner.

Every Pool can have 1 Maintainer.

It Is Safe To Trust Any Maintainers As They Don’t Have Many Permissions

  • Can set validator allowance.

  • Can not change pool status to private/public.

  • Can not set a whitelist.

  • Can not deploy a liquidity pool.

  • Can not access to stakers' funds.

  • Can not claim any fees.

  • Can not switch MaintenanceFee.

  • Can not change Maintainer.

  • Can not change Controller.

Node Operators Can Use Maintainers Too

A Node Operator on the Marketplace is owned by its Controller.

But again, Staking Operations can be easily automated.

  • Can switch Validator Period.

  • Can propose new validators.

  • Can stake to beacon.

  • Can not claim any fees.

  • Can not switch MaintenanceFee.

  • Can not change Maintainer.

  • Can not change Controller.

PreviousCurrent InterfacesNextWithdrawal Contracts

Last updated 2 years ago

βš™οΈ
⛏️