Certification of process and digest — Receipt r_495518e7519d472f

Issued 2026-11-22T00:41:45Z · https://alphacovenantholdings.com/r/r_495518e7519d472f · SHA-256 67f6174a381cb9fa6485431a4b53cde74e4e3672490b2bc0ac1955209ce5a0dc · read 2026-10-30T10:05:12.995661+00:00

1. The process, as described

On the read date and time stated, the platform queried the official public sources named in the receipt for the exact name and keys supplied by the requester, recorded what each source printed (or that it did not answer), assembled those rows into the receipt body as JSON, and computed the SHA-256 digest of that body. The digest, the receipt identifier and the read time were written to the receipt registry at that moment. The body of a published receipt is stored as issued; re-computing SHA-256 over the stored body reproduces the registry digest. Any later change to the body would change the digest. The platform's own key signs this certification; its public key is published in the DID document.

2. Hash verification

Stored body re-hashed at 2026-11-22T00:41:45.976664+00:00: 67f6174a381cb9fa6485431a4b53cde74e4e3672490b2bc0ac1955209ce5a0dc — matches the registry digest.

3. RFC 3161 timestamp over the digest

Issued by DigiCert at 2026-10-31T19:16:13+00:00, serial 30088977318170851302006876970360430796. Token: r_495518e7519d472f.tsr. openssl ts -verify -digest <sha256> -in token.der -token_in -CAfile <TSA chain> — the token is a standard RFC 3161 TimeStampToken over the SHA-256 given

4. Platform signature

Ed25519 under did:web:alphacovenantholdings.com:api:vc#key-1, public key at https://alphacovenantholdings.com/api/vc/did.json. proofValue zG8w4kwktYeAzngoqNLC3LWXTo4ptH9Bzhv7zU71tqzCwk3wktrgQUarJC31czrzVjjrUqKEoRMgZDVgt1ZSAQQe — sha256 of the JCS canonical form of this document without the 'signature' member. Machine form: JSON · Verifiable Credential.

5. The rules, as printed

Rule 902(13). Certified Records Generated by an Electronic Process or System. A record generated by an electronic process or system that produces an accurate result, as shown by a certification of a qualified person that complies with the certification requirements of Rule 902(11) or (12). The proponent must also meet the notice requirements of Rule 902(11).
Rule 902(14). Certified Data Copied from an Electronic Device, Storage Medium, or File. Data copied from an electronic device, storage medium, or file, if authenticated by a process of digital identification, as shown by a certification of a qualified person that complies with the certification requirements of Rule 902(11) or (12). The proponent also must meet the notice requirements of Rule 902(11).

Federal Rules of Evidence, Rule 902 (as amended Dec. 1, 2017)

6. Custodian declaration (template)

I, [name], [title] of Alpha Covenant Holdings, certify under penalty of perjury that the record at https://alphacovenantholdings.com/r/r_495518e7519d472f was generated by the electronic process described above, which produces an accurate record of what the named sources printed at the stated time; that the SHA-256 digest 67f6174a381cb9fa6485431a4b53cde74e4e3672490b2bc0ac1955209ce5a0dc was computed by that process at generation and recorded in the platform's registry; and that the copy furnished is authenticated by that digest. Signed [date].

What this is not

This certification describes the system and the hash. It does not state, and must not be read to state, anything about the party named in the receipt — no standing, status, finding or determination.

Whether this certification satisfies Rule 902(13)/(14), the notice requirement of Rule 902(11), or any state analogue in a given proceeding is for counsel and the court. The platform furnishes the process description, the digest, the timestamp and the signature.