🚀
Energy Web X Ecosystem
  • Documentation Overview
  • Core Concepts
    • Energy Web Chain
    • Energy Web X
    • Energy Web Tokens
      • Token Lifting
      • Token Lowering
    • Worker Nodes and Worker Node Networks
      • Server-based Worker Node
      • Marketplace App (desktop-based)
    • Worker Node Operator
    • Smart Flows and Groups
    • Subscription
    • Reward Period
    • Voting and Consensus
    • Ethereum
      • Transactions and Transaction Costs
    • Decentralized Identifiers (DIDs)
  • EWC ECOSYSTEM
    • Energy Web Chain
      • System Architecture
        • Proof-of-Authority Consensus Mechanism
        • System Contracts
          • Name registry
          • Holding Contract
          • Block Reward Contract
          • Validator-Set Contract
        • Validator Node Architecture
      • Energy Web Block Explorer
      • Energy Web Chain Governance & Validators
    • Energy Web Tokens
  • EWX ECOSYSTEM
    • Energy Web X
    • EWX: Architecture
    • Pallets
      • Worker Node Pallet
      • Balances Pallet
      • Proxy Pallet
      • XCM Pallet
      • Assets Pallet
      • Multisig Pallet
      • Scheduler Pallet
      • Preimages Pallet
      • Offences Pallet
      • Eth-Bridge Pallet
      • Token-Manager Pallet
      • Ethereum-events pallet
      • Avn Pallet
    • Worker Nodes
      • 🖥️The Marketplace App
        • Operator and Worker Accounts
          • Creating an operator account
          • Funding an operator account
          • Connecting to operator account
          • Disconnecting an operator account
          • Creating a worker account
          • Importing worker account
          • Exporting worker account
          • Linking a worker account to an operator account
          • Unlinking a worker account from an operator account
        • How to use Ledger on Marketplace App
        • Token Management
          • Creating an EWC account
          • Managing EWC accounts
          • Lifting tokens
          • Lowering tokens
          • Tracking lifting and lowering transactions
          • Checking EWT balance
        • Subscriptions
          • Subscribing to a solution group
          • Topping-up subscription amount
          • Managing subscriptions
          • Unsubscribing from a solution group
          • Unsubscribing delay
        • Worker Node and Rewards
          • Configuring remote worker node
          • Switching worker node location to remote
          • Participating into worker node network
          • Votes casted per Period
          • Reward Period
          • Checking rewards
          • Claiming rewards
        • FAQ: Marketplace App
        • Location Services
      • 🗄️Server-based Worker Nodes
        • Deployment Guide
        • Bootstrapping Server-based Worker Node Accounts
        • FAQ: Server-based Worker Nodes
      • Worker Node use cases
        • Sample Enterprise Use-Cases
          • Operating Envelopes Partitioning
          • ZEL Request Partitioning
          • Green Proofs
            • SAFc
            • Green Proofs for Bitcoin (GP4BTC)
            • Green Proofs as a Service (GPSaaS)
            • Green Proofs for Electrical Vehicles (GP4EV)
  • ENERGY SOLUTIONS
    • Green Proofs by Energy Web
      • Green Proofs Overview
      • Green Proofs Architecure
      • Green Proofs Software Stack
      • Use Cases and Reference Implementations
        • 24x7 Renewable Electricity
        • Sustainable Aviation Fuel
        • Green Proofs for Bitcoin
          • GP4BTC Miner Guide
        • Decarbonizing Shipping
        • Green Proofs for Electrical Vehicles
        • Green Proofs as a Service (GPSaaS)
    • Digital Spine by Energy Web
      • Design and Architecture
      • Component Guides
        • Energy Web Name Service (ENS)
        • Self-Sovereign Identities
          • SSI-Hub
          • Technical Guide
            • Organizations
            • Applications
            • Roles and IAM
          • Deployment Guide
            • Deploy Identity Cache Server
            • Deploy Switchboard
        • DDHub Message Broker
          • Technical Guide
            • Authentication and Authorization
            • Topics
            • Messaging
          • Deployment Guide
            • Deploy DID Auth Proxy
            • Deploy Message Broker
        • DDHub Client Gateway
          • Technical Guide
            • Authentication and Authorization
              • Key Vault
            • Client Gateway Identity and VCs
            • Address Book
            • Topics
            • Channels
            • Integration Options
            • Messaging
          • Deployment Guide
            • Launchpad SaaS
            • Azure Marketplace
            • Self-Hosted
              • Deploy with Kubernetes
              • Deploy with Docker
            • Key Vault
              • Deploy with HashiCorp Key Vault
              • Deploy with Azure Key Vault
              • Deploy with AWS Secrets Manager
            • Rebranding and Whitelabelling
Powered by GitBook
On this page
  1. EWX ECOSYSTEM
  2. Worker Nodes
  3. Server-based Worker Nodes

FAQ: Server-based Worker Nodes

PreviousBootstrapping Server-based Worker Node AccountsNextWorker Node use cases

Last updated 2 months ago

FAQ section is ever-growing, to accomodate frequently asked questions gathered by users. If you have some ideas for further information to be included here, please let us know!


Q: Is there an alternative way to bootstrap an operator account rather than using Marketplace App?

Yes, follow these steps to manually create an operator account:

  1. Visit .

  2. Select MAINNET EWX, depending on your use case.

  3. Go to .

  4. As the operator, call the extrinsic workerNodePallet.signupWorkerNodeOperator.

  5. As the operator, call the extrinsic workerNodePallet.registerWorker, passing the address of your worker.

  6. Finally, as the operator, call the extrinsic workerNodePallet.subscribeOperatorToSolutionGroup. To obtain the group, go to Developer -> Chain state -> workerNodePallet -> solutionsGroups.


Q: How many Worker Accounts can be assigned to single Operator Account ?

For now, single Operator to Worker account assignment is supported. You can always disconnect previously connected Worker Account and replace it with different one.


Q: Can I switch between Managed/Self-hosted versions of Worker Node ?

Yes, you can switch and move to new Worker any moment. If you dont want to tamper with blockchain-setup you just need to use the same Worker Account Seed in your new Worker. Keep in mind that old Worker Node instance should be stopped right after new one is set up.


Q: Where I can find blockchain explorers for EWX?


Q: Can I move between Launchpad/Marketplace Desktop App based worker/Server Based Worker Node?

Yes, you can move to another type of worker any time you want. The only thing you need is to use the same Worker Account Seed for configuration of your new worker.

Once new worker is set-up turned on on desired platform , please always remember to turn-off previous instance to omit double-voting which can potentially lead to unintended behaviour.


Q: Where and when will I be able to check whether my Worker is voting correctly?

  1. When you subscribe to any Solution Group using your Operator Account linked to Worker Account configured for your Worker, there is a max-24-hours period before any votes from your Worker will be accepted by EWX.

  2. After that time, your worker will start executing Solutions WorkLogic from Solutions that are in Active state in non-expired Solution Groups that your Operator Account is subscribed to.

  3. You should be able to view votes being submitted from your Worker

    • In Worker Node logs


Q: Are there any limits on Worker Node instances that I can set up?

  1. There is no limit on amount of Worker single user can set-up, but keep in mind that single Operator Account can have only single Worker Account linked

  2. You can set-up multiple Worker Nodes on the same machine if resources are allowing for that.

  3. Single Worker can handle multiple Solution Group subscription and therefore run multiple solutions simultaneously.


Q: Are there any tools where I can find EWX and Worker Nodes related stats?

While there is no official EW-built dashboard, there are several community/partner built dashboards that you can check.


Q: For one solution I see 50 votes while for other only 5 votes that are being casted by my Worker Node per reward period (24-hours), is that normal?

Each solution represent unique logic therefore different quantities of votes could be perfectly normal behaviour to expect.

As business process captured within solution logic is different, therefore also schedules and triggers can be also totally different.

E.g one solution can demand a steady voting every 30 min, while other can have an asynchronous triggers coming from real us of a given app.

Please keep in mind, that system does not reward quantity of voting itself, but rather quantity of votes when votes were needed - meaning it incentives your worker to run 24/7 instead of casting large amount of votes at random times.

You can use or explorer.

In after checking details of Solution Groups you subscribed to

By querying as shown in Picture (Use Operator Address here)

By querying as shown in Screenshot (Use Worker Address here)

🗄️
PolkadotJS
PolkadotJS Extrinsics
EWX Subscan
PolkadotJS
Marketplace App UI
EWX chainstate
EWX indexer
https://ewx.ewchain.io/
https://dune.com/substrate/energywebx
https://tokenterminal.com/explorer/projects/energyweb