Documentation / Start here

Sealing, anchoring, and external Time Stamping Authority (TSA) service

Understand local seals, independent timestamps, and how they work together in invoice evidence.

On this page

WorkSealed uses sealing to make changes to captured work detectable and optional anchoring to add independent time evidence. An external Time Stamping Authority (TSA) service supplies that time evidence.

The terms at a glance

Term Meaning in WorkSealed
Fingerprint, or hash A digital summary of protected data. Changing that data changes the fingerprint.
Sealing Protecting completed work records with fingerprints and connecting them to signed history on your Mac.
Audit history The signed sequence of events that records how work and evidence were created or changed.
Audit block A group of audit events with a combined fingerprint, called a block root.
Anchoring, or external timestamping Obtaining independent time evidence for a sealed block’s fingerprint. These names describe the same feature in WorkSealed.
External Time Stamping Authority (TSA) service An independent service that issues signed timestamp receipts.
Timestamp receipt The external Time Stamping Authority (TSA) service’s signed statement that a particular fingerprint existed by the stated time.

Sealing: protect the recorded work

Sealing happens locally as completed work records are saved. It does not require an external Time Stamping Authority (TSA) service or an internet connection.

WorkSealed uses:

  • Record fingerprints: detect changes to protected captured data.
  • Signed audit events: connect records and supported changes to the app’s history.
  • Inclusion proofs: let the verifier check that an event belongs to a particular sealed block.

Sealing does not remove normal editing controls. You can still make supported changes, such as moving an eligible work log or changing its billable status. Those changes are recorded separately rather than silently rewriting the original captured evidence.

Local sealing lets a recipient check consistency and signatures. By itself, it does not provide an independent time reference: the signatures come from the app’s signing key, not an outside clock.

Anchoring: add an independent time reference

Anchoring connects a sealed block’s fingerprint to a time supplied by an independent authority.

When external timestamping is enabled:

  1. Audit events accumulate into a block.
  2. WorkSealed closes the block when its time or event-count limit is reached.
  3. It sends the block’s fingerprint to an external Time Stamping Authority (TSA) service.
  4. The external Time Stamping Authority (TSA) service returns a signed timestamp receipt.
  5. WorkSealed stores the receipt and includes it in relevant evidence exports.

A timestamp covers a block, rather than making a separate network request for every work log. Records are linked to that block through the signed history and inclusion proofs.

Example: a record reports work at 09:05, and its block receives a timestamp at 09:20. The receipt establishes that the block’s fingerprint existed by 09:20. It does not independently establish that a person was working at exactly 09:05.

External Time Stamping Authority (TSA) service: issuing receipts

An external Time Stamping Authority (TSA) service receives a fingerprint and returns a digitally signed receipt using the RFC 3161 timestamp protocol. WorkSealed includes the following pre-configured providers, all enabled in the provider list:

Provider Timestamp endpoint
FreeTSA http://freetsa.org/tsr
DigiCert http://timestamp.digicert.com
Sectigo http://timestamp.sectigo.com

Manage providers and the timestamping mode in Anchoring settings.

The external Time Stamping Authority (TSA) service receives:

  • The block fingerprint: the value being timestamped.
  • Connection information: it can observe your IP address and the request time.

The timestamp request does not send:

  • Client or task names.
  • Hourly rates or invoice amounts.
  • Window titles or work-log contents.

The external Time Stamping Authority (TSA) service does not review your work or approve your invoice. Its role is to issue time evidence for the fingerprint.

How the pieces reach your client

The evidence chain is:

  1. Tracked work produces completed work records.
  2. Sealing fingerprints records and connects them to signed audit history.
  3. Blocks group audit events under combined fingerprints.
  4. Optional anchoring obtains external Time Stamping Authority (TSA) service receipts for those fingerprints.
  5. Invoice export bundles the relevant records, signatures, proofs, and available receipts.
  6. Browser verification checks the invoice and its supporting evidence locally, including offline.

An internet connection is needed to obtain a new external receipt. Your client does not need a connection to run the downloaded verifier against receipts already included in the package.

Offline mode and pending timestamps

Local sealing and external anchoring are separate. Missing receipts do not mean that tracking or local sealing has stopped.

Situation What remains available Independent time evidence
External timestamp received Tracking, sealed records, and signed invoice exports. The included receipt covers its block.
External timestamp pending Tracking and local sealing continue; you can export with the pending state disclosed. Missing for blocks still awaiting receipts.
Offline only Tracking, local sealing, and signed invoice exports without external Time Stamping Authority (TSA) service requests. No independent timestamp for work without receipts.

If a provider is unavailable, a receipt can remain pending. During export, use Retry anchoring or Export anyway when offered.

  • Retry later: once a receipt is obtained, create a new export to include it.
  • Already shared ZIPs: do not update automatically.
  • Mode changes: affect future requests; they do not remove receipts already stored.

Choose the mode and providers in Settings → Anchoring.

What these checks do not prove

  • Who did the work: records and timestamps do not identify the person at the keyboard.
  • Work quality: evidence does not judge whether the result meets the client’s expectations.
  • Manual charges: a signed manual invoice line has no captured-work evidence behind it.
  • Sender identity by itself: a signature identifies the holder of a key. Share the client’s verification code through an agreed channel to establish key continuity.
  • Full external Time Stamping Authority (TSA) service certificate trust in the browser: the verifier checks that a receipt covers the block root and reads its signed time. It does not perform full certificate-chain trust validation; the package’s README.txt explains additional checks.

Continue with How it works, configure Anchoring, or inspect the sample evidence package.

Need a hand? Contact support.

Screenshot preview

Open full-resolution image