FAQ: Server-based Worker Nodes

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 PolkadotJS.

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

3. Go to PolkadotJS Extrinsics.

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?

You can use EWX Subscan or PolkadotJS explorer.

---

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

   • In Marketplace App UI after checking details of Solution Groups you subscribed to

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

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

---

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.

1. https://ewx.ewchain.io/

2. https://dune.com/substrate/energywebx

3. https://tokenterminal.com/explorer/projects/energyweb

---

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.