Public counters and network observations

The page footer reports aggregate page visits and release downloads as HTTP responses. A page counter increments for an HTTP 200 HTML GET served by the public Cloudflare edge. An archive counter increments for an HTTP 200 GET of release.tar.gz, including a versioned archive. HEAD, redirects, unsuccessful responses and partial-range responses do not count. These counters include bots, reloads and operator verification. They do not measure unique people, completed downloads, installed nodes, customers or adoption. A download may disconnect before its last byte arrives. Counter collection started with version 2.0.0; there are no invented historical visits.

The free Worker sends a random ID for each response to the existing protected origin. A retry uses the same ID. SQLite stores aggregate counts by public route and random request IDs to reject duplicate retries. IDs become eligible for pruning after 48–72 hours; cleanup runs on the next collected event, so inactivity can retain them longer. The IDs have no connection to an account, wallet, browser or session. TOKN's counter does not store IP addresses, cookies, fingerprints, user agents, referrers, query strings or document contents. It creates no browser tracking storage. The infrastructure provider still processes requests under its own service policies.

Only the protected origin enables collection. The public Worker rejects the internal ingestion route. Counts are best effort: background writes have bounded timeouts and never delay page delivery. At most 200,000 recent IDs are retained; new counts are omitted if this capacity is reached until older IDs are pruned. The SQLite database has a 50 MiB page limit. Aggregates survive container restarts; request IDs are pruned lazily, so a retry after retention could count again. Outages or abuse can distort counts. They are operational observations, not an attestation of demand. Anyone can inspect the aggregates at /metrics.

The explorer separately shows Connected peers from net_peerCount and Active validators from qbft_getValidatorsByBlockNumber. A peer is one connection seen by our RPC node; it is not a count of every network node. Several peers or validators may share one controller. Verified independent operators currently equals zero. The bootstrap operator controls the validator and administrative replica.

For operators: the Cloudflare gateway mounts state/metrics as its only counter storage, owned by its container UID 65534. Its TOKN_METRICS_DB setting enables the collector; leave it unset on public or Tor gateways. Do not publish this directory. Loss of the database resets the counters; recovery must preserve the real start time and never reconstruct an invented count. No paid analytics service is used.