Start here
How Hopbits works
Nodes in many places run the same small check, and the network sets their answers side by side.
Nodes
A node is a small program in a Docker container. It keeps one outgoing encrypted connection to the Hopbits gateway and waits for jobs. Nothing connects in to it.
Each node is labelled residential or datacenter, after the kind of connection it sits on. Residential nodes show what people at home get. Datacenter nodes give a steady baseline to compare against.
Jobs
A job is one bounded measurement against one public target: an HTTP request, a TCP connect or a ping. Every job is signed. The node checks the signature against keys built into it and refuses anything else.
Before it sends a single packet the node applies its own limits: which addresses and ports it will touch, how often, and how much data in a day. The network cannot loosen those limits. It can only tighten them.
Results
A monitor or a measurement asks nodes in each country you chose. The answer comes back per country, together with how many nodes it is based on, so one bad line does not pass for an outage.
You read the results in the business dashboard or through the API.
Points
Operators earn points for the hours a node is online and for validated measurement work. A finished UTC day appears as pending and is confirmed after a review period. Points has the details.