Running the node
You can manage the node from either the Humanode or Logs screens.
We recommend you to start the node from the Humanode screen and then move to Logs to see if chain state sync is complete.

Running the node and synching

After you are done with the Settings you can go to the Humanode screen and press Start the node. You will need to accept requests if they appear.
All indicators should change to green, and the QR code for the bioauth enrolment and authentication will appear.
Once this is done, and everything appears to be as above, please go to the Logs and wait until the sync finishes. It can take a while.
If you scan your face before state sync is complete, you might get an error.
When the sync is complete, you can start enrollment or authentication process. Logs will change as follows:
2021-08-24 17:26:48 💤 Idle (3 peers), best: #11322 (0x0787…f440), finalized #0 (0x8f13…e745), ⬇ 0.3kiB/s ⬆ 0.2kiB/s
2021-08-24 17:26:53 💤 Idle (3 peers), best: #11322 (0x0787…f440), finalized #0 (0x8f13…e745), ⬇ 0 ⬆ 0
2021-08-24 17:26:54 ✨ Imported #11323 (0x2591…a139)
2021-08-24 17:26:58 💤 Idle (3 peers), best: #11323 (0x2591…a139), finalized #0 (0x8f13…e745), ⬇ 0.4kiB/s ⬆ 0.2kiB/s
2021-08-24 17:27:00 ✨ Imported #11324 (0x21f4…6314)
2021-08-24 17:27:03 💤 Idle (3 peers), best: #11324 (0x21f4…6314), finalized #0 (0x8f13…e745), ⬇ 0.3kiB/s ⬆ 0.2kiB/s
2021-08-24 17:27:06 ✨ Imported #11325 (0x699b…82f2)
2021-08-24 17:27:08 💤 Idle (3 peers), best: #11325 (0x699b…82f2), finalized #0 (0x8f13…e745), ⬇ 0.3kiB/s ⬆ 0.4kiB/s
2021-08-24 17:27:12 ✨ Imported #11326 (0x9e13…1d61)
2021-08-24 17:27:13 💤 Idle (3 peers), best: #11326 (0x9e13…1d61), finalized #0 (0x8f13…e745), ⬇ 0.4kiB/s ⬆ 0.4kiB/s
2021-08-24 17:27:18 ✨ Imported #11327 (0xe92e…3eca)

Enrolment and Authentication

When the sync is done, you can start the enrolment process (if you are running the Humanode for the first time) or authentication (if you have already ran Humanode previously).
Enrolment and authentication can be done by scanning the QR code on the "Humanode" page.
If you have enabled the Bioauth enrolment mode, take the following steps: Use the QR code to enroll into the system. Once it is "successful" in the Logs, scan the QR code the second time to authenticate. Open the QR code and scan your face again.
The node will authenticate itself with the blockchain and will be ready to produce and validate blocks.
If everything passed successfully, the indicator at the top will turn green and you'll get the timer on the Home page that indicates how much time is left for your auth ticket:
Your console output should look like this:
2021-08-21 18:25:01 Bioauth flow - authentication complete
2021-08-21 18:25:01 We've obtained an auth ticket auth_ticket=[128, ..., 0]
2021-08-21 18:25:02 💤 Idle (3 peers), best: #10 (0x4f96…fdec), finalized #0 (0x8f13…e745),0.7kiB/s ⬆ 0.3kiB/s
2021-08-21 18:25:06 ✨ Imported #11 (0x5594…e8a0)
2021-08-21 18:25:07 💤 Idle (3 peers), best: #11 (0x5594…e8a0), finalized #0 (0x8f13…e745),0.4kiB/s ⬆ 0.2kiB/s
2021-08-21 18:25:12 💤 Idle (3 peers), best: #11 (0x5594…e8a0), finalized #0 (0x8f13…e745),00
2021-08-21 18:25:12 ✨ Imported #12 (0x5ed2…da60)
2021-08-21 18:25:17 💤 Idle (3 peers), best: #12 (0x5ed2…da60), finalized #0 (0x8f13…e745),0.4kiB/s ⬆ 0.2kiB/s
2021-08-21 18:25:18 🙌 Starting consensus session on top of parent 0x5ed206762d36e0a47bffa4294d47bd9f4d85d959ced8d385017983ab8a8fda60
2021-08-21 18:25:18 🎁 Prepared block for proposing at 13 [hash: 0xa5396adaad72e875a61d71efe64984684e81b14e17a8f2892a1b6240b35c8600; parent_hash: 0x5ed2…da60; extrinsics (1): [0x4240…c102]]
2021-08-21 18:25:18 🔖 Pre-sealed block for proposal at 13. Hash now 0xa0ab5f3df7dc82a378b9206712b01f0c04ef1d08076626457aedb4c24479911a, previously 0xa5396adaad72e875a61d71efe64984684e81b14e17a8f2892a1b6240b35c8600.
2021-08-21 18:25:18 ✨ Imported #13 (0xa0ab…911a)
2021-08-21 18:25:22 💤 Idle (3 peers), best: #13 (0xa0ab…911a), finalized #0 (0x8f13…e745),0.1kiB/s ⬆ 0.4kiB/s
2021-08-21 18:25:24 ✨ Imported #14 (0xd65c…c7f1)
You should start getting rows with Starting consensus session on top of parent...
Congratulations, your Humanode peer has joined the Humanode testnet and produced blocks! You are one of the first human nodes in the Galaxy!

Re-authentication

To prevent extra malicious activity, Humanode uses a concept of authentication tickets to allow the peers to participate in consensus for blocks production. Unlike mainnet, where human nodes will have to go through the bio authentication every month, during the first testnet, each authentication ticket is valid only for 72 hours after passing the bio authentication procedure. Therefore, you need to get a new authentication ticket bypassing the bio authentication procedure again to continue participating in consensus.
The expiration of your ticket will be indicated at the top right corner of the navigation bar, also the QR code will appear on the Home page.
The following console output indicates that your authentication ticket has been expired.
2021-08-24 17:26:48 💤 Idle (3 peers), best: #11322 (0x0787…f440), finalized #0 (0x8f13…e745),0.3kiB/s ⬆ 0.2kiB/s
2021-08-24 17:26:53 💤 Idle (3 peers), best: #11322 (0x0787…f440), finalized #0 (0x8f13…e745),00
2021-08-24 17:26:54 ✨ Imported #11323 (0x2591…a139)
2021-08-24 17:26:58 💤 Idle (3 peers), best: #11323 (0x2591…a139), finalized #0 (0x8f13…e745),0.4kiB/s ⬆ 0.2kiB/s
2021-08-24 17:27:00 ✨ Imported #11324 (0x21f46314)
2021-08-24 17:27:03 💤 Idle (3 peers), best: #11324 (0x21f46314), finalized #0 (0x8f13…e745),0.3kiB/s ⬆ 0.2kiB/s
2021-08-24 17:27:06 ✨ Imported #11325 (0x699b…82f2)
2021-08-24 17:27:08 💤 Idle (3 peers), best: #11325 (0x699b…82f2), finalized #0 (0x8f13…e745),0.3kiB/s ⬆ 0.4kiB/s
2021-08-24 17:27:12 ✨ Imported #11326 (0x9e13…1d61)
2021-08-24 17:27:13 💤 Idle (3 peers), best: #11326 (0x9e13…1d61), finalized #0 (0x8f13…e745),0.4kiB/s ⬆ 0.4kiB/s
2021-08-24 17:27:18 ✨ Imported #11327 (0xe92e…3eca)
Note that there are no rows with Starting consensus session on top of the parent...
You have to go to the Humanode page and scan the QR code to get a new authentication ticket.
Copy link
On this page
Running the node and synching
Enrolment and Authentication
Re-authentication