Independent verification protocol

The book Proven Action claims that every decision of MITR, which checks the actions of agents built on artificial intelligence (AI), is written to a chain of receipts that an outsider can verify without trusting the owner of the server. Below is how to do it on the machine of the checker, which needs only Python 3 and, for the timestamps, the OpenTimestamps client.

An outside reviewer recomputes the receipt chain with a tool of their own, checks the time of the epoch with someone else’s client and compares the head of the chain without trusting the owner of the server.01 · STEP 1Integrity of the chainverify_chain_standalone.pycode 0: they agree1: they differ, 2: could not checkA verifier on the Python standard libraryrecomputes the anchors; it holds no MITR code.02 · STEP 2The time of an epochepoch 33timestampOpenTimestampssomeone else’s clientThe timestamp of the last epoch is checked withthe OpenTimestamps client, not the institute’s.03 · STEP 3The head of the chain agreesanchor of epoch 335,079 receipts=epoch filechain_ok: trueEpoch 33 holds 5,079 receipts; its line matchesthe file in every field but the witnesses.An outside reviewer recomputes the receipt chain with a tool of their own, checks the time of the epoch with someone else’s client and compares the head of the chain without trusting the owner of the server.01 · STEP 1Integrity of the chainverify_chain_standalone.pycode 0: they agree1: they differ, 2: could not checkA verifier on the Python standard libraryrecomputes the anchors; it holds no MITR code.02 · STEP 2The time of an epochepoch 33timestampOpenTimestampssomeone else’s clientThe timestamp of the last epoch is checked withthe OpenTimestamps client, not the institute’s.03 · STEP 3The head of the chain agreesanchor of epoch 335,079 receipts=epoch filechain_ok: trueEpoch 33 holds 5,079 receipts; its line matchesthe file in every field but the witnesses.
An outside reviewer recomputes the receipt chain with a tool of their own, checks the time of the epoch with someone else’s client and compares the head of the chain without trusting the owner of the server.

Step 1. Check the integrity of MITR’s receipt chain

curl -o verify_chain_standalone.py https://asi5.ru/console/verify/verify_chain_standalone.py.txt
curl -O https://asi5.ru/console/verify/gate_anchors-public.jsonl
python3 verify_chain_standalone.py gate_anchors-public.jsonl

The standalone verifier returns exit code 0 when all anchors match, exit code 1 with the epoch number if a discrepancy is found, or exit code 2 if the input files cannot be read; it relies solely on the Python standard library without a single line of MITR code and prints its diagnostic output in Russian.

Step 2. Check the time of an epoch with someone else’s client

curl -O https://asi5.ru/console/verify/gate-anchor-epoch-33.json
curl -O https://asi5.ru/console/verify/gate-anchor-epoch-33.json.ots
ots verify gate-anchor-epoch-33.json.ots

The OpenTimestamps stamp dates the anchor file by a block of the Bitcoin network. A new epoch is added once a day, the current number is shown at asi5.ru/console/verify/, and in the commands below the number 33 (25 October 2026) is to be replaced with the latest one. The stamp of the newest epoch waits a few hours for confirmation in Bitcoin, and until then ots verify reports that confirmation is pending, so the previous epoch can be checked instead, or the check repeated later. The OpenTimestamps client runs on Linux and macOS; on Windows it runs inside the Windows Subsystem for Linux (WSL).

Step 3. Compare the head of the chain

As a reproducible historical baseline checked on 26 October 2026: epoch 33 of 25 October 2026, 5,079 receipts in the anchor, head hash bca010ea76efd7290e5f4c7095d498786a49f3bf774b61e05c0d030829c04a1b, integrity flag chain_ok: true. The line of epoch 33 in gate_anchors-public.jsonl matches the file gate-anchor-epoch-33.json in every field except witnesses, because the list of witnesses is added to the chain after the stamp is made.

What these data cannot verify

The anchors prove that the chain has not been rewritten after the fact, but they do not prove that the decisions themselves, an admission or a refusal under a rule, were correct. For that, an auditor is given the chain of receipts and the texts of the rules in the SMT-LIB format used by solvers of satisfiability modulo theories (SMT), and the verifier replays each decision with any solver on the machine of the auditor.

In the historical epoch-33 baseline on 25 October 2026, replay gave 5,079 matches out of 5,079 decisions (on 14 October 2026, 4,958 out of 4,958); run by the institute itself, pending independent third-party replay. As of 15 November 2026, the live receipt chain holds 5,373 records across 55 completed epochs (56 published). For regulated Russian banks and critical information infrastructure, OpenTimestamps proofs are paired with accredited trust service time stamps and qualified electronic signatures under Federal Law No. 63-FZ. The verifier with the replay mode will be added to the open kit after the scientific paper of the institute is published.

Replay commands from the book (appendix B)

They are run by an auditor admitted to the server of MITR. The --date key sets the day of the report, and without it the last day is printed. The figures printed in the book refer to the date given in its Appendix B, so a replay shows the figures of its own day:

# liveness of the gate's services
systemctl is-active mitr-gate mitr-bot
# six basic claims and a line per tenant, for the day set by the --date key (without the key, the last day)
cd /opt/v && sudo -u v venv/bin/python scripts/gate_mode_report.py --six --date 2026-10-09
cd /opt/v && sudo -u v venv/bin/python scripts/gate_mode_report.py --tenants --date 2026-10-09
# price of a decision: the second line is the measurement of 26.09.2026, the last one is the latest
sed -n 2p /opt/v/data/logs/smt_latency_paper.jsonl; tail -1 /opt/v/data/logs/smt_latency_paper.jsonl
# the last anchor of the receipt chain of the gate
tail -1 /opt/v/data/gate_anchors.jsonl
# replay of all the decisions of the chain with the verifier for an outsider (25.10.2026: 5079 of 5079; 14.10.2026: 4958 of 4958)
cd /opt/v && sudo -u v venv/bin/python scripts/verify_chain_standalone.py data/logs/gate_actions.jsonl --anchors data/gate_anchors.jsonl --replay
# the first vocabulary rule adopted by the gate itself: receipt 305
grep -m1 'seq.: 305,' /opt/v/data/logs/gate_actions.jsonl