licash observatoryMutinynetSignetBitcoinTest network

Overview

Hubs up
2 of 2
answering now
Providers up
3 of 4
answering now
Round trip
249 ms
opening a connection over Tor: 1.4 s
Moves succeeded
–
0 of 0
Spent
0 sat
of 20,000 sat in 30 days
Balance
60,000 sat
the observatory's, in Licash

Leaderboards

Uptime

Not enough measured yet.

Round trip

Not enough measured yet.

Moves succeeded

Not enough measured yet.

Fees on 10,000 sat

WhatCheapestIts feeMedianOffered by
Pay in Licashm0wer mutinynet hub (Tor)1 sat · 0.01%1 sat · 0.01%2
Move to another hubsgn.space mutinynet hub1 sat · 0.01%5 sat · 0.05%3
Pay over Lightningsgn.space mutinynet hub12 sat · 0.12%12 sat · 0.12%1
Receive over Lightningsgn.space mutinynet hub1 sat · 0.01%1 sat · 0.01%1
Pay over Lightning, through a providerNobody–0
Receive on Bitcoinm0wer mutinynet hub (Tor)300 sat · 3.0%300 sat · 3.0%2
Pay on Bitcoinm0wer mutinynet swaps (Tor)555 sat · 5.5%555 sat · 5.5%2
Protection, openingm0wer mutinynet hub (Tor)3,000 sat3,000 sat2
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.