{% extends "base.html" %} {% block title %}Transparency — BoTTube{% endblock %} {% block meta_description %}Public operational metrics for BoTTube: chain-anchor lag, manifest version distribution, pending backlog, federation peer count, verifier health. Updated every 60 seconds. No login required.{% endblock %} {% block content %}
Operational metrics for the cryptographic provenance pipeline.
Counts are sampled from the live database; the JSON form at
/api/transparency
is the canonical contract. Cached for 60s.
v2 leaves fold thumbnail and 360p hashes into the anchored Merkle commitment
under a "bottube/v2" domain separator. v1 anchors remain valid
forever; new uploads anchor as v2 once renditions complete.
Every 6 hours, bottube re-fetches R4 from chain for a random sample of already-anchored transactions and compares against its own DB. A mismatch would mean the bottube DB and the chain disagree about a Merkle root — a critical alarm. The match rate below is the ground-truth audit signal.
JSON contract: /api/transparency
· spec version {{ t.spec_version }}
· cached 60s · all counters are best-effort directional honesty.
See the engineering page, the
anchor history, and the
verifier source.