Research note / Cycle 021
A receipt dated too late
An internal desk ranking and a five-case policy check show why a receipt created after a change, or signed by the same office, cannot serve as an independent first commitment.
The first moment of challenge
Lumen’s internal deputy exercise showed that a request could be held, acknowledged and checked without silently authorizing a restoration. It could not show whether anyone outside the office could later tell that the office had replaced both of its retained copies. On February 8 Chen and Haddad asked when such a challenge would first become possible.
At an internal desk they ranked five hypothetical receipts written on cards: held outside and dated before the change with a matching digest; signed inside the office; dated after the change; dated before with a differing digest; and absent. Only the first could support a claim of independence, and only if its stated properties were true. No key was generated, no digest of a Lumen record was computed and no outside party was contacted.
A toy gate and its limits
The same five cases were run through a software predicate that passes a receipt only if it precedes the change, comes from an outside signer and matches the record. One case passes. Removing any one of those three conditions from the passing case makes it fail. The cases are constructed Boolean inputs, so the one pass grants only what the input assumes. It is not a test of any Lumen system.
RFC 9162 on Certificate Transparency is a limited analogy: its consistency checks depend on retained history, and its own discussion of divergent views shows why a single office’s assurance is weak. NIST’s key-management recommendation treats the ownership and protection of keys as part of what a signature means. Neither source describes a Lumen log, procedure or implementation.
An unsigned specification
The pair drafted, but did not send, a custody specification that asks four things of a future outside holder: who owns the signing key, where the timestamp comes from, what was retained before any rewrite and who may challenge the record. The deputy’s permissions stay read-only and internal. Recovery authorization and independent history remain separate questions.
This follows Who can hold the second copy?, which showed that a delegate in the same office adds operational continuity rather than an outside witness.
Results at a glance
| Constructed receipt | Dated before the change | Outside signer | Digest matches | Passes toy gate |
|---|---|---|---|---|
| outside, earlier, matching | yes | yes | yes | pass |
| same-office signer | yes | no | yes | fail |
| receipt after the change | no | yes | yes | fail |
| digest conflict | yes | yes | no | fail |
| no receipt | no | no | no | fail |
External research and methods
- Certificate Transparency Version 2.0 · Ben Laurie, Eran Messeri and Rob Stradling · RFC 9162, Experimental (2021-12). Sections 2.1.4, 8.2–8.3 and 11.3: consistency and split-view limits.
- Recommendation for Key Management: Part 1 – General · Elaine Barker, National Institute of Standards and Technology · NIST SP 800-57 Part 1 Revision 5, final (2020-05). Publication abstract: key storage, protection and management responsibilities.