FAQs

1. How long does it take for a node to become a validator? I have done all the steps, but my validator status is still red. It takes 2 complete epochs (8 hours) before a node starts validating blocks.

2. I'm getting a "Failed to connect to Substrate" error. How can I solve this? This is a UI bug related to bootstrap. Don't worry! Restarting the node a few times will fix it.

3. I have some HMND in my account. Why is my balance still showing 0 on the launcher? Make sure your node is synced. Then restart the node. It will refresh the UI and show your balance.

4. I can't generate a mnemonic on the launcher. It says "An unexpected error happened. The output was hidden to avoid unintended information disclosure." We officially support Ubuntu 20.04. Please check and make sure you're using the supported distribution.

5. I want to transfer a node to another VPS, how can I do it? Make sure the old node is up and running > Install the new node > Synchronize the new node > Switch the new node to validator mode > Rotate and set the keys on the new node > Wait for new key mappings to activate (~3 epochs) > Shut down the old node

6. Why was my balance deducted when I set and rotated session keys? Setting and rotating session keys incur gas fees for execution. Hence, each time you perform these actions, you'll be required to cover the associated gas costs.

7. I am getting an "Authentication failed" error while authenticating myself on the phone. Before you authenticate yourself you need to enroll yourself (which is a one-time process). Follow the guide step by step to first enroll and then authenticate.

8. I am getting an "Enrollment failed" error while trying to enroll myself on the phone. This error occurs if you have generated more than one mnemonic in the launcher. Please insert the very first mnemonic you generated in the KEY MANAGEMENT section.

9. Do I need to authenticate once only? No, in order to keep your node up and running and prove that you're alive you need to reauthenticate every 7 days (168 hours) at the same time.

10. What if twins want to run two different nodes? Despite Humanode utilizing biometric verification tech with the highest possible accuracy, currently, biometric verification systems aren't yet advanced enough to distinguish between identical twins, who share the same genetic makeup and physical characteristics. As a result, it is currently not feasible to support multiple nodes for identical twins due to these technological limitations

11. Why was my BioAuthentication status revoked before the expiry period? In Humanode, staying authenticated as a validator means your node must remain active and online. If your node is offline or unresponsive, it can lead to removal in two cases:

    Two Scenarios Where You Might Be kicked off the validators list:

    1. Missed Block Production: If you didn’t produce at least one block during an epoch, your validator status is revoked. This happens if your node isn’t online when expected or isn’t configured properly, and you’ll be kicked off the validators set and need to reauthenticate to regain your spot.

    2. Offline at Epoch End: If your node is offline or unresponsive at the end of an epoch, the IamOnline function will remove your authentication ticket and kick you off the validators set. You’ll then need to reauthenticate before you can be added back as a validator.

    In both cases, reauthentication is required to restore your validator status.

    The IamOnline function plays an important role in this, as it checks if your node is online during each 4-hour epoch to make sure only online validators remain in the validators set. This function was recently reactivated after a year-long bug, which is why some users are now seeing unexpected revocations or removals from the validators set. Other than IamOnline function, BABE also plays an important part in kicking validators if a node didn’t produce at least one block in an epoch (keeping in mind that the node is selected in the validators set for the epoch), the status is revoked.

12. Why am I not included in the validators set for this epoch? If you’re not a validator in the current epoch, there are a few possible reasons:

    1. Not Active When the Epoch Started: The validator list is updated only at the beginning of each epoch (4 hours long). If your node wasn’t online or didn’t have a bioauth ticket when the epoch began, you will not be added to the validators set for this round.

    2. Missed Authentication or Reauthentication: If your previous authentication expired or was revoked (for example, if your node was offline for more than one epoch or didn’t produce any blocks within an epoch), you’ll need to reauthenticate to be eligible for the next epoch.

    3. Technical or Configuration Issues: If there are any issues with your node setup, internet connection, or configuration, your node may not be eligible for validation in this epoch.

    To become a validator in the next epoch, ensure that your node is online, correctly configured, and authenticated before the epoch starts.

13. Why do I need to wait 2 epochs to become a validator?

    When new validators join the Humanode network, they might need to wait at most two epochs before they can start producing blocks. This is because the network uses VRF (Verifiable Random Function) to randomly decide who produces a block in each slot, ensuring fairness.

    VRF checks are like a “random check” each validator goes through to see if it’s their turn. For this to work, the network needs enough randomness, which takes at most two epochs to gather. This waiting period helps make sure that everyone’s turn is fair and keeps the network secure and balanced.