Leaderboards
Uptime
Not enough measured yet.
Round trip
Not enough measured yet.
Moves succeeded
Not enough measured yet.
Fees on 10,000 sat
| What | Cheapest | Its fee | Median | Offered by |
|---|---|---|---|---|
| Pay in Licash | Nobody | – | 0 | |
| Move to another hub | Nobody | – | 0 | |
| Pay over Lightning | Nobody | – | 0 | |
| Receive over Lightning | Nobody | – | 0 | |
| Pay over Lightning, through a provider | Nobody | – | 0 | |
| Receive on Bitcoin | Nobody | – | 0 | |
| Pay on Bitcoin | Nobody | – | 0 | |
| Protection, opening | Nobody | – | 0 |
How this is measured
Every hub and provider is reached over Tor, each probe on a new circuit, so that none is favored by where the observatory runs. Round trip is the median time of a request on a connection already open: it still crosses Tor, but every service is measured over the same many random circuits. Opening that connection (Tor's circuit, the stream and TLS) is mostly Tor's time, and is shown apart.
Each service is probed every few minutes at a random moment: its health, then its terms. Uptime is the share of probes answered. A service is ranked once probed 3 times in the range.
The observatory also moves a small balance of its own between hubs, at random times, as often as its monthly budget allows: cheap moves often, payouts on Bitcoin seldom. Moves succeeded counts those that went through each hub or provider.