trustbeat
Anchor files to qualified eIDAS timestamps and verify the proofs offline.
A single static binary. Your files never leave your machine — only their SHA-256 digest is transmitted.
Part of TrustBeat — digital trust infrastructure for the EU. Prefer a library? Python, TypeScript, Java, C# and Go SDKs: trustbeat.eu/en/sdks.
$ trustbeat anchor contract.pdf --wait
✓ sha256 9f2a1c…4b7e contract.pdf
✓ submitted 01KNBQMYC0AQ7KA561TNKK71GJ
✓ anchored
time 2026-07-22T09:14:03Z
tsa SK TIMESTAMPING UNIT 2025E
proof contract.pdf.proof.json
$ trustbeat verify contract.pdf.proof.json contract.pdf
✓ document SHA-256 matches the anchored hash
✓ merkle 14 path step(s) re-derive the batch root
✓ timestamp token imprint (SHA-256) equals the batch root
✓ signature signed by SK TIMESTAMPING UNIT 2025E
PROOF VALID
Install
No Rust toolchain? Grab a prebuilt binary for Linux, macOS or Windows from
Releases — every release
ships a fully static x86_64-unknown-linux-musl build for containers, with
SHA-256 sums and a qualified timestamp over the artifacts themselves.
Verification works offline, forever
trustbeat verify makes no network calls and needs no API key. It re-derives
the cryptography from the proof bundle alone:
| Check | What it proves |
|---|---|
document |
SHA-256 of your file equals the hash in the proof |
merkle |
The proof path re-derives the batch's Merkle root |
timestamp |
The RFC 3161 token's messageImprint is that Merkle root |
signature |
The TSA's signature verifies against the certificate in the token |
The timestamp check is the one that matters most: it's the join between your
document's Merkle path and the qualified token. Without it, a valid token could
be paired with an unrelated tree.
This means a proof outlives us. If TrustBeat disappeared tomorrow, every proof
ever issued stays verifiable with this binary — or by hand with openssl, see
MANUAL_VERIFICATION.md.
Supported token algorithms
Timestamp tokens vary by TSA, so verify handles both common signature families:
| Supported | |
|---|---|
| Signature | ECDSA (P-256, P-384) with SHA-256/384/512; RSA PKCS#1 v1.5 with SHA-256/384/512 |
| Message imprint | SHA-256, SHA-384, SHA-512 |
| Not supported | RSA-PSS, Ed25519, curves other than P-256/P-384 |
Anything unsupported fails closed — it is reported as an unsupported token and the proof is marked invalid. A token is never accepted because its algorithm wasn't recognised.
The three algorithm slots in a token are independent and routinely differ: the
message imprint may be SHA-256 while the SignerInfo digest is SHA-512 and the
signature is ecdsa-with-SHA512. For ECDSA the prehash is chosen by the
signature algorithm OID, not the SignerInfo digest.
Scope limit: certificate chains
verify checks that the token's signature is internally consistent against the
certificate embedded in the token. It does not validate that certificate's
chain up to a trusted eIDAS root, and does not check revocation. For a full
qualified-status assessment against the EU Trusted List, use the API's
/v1/verify/signature endpoint or the portal.
Commands
trustbeat anchor
Anchors are batched into a Merkle tree and timestamped roughly every 10 minutes,
so --wait can take that long. Without --wait the command returns instantly
and you collect the proof later with trustbeat proof <id>.
trustbeat verify
|
Exit codes: 0 valid, 1 invalid, 2 usage/IO error.
trustbeat proof
Exits 3 when the anchor is still pending.
trustbeat hash
Configuration
anchor and proof need an API key (get one).
verify and hash never do.
Resolution order:
--api-key/--api-urlTRUSTBEAT_API_KEY/TRUSTBEAT_API_URL~/.config/trustbeat/credentials
# ~/.config/trustbeat/credentials
api_key = tb_live_...
Scripting
Every command takes --json:
|
|
Colour follows NO_COLOR and is disabled when stdout is not a terminal.
Building from source
Documentation
Full API reference and guides at api.trustbeat.eu/docs.
This CLI covers file anchoring. The same qualified-timestamp infrastructure also backs:
| Tamper-Evident Logs | Sealed log trails for NIS2 Article 21 |
| AI Decision Anchoring | Provable records of model decisions |
| Audit Trail | Append-only, independently verifiable event history |
| EU Digital Identity | EUDI Wallet / eIDAS 2 credential verification |
| Signature Verification | Full qualified-status assessment against the EU Trusted List |
Free tier — 100 anchors a month, no card: trustbeat.eu/en/pricing.
License
MIT © Trustbeat s.r.o.