# AFFIDAVIT OF RECORDS CUSTODIAN — KNOX-ANCHORED ELECTRONIC RECORD

**Template for use by counsel authenticating a Knox record under FRE 902(13) / 902(14).**

---

STATE OF _______________________
COUNTY OF ______________________

I, **[CUSTODIAN NAME]**, being duly sworn, depose and state as follows:

1. I am of legal age and competent to testify to the matters stated herein, and I have personal knowledge of the facts set forth below.

2. I am the **[TITLE]** of **[ORGANIZATION]**, and in that capacity I am the custodian of the electronic records identified in this affidavit.

3. The record attached hereto as **Exhibit A** (the "Record") was produced by the Knox Immutable Ledger operated by Bonis Systems LLC, a Wyoming limited liability company (UEI R2BPJDC5CBA3, CAGE 1TSP2), in the regular course of its regularly-conducted business activity, at or near the time the event occurred.

4. The Record bears the following cryptographic identifiers, which I have caused to be independently verified prior to this affidavit:

   - **Event hash (SHA-256):** `[RECORD_HASH]`
   - **Merkle anchor:** `[ANCHOR_ID]`
   - **Merkle root (SHA-256):** `[MERKLE_ROOT]`
   - **OpenTimestamps .ots proof file:** `[PROOF_FILENAME]`
   - **Bitcoin block containing the timestamp commitment:** block `[BITCOIN_BLOCK_HEIGHT]`, mined `[BITCOIN_BLOCK_TIMESTAMP]`

5. The Record was created by an automated electronic process (the "Knox system") whose correctness is described by a publicly-published formal specification in TLA+ (the "Specification"). The human-readable landing page for the Specification is published at `https://bonissystems.com/bonis/spec`, with the raw `.tla` and `.cfg` artifacts served directly at `https://bonissystems.com/spec/knox_anchor_chain.tla` and `https://bonissystems.com/spec/knox_anchor_chain.cfg`. The Specification has been machine-checked using the TLA+ model checker, and the model-checking transcript is published at `https://bonissystems.com/spec/tlc_knox_anchor_chain.log`.

6. The Record was produced by the Knox system without intervening human input between the triggering event and the anchoring of the event. No party — including Bonis Systems LLC, the operator of the Knox system — has the ability to alter the Record after the Merkle root of the anchor has been published to Bitcoin, because any modification to the Record would cause its cryptographic hash to differ from the published hash, and any such modification would be immediately detectable by the public Bitcoin record.

7. I have caused the Record to be independently verified by running the verification script published by Bonis Systems at `https://bonissystems.com/legal-kit/verify-knox-record.mjs` against the Record. A transcript of that verification run is attached hereto as **Exhibit B**. The verification transcript confirms that (a) the Record's event hash matches its contents, (b) the Record is included in the Merkle tree of anchor `[ANCHOR_ID]`, and (c) the Merkle root of anchor `[ANCHOR_ID]` is committed to Bitcoin block `[BITCOIN_BLOCK_HEIGHT]`.

8. I further state that the Record has not been altered in any way since the time of its production, and that the verification described in paragraph 7 could not have produced a positive result if the Record had been altered.

9. This affidavit is made in conformity with Federal Rule of Evidence 902(13) regarding records generated by an electronic process or system, and Federal Rule of Evidence 902(14) regarding data copied from an electronic device, storage medium, or file.

I declare under penalty of perjury that the foregoing is true and correct.

Executed on this _______ day of _______________, 20____.

_______________________________________
[CUSTODIAN NAME], [TITLE]

---

**NOTARY ACKNOWLEDGMENT**

Sworn to and subscribed before me this _______ day of _______________, 20____.

_______________________________________
Notary Public

My commission expires: _______________

---

## Exhibits referenced

- **Exhibit A** — the Knox record (JSON bundle, including event hash, Merkle anchor reference, Merkle proof, and optionally the .ots proof).
- **Exhibit B** — transcript produced by running `verify-knox-record.mjs` against Exhibit A on an air-gapped machine.
- **Exhibit C** (optional) — attached screenshot or print of `https://bonissystems.com/api/knox/verify?hash=<RECORD_HASH>` showing the public verification response.
- **Exhibit D** (optional) — downloaded copy of the TLA+ Specification from `https://bonissystems.com/spec/`.

---

*Template last updated 2026-04-19. This is a STARTER template. Counsel must adapt it to the jurisdiction, case posture, and applicable evidentiary rules.*