TgWitness / Documentation

What has been tested →

TGWITNESS / REAL EXPORTS

56 329 messages.
Captured. Exported.

Two fresh Telegram exports, timed from collection to the finished archive. Explore the workspace, inspect the numbers and download a sample.

The interactive demo and sample use fictional messages. The measurements below come from real export runs.

TGW / 001

Recorded snapshot · not live monitoring

Checked at
Tested revision
92e539af
Text + metadata · signed archives
56 329Messages exported
160.531Messages/s · best collection run
2Signed export runs
3Servers inspected
Server AWARP · 2 accounts
27 030Messages exported
142.983messages/s
Collection only
189.043 s
Complete export
211.647 s
Server BWARP · 2 accounts
29 299Messages exported
160.531messages/s
Collection only
182.513 s
Complete export
206.650 s
01 /

Measured on real exports.

One new export per server, using two accounts on each. Text and metadata through WARP; attachments excluded.

messages/s
Server A142.983 messages/s
Server B160.531 messages/s
Server C
Not measured
—

Messages ÷ collection time. Preparation, selection and packaging are outside this interval.

No collection benchmark receipt for server C.

No reused records or duplicate IDs in either run. Server A also had a protected-source read running in the background. FloodWait pauses were respected: A · 4, B · 3.

Exact measurements & archive hashes
ServerMessagesCollection onlyComplete export
Server A27 030189.043 s
142.983 messages/s
211.647 s
127.713 messages/s
→
SHA-256 20e507fc68446680ed002fd486d0968a944ec0c71e02f937331ae2b19ab4cd66
Server B29 299182.513 s
160.531 messages/s
206.650 s
141.781 messages/s
→
SHA-256 824601b502762efaabb8ff9afdb1e8d7fff189862ef2cbc4d8d26d0d68c83e4c

Both archives passed verification with a pinned collector key.

02 /

All three, with the scope spelled out.

Journal integrity, file permissions, storage, network routes and running processes were inspected on every server.

A Inspected

Server A

Collection & export

8 vCPU · 16 GiB · Ubuntu 24.04

Journals checked
21
Journal events
4 517
Checkpoints
147

Fresh collection benchmark, archive verification and backup integrity checks.

B Inspected

Server B

Collection & export

8 vCPU · 16 GiB · Ubuntu 24.04

Journals checked
21
Journal events
1 993
Checkpoints
147

Fresh collection benchmark, archive verification and backup integrity checks.

C Inspected

Server C

Panel & nested VM

8 vCPU · 32 GiB · Ubuntu 24.04

Journals checked
14
Journal events
7 185
Checkpoints
973

Panel authentication, loopback binding and a nested VM inspected. No collection benchmark on this server.

Test results, scope & technical notes
03 /

Passes and gaps, side by side.

Latest result per pytest case, including reruns. Standalone browser and evidence suites are counted separately below; they are not added to the pytest total.

1 585Passed
3Failed
37Skipped

Three capture browser tests need the Chromium sandbox, which these containers do not provide; the sandbox stays enabled. The 37 platform skips are counted separately from passes.

  • Browser suites102 passed
  • Interface suites66 passed
  • Evidence suites15 passed
  • Website suites9 passed
  • Additional suites13 passed
04 /

Scope of this snapshot.

  1. 01

    Browser sandbox

    Three browser checks wait for an environment with the Chromium sandbox.

  2. 02

    Backup recency

    42 backup journals and 51,285 files passed integrity checks. At the snapshot, the latest backup was 3,507 events behind live collection.

  3. 03

    Network coverage

    24 of 40 routes qualified. The other 16 accounts stayed disconnected instead of falling back to a direct connection.

  4. 04

    Independent time

    The retained witness journal passed integrity checks. Its last event was at 07:27 UTC on 6 November.

  5. 05

    Security controls

    Key protection, account protection, durable storage and release controls are described in the security model; the open findings of this audit are listed in the signed report.

  6. 06

    Inspected servers

    The three inspected servers are the scope of this page.

  7. 07

    Measured workload

    Two public sources, two individual runs, text and metadata without attachment downloads. Server C ran without a collection-rate measurement. Each figure applies to its recorded workload.

05 /

A dated record, with a way back to the numbers.

Measurements by the maintainers, signed with the audit key. The JSON contains only aggregate data. Source and account identities, message contents, credentials and private archives are not published.

  1. Pin the source revision and verify the installed release.
  2. Collect into a new workspace, retaining zero reused records.
  3. Measure collection and complete-export intervals separately.
  4. Verify the archive against its pinned key; retain its SHA-256 digest.

Tested release 92e539af40d8-83e41104669e

Download the data ↓

SIGNED AUDIT / ENGLISH

Check the numbers.

The English report includes the measured results, open findings and a reproducible signature check.

The signature binds the report and its measurements to the audit key; a change to any signed file fails VERIFY.py. The report records the completed audit at 19:08 UTC; the infrastructure snapshot above was taken earlier.

Source receipt digests

These hashes identify the retained signed receipts of the measurements; the private originals are kept by the maintainers.

  • benchmark-1.json66cdf2db25901ee1f780a0e2d14b9b84888dbe525bff73bae19819b217f95d0c
  • benchmark-2.jsonad2978fe2a7563476da43293eaaf5f498ee12522f0ea3e401bc43205c64874d1
  • test-totals.json922cf87d9320b149f2fc6791fc05f98335ec0952f9258e6eaeff179aeef33bb1
  • infra-summary.json325d390ef752b15f44203f97348863e24f0f631fe88998d5e1f398a5311a9339

Each figure names its revision, workload and environment. A measurement that was not taken is shown as missing.

These guides describe the current implementation. Validation results and remaining gaps are documented separately. What has been tested →