MilkyWay Docs
  • INTRODUCTION
    • Welcome to MilkyWay
    • Mission and Vision
    • MILK
      • Staking
        • Quick Start
      • Governance
        • Quick Start
      • Network Parameters
        • Chain Registry
      • Tokenomics
  • User Guides
    • For Liquid Stakers
      • Celestia (milkTIA)
        • Quick Start
        • Using third party apps
          • Camelot
          • Demex
          • Dymension
          • Levana
          • Margined
          • Mars
          • Osmosis
          • UX
      • Initia (milkINIT)
        • Quick Start
        • Using third party apps
      • Babylon (milkBABY)
        • Quick Start
        • Using third party apps
    • For Restakers
      • Quick Start
      • Creating a wallet
      • Restaking your assets
    • Bridging
      • Hyperlane
      • IBC Eureka
  • Infrastructure Operators
    • For Validators
      • Quick Start
      • Consesus node
      • Validator node
  • For Operators
    • Quick Start
    • Operator Management
    • Opt-in and Opt-out Services
  • For Developers
    • Quick Start
    • Service Management
    • Inviting Operators to Join Your Service
    • Creating Rewards Distribution Plan
  • Architecture
    • Modular Liquid Staking
      • Overview
      • Liquid Staking 101
      • Celestia (milkTIA)
        • Technical Architecture
          • Liquid Staking Process
          • Withdrawal Process
          • Exchange Rate
          • Compound Staking Rewards
          • Claim Process
          • Limits and Restrictions
        • Integrating with milkTIA
          • Contract Specifications
          • APIs specification
      • Initia (milkINIT)
        • Technical Architecture
          • Liquid Staking Process
          • Withdrawal Process
          • Exchange Rate
          • Compound Staking Rewards
          • Claim Process
          • Limits and Restrictions
        • Integrating with milkINIT
          • Liquid staking module specifications
          • Chains specifications
      • Bablyon (milkBABY)
        • Technical Architecture
          • Liquid Staking Process
          • Withdrawal Process
          • Exchange Rate
          • Compound Staking Rewards
          • Claim Process
          • Limits and Restrictions
        • Integrating with milkBABY
          • Liquid staking module specifications
          • Chains specifications
    • Modular Restaking
      • Overview
        • Technical Architecture
        • Design Philosophy
        • Programmable Rules
        • Economic Model
        • Use Cases
      • Restaking 101
      • Modules
        • x/assets
        • x/ibc-hooks
        • x/liquidvesting
        • x/operators
        • x/pools
        • x/restaking
        • x/rewards
        • x/services
        • x/tokenfactory
  • SECURITY
    • Audits
    • Bug Bounty Program
  • APPENDIX
    • Official Links
    • Frequently Asked Questions
    • Glossary
    • Branding Resources
    • Whitepaper (PDF)
Powered by GitBook
On this page
  • Adding an operator to the allow list
  • Removing an operator from the allow list
  1. For Developers

Inviting Operators to Join Your Service

After setting up your service, you can invite operators to join and confirm they will run your binary file and validate your service. To help them get started, send them this guide: Opt-in and Opt-out Services.

By default, any operator that has your service ID will be able to join and take part to the rewards distribution. However, if you want to limit which operators are allowed to join you can do so by using a list of allowed operators.

If your service's allow list only contains an operator, and that operator gets deleted, your service will automatically be marked as INACTIVE. You will then be required to set up a new allow list or simply activate it again without any restriction on what operators can join.

Adding an operator to the allow list

To add an operator to your service's allow list, you will have to know its ID. Once you have that, you can run the following transaction:

milkywayd tx restaking service allow-operator [service-id] [operator-id]

Where:

  • [service-id] is the unique ID of your service.

  • [operator-id] is the unique ID of the operator you want to add to the allow list.

Removing an operator from the allow list

If you want to remove an operator from the allow list of your service, you can do so by running the following command:

milkywayd tx restaking service remove-allowed-operator [service-id] [operator-id]

Where:

  • [service-id] is the unique ID of your service.

  • [operator-id] is the unique ID of the operator you want to remove from the allow list.

PreviousService ManagementNextCreating Rewards Distribution Plan

Last updated 6 months ago