Project

Hopbits litepaper

What Hopbits is and where it is going, how the network works, what operators earn, how the points economy is built, and what is still undecided. A short paper, kept up to date.

On this page

Hopbits is a network of independent nodes that measures the internet from where people use it: whether a service can be reached, how fast it answers, and where an IP address really is. Operators run a small node and earn points for the measuring. Businesses read the results in a dashboard and through an API.

The gap

Most monitoring runs from data centres. Most people do not. They are on home and mobile connections, behind a local provider, at the end of a route no cloud server ever travels.

That last stretch is where a service can fail for one country, one provider or one evening while every dashboard stays green. Our blog follows cases as they happen: a football match that takes websites offline in Spain, six hours without power in a London cloud zone, and a court finding that IP location cannot be perfect.

Closing the gap takes many points of view on many networks. No company can rent them all. People who already have a connection can run a node on it.

The goal

Hopbits has one goal: to become the largest and most accurate network for measuring the internet from real connections, and the first place people turn to when they need to know how a service looks from somewhere else.

Open networks such as RIPE Atlas and Globalping have shown how much a shared measurement network can do. They are the bar we measure ourselves against. We get there in three steps:

  1. A node in every country

    First, at least one node online in every country of the world. When a business asks whether we can check from a country, the answer should always be yes.

  2. City by city

    Then as many cities as we can reach inside each country. Data centres are built in a few places, and most cities have none. Homes and offices are everywhere, so that is where these nodes come from.

  3. Network by network

    Then as many home and mobile providers as there are. Each provider runs its own network, and a failure often belongs to just one of them. Only a node on that network can see it.

Size is half of the goal. Accuracy is the other half, and it grows with the network: every node is checked, every answer is compared with the answers of other nodes, and every result says how many nodes it rests on. The more independent nodes a place has, the surer its results.

We are at the start of this path. The status page counts the countries, cities and networks that have a node online right now, and every new node in a new place moves the count. Run a node to add yours.

The network

A node is a small program in a Docker container on a Linux machine. It keeps one outgoing encrypted connection to Hopbits and waits for jobs. Nothing connects in to it.

  • A node only measures. A job is one small check against one public address: an HTTP request, a TCP connect, a ping, a DNS lookup or a trace of the route. A node is not a proxy and never carries anyone else's traffic.
  • Every job is signed. The node checks the signature and refuses anything else. It also keeps its own limits on what it will touch, how often, and how much data it uses in a day. The network cannot loosen them.
  • The node is open source. The node client and the command-line tool are published under the Apache 2.0 licence on GitHub, so anyone can read what runs on their machine before starting it. The service that hands out the jobs and checks the answers is not public, because the checks against cheating live there.
  • Three kinds of connection. Home and mobile nodes show what people really get. Datacenter nodes give a steady line to compare against.
  • Answers are compared. A check asks several nodes on different networks in each country, so one bad line does not pass for an outage.

How Hopbits works has the longer version. What a node will never do lists the limits built into the client.

What businesses use today

ProductWhat it does
MonitorsCheck a service on a schedule from up to three countries, and tell you by email or webhook when a country stops reaching it and when it recovers.
Instant testsRun a check right now from the countries and kinds of connection you choose, and show what every node saw: HTTP, TCP, ping, a DNS lookup or a trace of the route.
IP locationTime the replies from several nodes to say in what area an address can be, how sure that is, and whether a claimed country fits.
APIAll of the above from your own code, with keys you create in the dashboard.

Prices are in US dollars and no wallet is needed. Every account with a verified email gets 1,000 free credits a day, enough to watch a service around the clock. For businesses explains each product, and three of them have a page of their own with examples: uptime monitoring, network tests and IP location.

What comes next

These products are the first ones, not the limit. What Hopbits really has is the network: independent points of view on real connections that can be asked a question. Each new kind of question is a new product, and the same nodes can answer it.

Which ones we build depends on two things: what businesses ask for, and where the network has enough nodes to answer well. We would sooner build for a use case a customer brings than promise a list here. The direction is this:

StageWhat it means
NowBuild the foundation: the first Linux and Docker operators, and the first business teams.
NextExpand the network: more nodes on more networks, measurements checked against each other across networks, and the points rules refined.
AheadDeeper intelligence: more confidence in IP location answers, more ways to be notified, and benchmarks by region.
PlannedGlobal reach: more countries, cities and local providers, so every check has a closer point of view.

What operators earn

Operators earn points. Today a node earns them for the hours it is online and reachable. A home or mobile connection earns more than a datacenter one, because that point of view is harder to come by.

  • A finished day shows as pending and is confirmed after a review period.
  • One node per public address earns points. You can still connect as many nodes as you like.
  • Inviting another operator earns a bonus on their confirmed points, one level deep. It is added on top, so they keep all of theirs.

Points has the rules in full.

The points economy

Two things move through Hopbits. Businesses bring credits, which they spend on measurements. Operators earn points, which record what their nodes gave the network. The points economy is the set of rules that ties the two together, and it has to be fair to both.

WhoWhat they giveWhat they get
BusinessesThey pay for measurements with credits. Pricing lists the packages.Answers from real connections in the countries they choose.
OperatorsThey keep a node online on a real connection and let it measure.Points: today for time online, later also for the measurements that paying clients run through the node.
HopbitsIt runs the network: it sends the jobs, compares the answers and keeps points fair.Later, the part of client income that does not go to operators. It pays for the infrastructure and for the people who build the network.

The economy is built in three phases, and each one adds to the one before.

PhaseWhat it addsWhen
1. BaselinePoints for time online. Nodes on the same kind of connection earn the same, however much clients use them.Now
2. UsageOn top of the baseline, points for the measurements that paying clients run through a node.Once businesses pay for measurements
3. PayoutsA fixed share of what clients pay goes to the operators and is split by their points.No date yet

How points develop describes each phase in full. Four things are meant to hold in all of them:

  • The baseline stays. A node in a quiet place is still a point of view that businesses need, so time online keeps earning.
  • Usage follows real demand. Only measurements a client paid for count. Measurements on free credits do not, and neither do tests an account runs through its own nodes.
  • Payouts come from income. Operators are to be paid from what clients pay, which is why a point has no fixed price.
  • Both sides have to gain. Operators need a fair return for a real connection. Businesses need prices they can afford and answers they can trust. The rules can change to keep that balance, and each change is written into these docs before it applies.

From points to payouts

This part is still in development. Here is what is decided and what is not.

QuestionWhere it stands
What do nodes earn today?Points for time online. They record what each operator has contributed while the network is being built.
What will the points lead to?Payouts from what clients pay. We intend to pay the operators a fixed share of that income, split by their points, and to keep the rest to run the infrastructure and pay the people who build the network. Early participants are to get a part of their own for helping to build it.
What is a point worth?It has no fixed price. A point is a part of the operators' share for a period, so its worth follows what clients paid in that period.
Will there be a Hopbits token?There are no plans for one. A token of our own would be one more layer that costs effort and brings downsides, when existing currencies and crypto already let us receive and pay out funds. There is no Hopbits token today, so anyone offering you one is not us.
How will operators be paid?In both ordinary currency and crypto.
How much, and from when?Not decided. No share, date or schedule has been set.

Who is behind it

Hopbits is independent. It has no outside investors today. We expect to look for investment at a later stage of the network's growth, and this page will say so when that changes.

The quickest way to reach us is the Hopbits Discord. For anything private, write to [email protected].

Where it stands

  • The node client for Linux and Docker, the operator and business dashboards, the API and these docs are live.
  • The network is in its first stage. The status page shows how many nodes are online and in which countries, as it is right now.
  • Rules can still change as the network grows, above all the ones that keep points fair. Changes are written into these docs.