Qualified timestamps, RFC 3161, Merkle anchoring, and EU compliance evidence — written by the people building TrustBeat. RSS
How to get proofs for many documents out of TrustBeat at once: a ZIP from the portal, proofs with RFC 4998 evidence records from the API, daily evidence packages at high volume, and a preservation package for long-term archiving. None of them need TrustBeat to verify.
No, and eIDAS 2 does not change that. What Articles 41 and 42 require, what electronic ledgers (45k, 45l) add, and when each option fits.
How an RFC 3161 trusted timestamp works: request, token and verification, run with openssl and curl — and what makes a timestamp qualified under eIDAS.
The European standard for preservation services describes every service with two codes: what is preserved (PDS, PGD, AUG) and who keeps the evidence (WST, WTS, WOS). What they mean, why PGD can never be qualified, how to check a vendor's claim — and TrustBeat as a worked example.
The shortest path from a file on your desktop to a qualified eIDAS timestamp proof: one 3 MB executable, one command, and offline verification that needs no account. Install via Scoop or a direct download.
What to expect here: practical writing on eIDAS-qualified timestamps, RFC 3161, Merkle anchoring, and what NIS2 and DORA auditors actually accept as evidence.