Trust » Daily seal

Daily seal

Each night Fohrkast's records are sealed: one fingerprint, the root of a Merkle tree over the audit trail of every workspace, is signed by independent time-stamping authorities under RFC 3161. A night is listed once at least two of them have signed it.

The last 30 days

  1. 8 November 2026

    Fohrkast's records sealed

    Fingerprint (SHA-384)

    919292f5636f53c8c83e8cd29e4a00463ea98e3f6422d03e80d45b74de0956c7ef724e92fede92f7d2e613daf6998915
  2. 7 November 2026

    Fohrkast's records sealed

    Fingerprint (SHA-384)

    471362304d5ffd9168328b320c9fa9754cb6a2122e0a7ab065f90b20346491c3ea9ba1b14e4e214f186512c6fedf12cd
  3. 6 November 2026

    Fohrkast's records sealed

    Fingerprint (SHA-384)

    1579b55af8625f5fa14d65d14cbc5284a21fba4c9a0d48c13ca60aff428d2dfbf295970ef0dd7f278c796138703e4ac8
  4. 5 November 2026

    Fohrkast's records sealed

    Fingerprint (SHA-384)

    a027b7bfa390776c2a9f7414da55627c706438a8c70d087d384277379e3b3b064a40e5e20c99163af406bf4307090b9d
  5. 4 November 2026

    Fohrkast's records sealed

    Fingerprint (SHA-384)

    d348b94bad3997fe1f5f88e1f3a4b249cdb4e6a5625c7ebc18bf292bbc0159fb2ea32b2534d647e0a81ee314f283f979
  6. 3 November 2026

    Fohrkast's records sealed

    Fingerprint (SHA-384)

    4af575af2a7e289ccf660e103cb41362af22abaf511940d37fb6e98a6f1c1301bcb73f83d732550009615d6e3746890c
  7. 2 November 2026

    Fohrkast's records sealed

    Fingerprint (SHA-384)

    f013f689ea18c8196905001d143b2b93f4401bbdd93379b7d4506064679ffcb5c3c24b702c8d2d1696dd9d1b021d6cde
  8. 1 November 2026

    Fohrkast's records sealed

    Fingerprint (SHA-384)

    ecbf1724cce5ee4393f03514b7718ccaa5d6feff4b5fcab7c2bee01a9d95f07ff5561702427000d17d293f3b5a3b313a
  9. 31 October 2026

    Fohrkast's records sealed

    Fingerprint (SHA-384)

    4d6f12b3eca161566fd9fc82b705330062997ade7d48124fd15252e9ef9b3ca02aa28a84d1c914175e4e2fee7a39ffe8
  10. 30 October 2026

    Fohrkast's records sealed

    Fingerprint (SHA-384)

    e91edafbeea5c42a1e388d85cd2c963cfd6724e1fefe198f7a6e5c32f4c00f35a9e875442ecd94971fbadb6361fe2d6d
  11. 29 October 2026

    Fohrkast's records sealed

    Fingerprint (SHA-384)

    2ac732fc3d42d0d7f540392ac0ccb5b4977bfbf125d72ad87944f2d426644a37aebdc6ca05c2e3ed8664b109f19fd354
  12. 28 October 2026

    Fohrkast's records sealed

    Fingerprint (SHA-384)

    3bc60104d4ae537b722c7d5c5e2635436faec10f6e4127187abe864b317f30b553d6f9a2535b6a0830b966cc00496a81
  13. 27 October 2026

    Fohrkast's records sealed

    Fingerprint (SHA-384)

    4f7569a8081194a1f11e0dc8fddc5519b90e661b4f6f38b09fdcd0bbe7613f29d25399287d7b80b19475fc87577e2cdd

What the fingerprint covers

  • » One line per workspace with an audit trail: its id, its number of entries and the hash of its latest entry.
  • » Each line, preceded by the night's date, is a leaf of a Merkle tree (RFC 6962 hashing, SHA-384), and the root is the fingerprint. The lines stay with Fohrkast.
  • » The tree has a fixed depth of 20, so 2^20 slots, the same every night. Each line sits in a slot drawn from the night's lines, and each part of the tree without a workspace holds one padding hash, made from the night's lines and marked by its own first byte (0x02), so no line can stand in for it. Every proof is 20 hashes long, and the fingerprint is the same size, whatever the number of workspaces.
  • » Inside Fohrkast, each workspace's Administrator, Privacy lead and Auditor see that workspace's own line and the 20 hashes from it up to the fingerprint, and can recompute the fingerprint from them.
  • » The time-stamping authorities receive the fingerprint only.

How to check

  • » Download a night's signed token, for example as seal.tst.
  • » Read it: openssl ts -reply -token_in -in seal.tst -text. Message data is the fingerprint; Time stamp is the authority's time, in UTC.
  • » See who signed it: openssl pkcs7 -inform DER -in seal.tst -print_certs -noout lists the signing certificate and the chain the token carries.
  • » Check the signature: openssl ts -verify -token_in -in seal.tst -digest <fingerprint> -CAfile roots.pem. OpenSSL prints Verification: OK when the authority signed that fingerprint and its certificates lead to a root in roots.pem.
  • » Inside a workspace, the proof checks by hand: the SHA-384 of byte 0x00 followed by "<date> <line>", then, for each of the 20 steps, the SHA-384 of byte 0x01 followed by the left hash and the right hash. The last result is the night's fingerprint.
  • » For roots.pem, the operating system's list of root certificates (on Debian and Ubuntu, /etc/ssl/certs/ca-certificates.crt) or, for an authority whose root is outside that list, the root certificate that authority publishes.