Bitrovas Wallet-Adressen

https://api.bitrovas.ch/v1/walletaddr

Watch-only address derivation from xpub/ypub/zpub/tpub or an output descriptor: receive + change addresses (configurable gap, max 1000) and ownership check of given addresses with derivation path. Offline, nothing stored. Private keys/seeds are rejected.

54
reliability

Reliability & health

Uptime and response time from our own unpaid probes, plus the reliability score built from them.

Uptime

100.0% avg
0% 50% 100% Oct 21Oct 28Nov 5Nov 17

Response time

p50 742ms · p95 991ms
0ms 550ms 1100ms Oct 21Oct 28Nov 5Nov 17
Data table
Reliability history per time bucket over the last 30 days (daily).
Bucket Uptime Probes Response time
10/21/2026, 12:00:00 AM 100% 9 738ms
10/22/2026, 12:00:00 AM 100% 1 995ms
10/23/2026, 12:00:00 AM 100% 1 858ms
10/25/2026, 12:00:00 AM 100% 1 704ms
10/26/2026, 12:00:00 AM 100% 1 1028ms
10/28/2026, 12:00:00 AM 100% 1 937ms
10/30/2026, 12:00:00 AM 100% 1 665ms
11/1/2026, 12:00:00 AM 100% 1 725ms
11/3/2026, 12:00:00 AM 100% 1 709ms
11/5/2026, 12:00:00 AM 100% 1 748ms
11/8/2026, 12:00:00 AM 100% 1 687ms
11/10/2026, 12:00:00 AM 100% 1 747ms
11/12/2026, 12:00:00 AM 100% 1 731ms
11/15/2026, 12:00:00 AM 100% 1 969ms
11/17/2026, 12:00:00 AM 100% 1 753ms
54
Composite reliability — the weighted average of the dimensions below, on a 0–100 scale.
Availability
96

How often it was reachable when we probed it (weight 35%).

Latency
83

How quickly it answers when it is up — fast scores high (weight 20%).

Security
100

Whether it serves over working TLS / https (weight 15%).

Transparency
36

Whether the operator disclosed what it does — description, schema, identity (weight 15%).

Activity
not yet measured

Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).

Confidence 54% — how much probe evidence backs this score. A thin history is flagged, not hidden.

See the scoring methodology for exactly how each number is computed.

Payment

Currencies
BTC
Networks
lightning
Facilitator
unknown
SDK
unknown

Operator

Company
inferred — unknown
Jurisdiction
—
Registrar
—
Domain registered
—
Hosting network
MSFT
Hosting country
—

Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.