Verify
A rule only counts if it was fixed before its results were known. Here is how that is recorded and how you can check it yourself.
How a seal works
- Rule, configuration, plan and decision date are written down before the forward start, without any result on the data the decision will use.
- For each of these files the SHA-256 is computed: a fingerprint that changes completely if a single character changes. The seal file (.sha256) lists them; I confirm it, and it is committed to my repository.
- The code that books the shadow books is bound by its own hash, recorded in the registration contract.
- Two independent public timestamp authorities sign the SHA-256 of each seal file (RFC 3161). Their signed replies are here for download.
- On the decision date the forward results are measured against the criteria of the registration. Changes are possible only as a new, dated registration or amendment, listed in the register.
Check it yourself
With OpenSSL (on Windows it comes with Git for Windows). Example: the seal of AT-UT and its configuration.
# 1. Fingerprint of the configuration; compare with its line in the seal file
sha256sum schatten-atu-v1.json
# 2. Fingerprint of the seal file; compare with the register
sha256sum registrierung-atu.sha256
# 3. Show the timestamp: time and the hash it signs
openssl ts -reply -in docs--validation--registrierung-atu.sha256.digicert.tsr -text
# 4. Check signature and hash against the seal file
openssl ts -verify -data registrierung-atu.sha256 -in docs--validation--registrierung-atu.sha256.digicert.tsr -CAfile digicert-trusted-root-g4.crt
openssl ts -verify -data registrierung-atu.sha256 -in docs--validation--registrierung-atu.sha256.freetsa.tsr -CAfile freetsa-root.crt
Both checks end with “Verification: OK”. The root certificates are the published roots of the two authorities.
What the evidence shows, and what not
- The timestamps were created on 19 November 2026. They prove that the seal files existed unchanged from that day on. That they existed on the seal dates (18 October and 8 November 2026) rests on the history of my repository, which is private.
- Every new registration gets its timestamps on the day it is sealed.
- Files that are only listed with their hash can be released later; anyone can then check them against the hash and timestamp published today.
Code hash AT-UT
SHA-256 over 232 source files of the booking code, recorded in the registration contract: dcceddcbd55b0ddb86e58a0d9c453473b48bb11e25455dd612c85df204f301af
Downloads
Seal files
- docs/validation/nachtrag-etf-demo-atu.sha256
f8f832848d33975277164ab0c27c4fe06681103a3d1051128c55e6aae59bc8b3 - docs/validation/nachtrag-etf-eur-kurse.sha256
e50f10bee84933e426ead0f5f0a678386abc7a996a594ad26132ba98ef857bdf - docs/validation/nachtrag-etf-usd-kurse.sha256
4045d819b80b9d723bddfb5b8cfe29316671d268309bd4c87db3dbdcb4bf1069 - docs/validation/registrierung-atu.sha256
c31e3aa2011ed12bc26d88ae0434c93d935bd1db4334e317b893813e2e169659 - docs/validation/registrierung-etf.sha256
b5ce737fe1e692bc99c4dac9d08e5012e278a5e434c0e1a82f43c52a6fee4e27
Registration contracts and configurations
- config/schatten-atu-v1.json
8b8ad2827176a65729aa120feff7303f324e77c029b1f8f49fc0024e51626a7e - config/schatten-etf-v1.json
19c3422b48a7a5494f3ff25556739d2a094af5fac4e375e33cf1ab782a4d7ce7 - docs/validation/registrierung-atu.json
7ee7e60362664b40f9116373d15c789000524ffa6b174d07dee2c43ca8ffdce9 - docs/validation/registrierung-etf.json
b2cee0f2f743a2ce8159a66d81919f75a9bc3a9fc0f7191261a11206fa2f4fa4
Amendments
- docs/validation/nachtrag-etf-demo-atu.md
37c5ff23261b1d0d9a692c9aa4e6ecda23550390e68606c167e88dfac83d36ed - docs/validation/nachtrag-etf-eur-kurse.md
e66643541a29b71208a29b852fe493e3b1860977c6b911fcd4bde87f3de6a4d1 - docs/validation/nachtrag-etf-usd-kurse.md
518055ff278398b14399890e65bd4ab34790d29f3f7d8e72c83dd72d21b7b357
Root certificates of the timestamp authorities
- docs/evidenz/zeitstempel/ca/digicert-trusted-root-g4.crt
ce7d6b44f5d510391be98c8d76b18709400a30cd87659bfebe1c6f97ff5181ee - docs/evidenz/zeitstempel/ca/freetsa-root.crt
2151b61137ffa86bf664691ba67e7da0b19f98c758e3d228d5d8ebf27e044438
The timestamp replies are linked next to each file in the register.