LearnHNS SPV Helper
Aggregate, privacy-preserving activity for spv.learnhns.com/hsd.
The badge checks node configuration and sync progress. It does not measure request reliability or independently verify the latest network tip.
Recent API reliability · approximately 15 minutes
1,043 API requests · 0 HTTP errors · 0 rate limited · 0 server errors · 0 RPC error responses
Current minute and previous 14 minutes, limited by process uptime. Window: 2026-10-06T03:06:00.000Z to 2026-10-06T03:20:16.000Z.
Requests by API category
| Category | Requests | HTTP errors | Average | Maximum |
|---|---|---|---|---|
| Address history | 4,322 | 246 | 392.84 ms | 10,004.95 ms |
| Block lookups | 60,539 | 8 | 30.08 ms | 10,001.31 ms |
| Coin lookups | 8,680 | 270 | 4.64 ms | 1,519.13 ms |
| Header lookups | 172 | 1 | 6.9 ms | 61.08 ms |
| Node information | 79 | 0 | 9.11 ms | 48.85 ms |
| Read-only RPC | 1,685,860 | 19,971 | 24.71 ms | 17,281.6 ms |
| Transaction lookups | 296,370 | 12,137 | 603.6 ms | 10,005.17 ms |
Why requests failed
Totals cover this process lifetime. HTTP 429 means throttling, not a node outage. HTTP 404 means a record was not found; a coin may already be spent. Rejected requests include invalid input and blocked RPC methods. Timeouts and other upstream failures need investigation.
RPC error responses are counted here even with HTTP 200; they may reflect invalid parameters or an operation-specific failure. They can overlap HTTP errors. Upstream failures in the summary also include health and analytics probes.
| Category | HTTP | Reason | Total | Recent | Last seen (UTC) |
|---|---|---|---|---|---|
| Address history | 429 | Address-history rate limit | 227 | 0 | 2026-10-05T12:43:14.000Z |
| Address history | 429 | General rate limit | 11 | 0 | 2026-09-30T18:09:08.000Z |
| Address history | 504 | Upstream timeout | 8 | 0 | 2026-10-04T04:06:19.000Z |
| Block lookups | 504 | Upstream timeout | 8 | 0 | 2026-10-04T05:39:41.000Z |
| Coin lookups | 404 | Record not found | 258 | 0 | 2026-10-05T14:34:20.000Z |
| Coin lookups | 429 | General rate limit | 12 | 0 | 2026-09-30T18:09:08.000Z |
| Header lookups | 404 | Record not found | 1 | 0 | 2026-09-29T06:30:49.000Z |
| Read-only RPC | 200 | RPC returned an error | 68 | 0 | 2026-10-06T02:30:08.000Z |
| Read-only RPC | 400 | Request rejected | 1 | 0 | 2026-09-26T02:50:51.000Z |
| Read-only RPC | 403 | Request rejected | 7 | 0 | 2026-09-29T06:29:10.000Z |
| Read-only RPC | 429 | Transaction-broadcast rate limit | 4 | 0 | 2026-09-29T16:57:47.000Z |
| Read-only RPC | 429 | General rate limit | 18,393 | 0 | 2026-10-06T00:39:42.000Z |
| Read-only RPC | 502 | Upstream connection/request failure | 10 | 0 | 2026-09-30T07:43:31.000Z |
| Read-only RPC | 504 | Upstream timeout | 1,556 | 0 | 2026-10-04T05:51:42.000Z |
| Transaction lookups | 404 | Record not found | 346 | 0 | 2026-10-05T23:53:27.000Z |
| Transaction lookups | 429 | General rate limit | 6,256 | 0 | 2026-10-06T00:39:40.000Z |
| Transaction lookups | 502 | Upstream connection/request failure | 2 | 0 | 2026-09-30T07:43:17.000Z |
| Transaction lookups | 504 | Upstream timeout | 5,533 | 0 | 2026-10-05T20:01:21.000Z |
For rate limits, clients should respect Retry-After, reduce concurrency, and avoid repeated full-history scans. The breakdown distinguishes the general limit from the stricter address-history limit.
Node readiness
| Network | main | HSD version | 8.99.0 |
|---|---|---|---|
| Full node | Yes | Non-pruned | Yes |
| Transaction index | Ready | Address index | Ready |