Registered receipt
r_459623f95b4b4d62
Read 2026-10-03T05:33:36.926657+00:00 · name not published in the registry (the default unless the requester opts in) — id, time and hash recorded
SHA-256 da91e2b6fa8f2e8653f7140392199313cd294ba45a618c0c4f4bb91b0f66ba64
Signatures over this hash: Ed25519 (registered before the signature set existed) · check · what signs our records
Cite as: Alpha Covenant Holdings, Receipt r_459623f95b4b4d62 for (name not published in the registry), read 2026-10-03T05:33:36Z, SHA-256 da91e2b6fa8f2e8653f7140392199313cd294ba45a618c0c4f4bb91b0f66ba64, https://alphacovenantholdings.com/r/r_459623f95b4b4d62
Checks read: leie, sam, ofac, state, usaspending, fac, ocr, echo, csl, fda_debar, sec, irs, oig_cia, dea_actions · not read: none · crosswalk edges 2 · keys supplied uei
Ledger for this key: UEI NL6ZAHMLKLZ6
File statement for this organization: NL6ZAHMLKLZ6 — every receipt and anchored document, signed, one page.
For the file: Certification of process and digest (FRE 902(13)/(14), RFC 3161 timestamp) · Verifiable Credential
Would this receipt satisfy your file?
One tap. Read by the owner the same hour; not published, not a review.
Decision record
The receipt says what the files printed. This says who looked, what they decided, and which payment, award or contract it was for — hashed, countersigned, appended under the receipt.
Questions that ask for an eligibility, compliance, legal, approval or risk call are declined; those decisions belong to your officer, auditor or counsel.
Retention line for the file this receipt sits in
Pick the rule your file is kept under and give the date its clock starts. You get the rule's own words and the date the period runs to — arithmetic, outside the signed body. Not a disposition status.
Clock starts at: submission of the final expenditure report (or, for awards renewed quarterly or annually, the quarterly or annual financial report). 2 CFR 200.334
Anchor your own document beside this record
Your checklist, certification or subcontract stays with you. Your browser computes its SHA-256; only that hash, a label and the document's date are recorded in the same transparency log as the receipt. Proof the document existed unchanged on that day, next to what the source printed — without us ever holding it.
Embed this receipt
A badge that prints the id, read date and hash prefix and links here. It says a receipt was registered; it is not a clearance or a seal of approval.
<a href="https://alphacovenantholdings.com/r/r_459623f95b4b4d62"><img src="https://alphacovenantholdings.com/api/receipts/r_459623f95b4b4d62/badge.svg" alt="Registered receipt r_459623f95b4b4d62" width="360" height="56"></a>
Prove a copy matches
Paste the receipt JSON you hold. Its hash is recomputed and compared with the registered SHA-256. Nothing is stored.
Transparency log: this receipt's hash is a leaf in the registry's append-only Merkle log (RFC 6962 construction; signed tree heads). Inclusion proof · checkpoint · witnesses · Evidence Record (RFC 6283). It proves the registry recorded this hash then and has not altered it — not that any agency's statement is true. Each tree head is timestamped by independent public RFC 3161 authorities and open to C2SP witness cosignatures.
Was this receipt built for your office? The roster is the same read on every vendor, monthly, with the diff — order on invoice or PO, quote in one step. Prices.