HOPRators, we need your feedback

Hi Andrew, I mentioned those suggestions loosely. I think to get the most out of it you would need to question what makes a “Good” HOPR node.


0-1 Peers = 5 points
1-5 Peers = 10 points
5-10 Peers = 33 points

Staked HOPR:

10-100 HOPR = 5 points
100-1000 HOPR = 10 points
1000-5000 HOPR = 15 points
5000-10000 HOPR = 33 points


1mb/s = 1 point
5mb/s = 15 points
10mb/s - 50mb/s = 20 points
50mb/s - 500mb/s = 33 points

Then you would grab the total.

For example 4 peers with 1000 HOPR staked with a connection of 33mb/s would give you a score of 44/100 = 44% giving you an average or moderate score.

The selection of what is measured and the points would be up to the HOPR team to decide or for the DOA to vote for.



Cool, got your great idea! Thanks!

Hey Andrew!
“Read access to logfile from UI” - Ease of access. Logfile could be viewed from command line or pulled off the node (VPS) but having it viewable in the UI is likely easier on the end user.

“Read access to dbschema from UI.” - If allowing queries against the db is possible, having the dbschema available would be helpful but does not really need to be viewable from the UI.

“Simple UI for read only queries to the db.” - troubleshooting issues, monitoring health of a queue, getting counts and statuses for transactions going through the system.

Side Note: I have a node running on an raspberry pi which is not connected to a battery backup power source.(yet) I had a power flicker causing the rPi to reboot itself. After this, hoprd would not start properly. From viewing logfile data, it appeared a transaction was hung in a pending status, and this was preventing hoprd from starting. Since the node was not funded yet, I took the easy route and after confirming with Juri on telegram, decided to just wipe it and reinstall with a new version of hoprd.(where a potential issue may have already been fixed) Had this been a funded node, wipe/reinstall may not have been a reasonable solution for fear of loss of funds. I would need to familiarize myself with how you are queuing transactions but I suspect the hung transaction could have been an easy fix by simply updating a status or something in the database. Main take away, there will be nodes running in the field that have issues and some of those nodes could be funded with tens of thousands of HOPR. There should be good troubleshooting tools available. Also, in case of a catastrophic failure such as a lightening strike that completely fries a node, there should be documentation about how to withdraw from and/or migrate an existing wallet address even when the corresponding node is not functional.

Current cost per transaction.(in HOPR and/or USD) - about which transaction you are talking about? gas costs? - I was referring to how much HOPR an end user would pay to send his/her message through the HOPR protocol but if gas fee information is available this could be useful too. At the end of the day, I just want clear information about how my nodes are preforming and want some peace of mind that my node funding will be safe, secure, and recoverable.


Hi Andrew! It could be a web interface, where it practically gives me information about the node.

something similar exists in a node that I am currently running and it is very useful to me.

something like this:

Node Statistics

Current Node Status

Description :

$HOPR Stake: $1000 HOPR

Status Connected/disconected (00:00:00 hrs)

Node Version: 1.70.8

Date Registered e.j. 11 Mar 2021, 6:16 pm UTC

Total traffic processed: e.j. 45/mb, GB

Filters en Web interface:

Last Day

All Time

Custom date range (UTC)

Server Statistics

Total Uptime 12d, 20h, 6m, 48s (40%)

Avg Latency 2,232.0 ms

Avg Success Rate 59.2%

Reward Calculations

Avg Reliability Score 46.1

Avg Uptime Score 87.0

Avg Latency Score 6.0

Avg Success Rate Score 47.8

Avg Staked Capacity % 0.0000%

Avg Utilization % 0.0006%

Total Earned 0.0000 HOPR

1 Like