TgWitness / Documentation

Repository / docs/ROADMAP.md

TgWitness roadmap

TgWitness / Documentation · Project reference

Project reference

Reviewed 6 November 2026. Implemented capabilities and their qualification are in Current status; shipped changes are in the changelog. This page describes remaining work, not the contents of a published download.

On this page

Now: 0.9 preview source#

Account workspaces, observing what Telegram delivers, interaction records, media, signed exports, scoped panel tokens, proxy policies and a separate witness that checks freshness and continuity. It only covers what the account and collector actually receive.

Before each release we:

  • run backend and browser checks on the release commit and write down what failed or wasn't tested;
  • build source, wheel and Windows portable from that same commit, look inside and publish SHA-256 first;
  • keep sessions, credentials, journals and test output out of the source archive;
  • reject broken OpenTimestamps trees and report Bitcoin attestations as bitcoin-unverified (use ots verify for the real check); RFC 3161 still needs the recipient's --tsa-ca;
  • mark English fallbacks where translations are still missing.

Next: qualify and connect existing workflows#

Other work runs alongside, each item judged on its own test:

What Done when Status
Long history loading Signed resume, shared waits, Takeout and media recover together Implemented; controlled live acceptance pending
Simultaneous live and backfill Live update intake remains durable while older history is read, with explicit account ownership and crash tests Open; these tasks currently require separate time intervals on one account
Complete source list Skipped and later-added chats are visible, only failed ones retry Open
Everyday reading Search, jumps by date and context, topics, gallery, forwards, reactions, versions Search, versions and context implemented; complete reading workflow remains open
Distributed export date boundaries Every message at the inclusive start survives acquisition; signed chunks remain reusable after pause Shipped; regression tests and live two-account pause/resume with 160 matching public messages
Distributed export throughput Current-run acquisition rate, separate stage durations, and resume-safe message counts Shipped; tests, browser check and bounded live one/two-account comparison in two public supergroups
Connection identity and retry safety Imported settings survive restart; platform defaults fill gaps; connection diagnostics report server responses; server-requested pauses survive reconnects Shipped
Independent login from an imported session Opt-in QR authorization keeps the donor intact, retains an interrupted candidate and supports 2FA Implemented; live-checked with Telethon, Pyrogram and TData donors, including 2FA and concurrent independent authorizations
Voice messages Local transcription and search, original stays Shipped
Accounts and access Revoking access stops reading, nobody sees other people's chats Shipped
Offline handover Recipient reads and verifies without our server Shipped
Operations and cost Published CPU, memory, disk and recovery numbers Search benchmark and CPU network checks recorded; sustained combined-load qualification open
Export request diagnostics Identify the method and retain the full FloodWait deadline with argument-free client-call counters Implemented locally; offline checks and dated live measurements. Separate learned method budgets and controlled fleet scaling remain open
Large-list export qualification Text-only acquisition makes no photo requests; ID rechecks share pacing; completed archives and resumed pages verify 50-source qualification completed: 48 verified archives, 3,598,381 records, four pause/resume checks; two unavailable usernames. Three fixes tested locally. Large archives have sampled content checks, not complete second passes
Distributed Takeout history Public-chat export reuses validated private Takeout handles, keeps signed receipts and reduces empty requests Implemented locally; protocol, recovery, archive and browser tests. Live speed not yet measured; limits and scope
Distributed page checkpoints Resume within an interrupted chunk from verified pages without weakening observer binding Implemented locally; 100-message checkpoints, standalone verification, crash/disk/cancellation/tamper tests and old-plan compatibility. Four live pause/resume checks retained pages; controlled recovery-cost comparison remains open; details
Independent verification Rewritten chain, cut tail, key change or missing witness gets caught Shipped
Chat archive comparison Full saved records determine equality; content-based candidates do not claim equality Implemented locally; signed-archive regression tests cover metadata, full text, unknown fields and signer checks

Importing third-party Desktop archives, device-cache dumps and recovered offline records is outside this roadmap. TgWitness records its own observations. Writing Desktop-compatible JSON from an account acquisition remains supported; see account export.

The witness already signs checkpoints and binds fresh challenges. Remaining controller work must qualify the complete path with a real collector:

  • every response bound to a fresh challenge, the registered collector key and a previously witnessed head;
  • the observer set fixed when an investigation is registered, missing observers stay visible;
  • outgoing receipts and jobs saved transactionally, survive restarts, retry with backoff;
  • receipts exportable for offline checks, only metadata, commitments and signatures go to the witness;
  • no free hosted pilot until resource use is measured.

Done when restarts, lost connectivity, repeated responses, a key change and an export with an unwitnessed tail all stay checkable from the saved receipts.

Next: independent observation and offline review#

  • Qualify the implemented opt-in browser, AyuGram and Trusted Live previews with permitted test accounts. Each keeps its own login, key and journal. A scrolled-away message must not be treated as a deletion.
  • Offline replay of captured material in a browser, with clear marks for missing media.
  • Preserve native-export attachments in Trusted Live and reduce the manual work needed to link visible messages to frames, without inventing IDs from pixels.
  • Match message IDs and versions across observers and keep disagreements. Reading the first collector's database is not a second observation.

Done when a test chat with sends, edits, deletes, changed buttons and observer restarts looks right in the offline bundle.

Later#

  • A small Go audit agent for collector lifecycle, file hashes, config changes and access metadata. Losing the agent must look different from "nothing happened".
  • Hosted pilot only with isolated investigations, quotas, retention and admin audit.
  • External anchoring of witness history, full OTS verification, maybe hardware keys and observers run by other people.
  • Longer live runs, recovery tests, Linux/macOS installs and containers on real targets.

Signed receipts catch changes to history someone already witnessed. The next step extends that trust to the collector itself: the build that signed the record, and witnesses on separate hosts run by separate admins.

Proposed: trust in the build#

A recipient should be able to see which build collected the record, which journal it showed, which witnesses kept it and where the gaps are. Today the run receipt measures program files, the code check compares them with a public commit and the witness publishes checkpoints. Next, in order:

  1. Keep the implemented release manifest, SBOM and workflow attestations bound to the tested revision and run receipt.
  2. A durable outgoing queue on the witness that survives restarts and shows retries. A late delivery never counts as on time.
  3. Qualify the existing draft-release and guided GitHub capture workflows on each release candidate.
  4. GitHub as extra storage for hourly signed checkpoint blocks, no force-push.
  5. Several witnesses run by different people, visible key rotation.
  6. Live tests of restarts, lost connectivity, old backups and changed builds.

Not done yet either: threshold signing (FROST), a GitLab mirror, Nostr anchoring, co-signers.

Release automation#

The release pipeline provides draft → checked assets and attestations → publish, pinned inputs, a release manifest and installer provenance checks. Require these gates on the exact candidate. Queued or skipped jobs never count as passed checks.

The one-command preview installer follows the same rule: every main commit is checked, the exact signed package is installed on disposable Ubuntu and Windows hosts, and publication waits for application/security CI. Failed candidates leave the previous public download available. Public HTTPS acceptance can be dispatched separately against the published commit; this does not qualify Telegram capture or a user's existing server.