Documentation / 16
Set Up a Telegram Evidence Witness Bot
A separate process checks your journal and posts signed checkpoints to a channel.
Two hosts, two signing keys
Telegram session
Collector signing key
signed answer →
Pinned collector fingerprint
Separate witness signing key
head 9c7d…head a4f2…Accepted: the count grows, the signature verifies and the key matches. The witness retains this new boundary.
Prepare a bot and a channel
Make a bot with BotFather and let it post in your channel. Run the witness somewhere else: another host, ideally run by someone else, is worth much more than a second process next to the collector.
Three steps in Extras
- Read-only access. Extras → Independent witness, create a token, save the file. It reads checkpoints and health, nothing else.
- Channel and interval. Telegram channel or Discord webhook, plus a collector address the witness can reach. Save the settings file.
- Launch. Put
witness.json,witness-token.txtandbot-token.txttogether on the witness host and run:
python -m tgwitness.witness run --config witness.json --check-config
python -m tgwitness.witness run --config witness.json
Wait for the first signed post in the channel, then save the witness fingerprint somewhere safe.
Discord instead? Save the webhook URL as discord-webhook.txt. One witness posts to one place; long checks arrive as a file on Discord.
Choose how often to publish
Posting every check gives a steady outside record: every five minutes is about 288 posts a day per workspace. Advanced settings can post only on changes or problems, use a proxy or a custom Bot API.
What does the bot actually attest to?
It asks the collector for a signed checkpoint, checks it against the expected key and keeps its own signed journal, including missed and rejected answers.
It checks the journal state, it doesn't watch Telegram itself. For that, run a controlled delivery test.
Check the evidence later
Keep the witness journal, the posts and the fingerprints. How to check them against the collector's export.