Try to backdate a record

Move the device time back on a sample record in GuardHelm’s production format. See what happens to the signature, the chain and the receipt.

This sample ships its records and a demonstration phone key, so your browser runs all three checks. On a real receipt anyone can repeat one of them, GuardHelm’s countersignature, with any ES256 library and the published keys. The receipt page also runs it in the reader’s browser. That the phone signed it and that it follows the record before are GuardHelm’s checks, reported on the receipt page.

Signatures not checked

Signed receipt

Sample record, demonstration keys

Record 43

Checkpoint scan at North Stairwell, level B2

Site
Riverside Tower
Post
North Gate
Activity
Checkpoint scan
Device time
02:14:07 EDT
Server time
02:41:30 EDT
Server sequence
88412

Unsigned sample labels: the site, post and checkpoint names and the display zone (America/New_York).

Change the device time on record 43

Now 02:14:07 EDT

  1. Device signature

    The demo phone key verifies the signature on the original record.

  2. Chain link

    Record 44 names this record’s fingerprint.

  3. Countersignature covers this record

    The receipt names this fingerprint and records a server time of 02:41:30 EDT.

A valid receipt shows

  • The enrolled phone signed it
  • Whether it follows the record before it
  • GuardHelm received it at the server time

It does not show

  • Who was holding the phone
  • That the phone’s clock was correct
  • The hours that will be billed

When a client disputes a shift

QuestionScreenshots and PDF exportsGuardHelm
What the client getsA copy you madeA link to the signed record
Who vouches for itYour company, the party in the disputeGuardHelm’s signature, checked against published keys
If it was edited laterYour client can’t tellThe check fails
Technical details

A receipt is the ASCII string guardhelm.receipt.v1, a line feed, then RFC 8785 canonical JSON, signed with ECDSA P-256 and SHA-256 (ES256). The signature is 64 raw bytes. Records signed on the phone use the same scheme with the tag guardhelm.event.v1, so any ES256 library can repeat these checks on this sample. Device keys are not published, so on a real receipt it can repeat one: GuardHelm’s countersignature.

Receipt, signed bytes
{"accepted_at":"2026-10-14T06:41:30.052Z","event_hash":"34c5a6cf3d374e8800dc73ec6a76c1c32559a862e22ec7b9b6aa1ad5e1633754","event_id":"45d6730e-8fe4-45a1-a568-3a9f2c047898","ingest_ordinal":"88412","schema_version":1,"server_key_id":"1f7ca53b-a051-4b39-a139-cd7242eb21d5","tenant_id":"b7f8ecaa-c8e9-4ee9-babb-3e3c3089cbd7"}
Receipt signature, base64
dkneV1q3JAJbalRvhRIkcHz46k8RNTUNCuRUsMDaSwwutJTjB1sDGtoNiI5KPB8Yw6JWKef9OHqnPIE8Y3wVKg==
Record 43, bytes under test
{"actor_id":"577bf3d0-b549-4566-8e50-287038345bea","body_commit":"a1742b20438019f58c3f89337c0a467c8000bf65f5b3bae08c05b460f2472a47","boot_id":"b3160ae8-db22-41a7-8c3f-9ae2639999c4","captured_at":"2026-10-14T06:14:07.193Z","chain_id":"89467612-f899-48d0-957f-fb45e273f108","device_id":"c0b5be7a-b718-4041-9ab6-32813d5a4c45","elapsed_ms":19017387,"event_id":"45d6730e-8fe4-45a1-a568-3a9f2c047898","key_id":"9942f12a-c012-4586-a738-5a5eb6aebed4","kind":"checkpoint_scan","media_digests":[],"origin_kind":"field","prev_hash":"3f587714fd0fef2b652026b5b04d69ea2f206f14bd48d4f8a85216d7492e9171","schema_version":1,"seq":43,"shift_id":"17cd39b6-2f81-4d16-a254-e6599ab484fb","signer_kind":"device","site_id":"56b7dc8d-8b50-4d30-b5a5-409e6f8e7f7d","tenant_id":"b7f8ecaa-c8e9-4ee9-babb-3e3c3089cbd7"}
Demonstration public keys, JWK
[
  {
    "kty": "EC",
    "crv": "P-256",
    "x": "GcUORkfcjAHaQuBZyXC6TTtNvUTxpRNSAaSLP6c3nJE",
    "y": "_NxWSWyGG42TfHByvMed5rIROT0D8Rd3lHW-Q6n37D0",
    "kid": "9942f12a-c012-4586-a738-5a5eb6aebed4",
    "alg": "ES256",
    "use": "sig",
    "guardhelm": {
      "purpose": "device",
      "demo": true
    }
  },
  {
    "kty": "EC",
    "crv": "P-256",
    "x": "17oPDnMQIxi6BVvRqbXiedvueoIe6H7VN5WulAk9D48",
    "y": "PNIjGynsdqekYmuPDVtwwejxOzdTRP9pk91MDzckhnI",
    "kid": "1f7ca53b-a051-4b39-a139-cd7242eb21d5",
    "alg": "ES256",
    "use": "sig",
    "guardhelm": {
      "purpose": "receipt",
      "demo": true
    }
  }
]

These sample records were produced by GuardHelm’s own signing code using throwaway keys. They do not describe a real company, guard or site. Customer receipts are verified against the keys GuardHelm publishes.

What the check does

Each record is signed with a key held on the guard’s phone, and GuardHelm checks that signature when the record arrives, then countersigns it. Anyone holding a receipt can check GuardHelm’s countersignature against its published keys, without an account and without our cooperation. If a single byte has changed, the check fails.

Receipts you have shared stay checkable after you leave, or if GuardHelm shuts down, because checking one needs only the receipt and a copy of GuardHelm’s published keys.

Back to GuardHelm

Check a real receipt

To check GuardHelm’s signature, you need the receipt file, the published keys and an ES256 verifier. No account is needed.

With GuardHelm’s verifier

  1. On the receipt page, open Verify it yourself and download the receipt file.
  2. Download verify-receipt.ts. It needs Node 22.6 or later and no npm packages.
  3. Run its self-test, then check the receipt file:
node --experimental-strip-types verify-receipt.ts --self-test
node --experimental-strip-types verify-receipt.ts --bundle receipt-8f4c21b73ad9.json --jwks https://api.guardhelm.com/v1/verification-keys/jwks.json

Exit code 0 means the supplied checks passed. Code 1 means the signature or timestamp proof did not verify. Code 2 means a check could not finish. Code 3 means the signature holds but the bytes are not canonical.

With any ES256 library

  1. Take the receipt bytes exactly as they are: server_receipt.canonical in the receipt file, or Receipt bytes in the page’s technical record. Do not parse and rewrite them.
  2. Read server_key_id from inside those bytes. In the published keys, take the key whose kid is that id, and check that its guardhelm.purpose is receipt. A key listed under revoked_keys no longer counts.
  3. The signed input is the ASCII text guardhelm.receipt.v1, one line feed, then the receipt bytes, as UTF-8.
  4. Check the signature with ECDSA on P-256 and SHA-256 (ES256). It is 64 raw bytes, r then s, in base64. A tool that expects ASN.1 DER, such as openssl dgst, needs it converted first.
  5. Check that the receipt is for the record you were sent: its event_hash is the fingerprint on the receipt page, and its accepted_at is the server time.

If the key is not in your copy of the published keys, fetch them again past any cache before concluding anything. A new key is published before it starts signing.

Check an independent timestamp

If the receipt includes timestamp responses, the verifier also needs OpenSSL and the authorities’ certificates. Follow the offline verification recipe to obtain the certificates independently, then add --tsa-trust ./trusted to the command above.

Each verified response shows that the signed receipt existed by that authority’s time. It does not establish when the guard was at the site. Without a verified response, there is no independent time.

Test vectors

Signed once with a key made for the purpose, whose private half was discarded. They describe no real company, guard or site, and the key is not one GuardHelm signs with.

Receipt bytes
{"accepted_at":"2026-03-14T09:26:53.589Z","event_hash":"5d41402abc4b2a76b9719d911017c592a1b2c3d4e5f60718293a4b5c6d7e8f90","event_id":"01936f2a-7c58-7a1b-9e44-2d8c0f5b3a97","ingest_ordinal":"41","schema_version":1,"server_key_id":"9f2c1e6a-4b70-4d18-9a3e-1c5f80b2d743","tenant_id":"3a7d5c92-8e41-4b6f-90ad-6f2b1c4e8d05"}
Signature, base64
gOKlzY8pNJiABhYqdN9nLUdPCV4bm++ZdtPFvv8wJyheCvNHXmsbvSDKZNE1Q7rsuDrYOO+Uhy9fgE/gTFF5nw==
Receipt key, JWK
{"kty":"EC","crv":"P-256","kid":"9f2c1e6a-4b70-4d18-9a3e-1c5f80b2d743","x":"AlFo0yCTqgyCfVldRTAc6FGZFGhPkYX4wS_ylDRP3-o","y":"kTp63Ue6qt0anK-C9uECPyBFeU1t5imscM7CF4Lm77I"}

The receipt bytes are RFC 8785 canonical JSON with two narrowings: numbers must be safe integers, and no value may be undefined. Keys sort by UTF-16 code unit, which a plain string sort does and JSON.stringify does not. Each input gives the output under it.

{"b":1,"a":2}
{"a":2,"b":1}
{"é":1,"z":2,"A":3}
{"A":3,"z":2,"é":1}
{"10":1,"9":2,"1e3":3}
{"10":1,"1e3":3,"9":2}
{"nested":[1,{"y":null,"x":[true,false]}],"":0}
{"":0,"nested":[1,{"x":[true,false],"y":null}]}