Elliptic Curve · Custody v2026.09

A custodian's checklist

Nine questions, five contract clauses, and a migration order. Nothing here depends on a view about timelines.

PUBLICATION GATE · SPEC §12, implementation-note.md Counsel review required before publication of section B. The model contract language has not been reviewed. Section A and section C are gated with the rest of the custody material on the SPEC §11 employment disclosure.

OPEN QUESTION · SPEC §14 question 4 Published under Delta Gamma LLC or under the owner's own name? It is professional opinion touching their employer's sector and the two framings carry different exposure. Unanswered, and it changes the byline, the footer and the disclaimer on this sheet.

A · What to ask your provider

Question 1 — to be written.

Rationale: what a good answer looks like, and what a bad one reveals.

Question 2 — to be written.

Rationale: what a good answer looks like, and what a bad one reveals.

Question 3 — to be written.

Rationale: what a good answer looks like, and what a bad one reveals.

Question 4 — to be written.

Rationale: what a good answer looks like, and what a bad one reveals.

Question 5 — to be written.

Rationale: what a good answer looks like, and what a bad one reveals.

Question 6 — to be written.

Rationale: what a good answer looks like, and what a bad one reveals.

Question 7 — to be written.

Rationale: what a good answer looks like, and what a bad one reveals.

Question 8 — to be written.

Rationale: what a good answer looks like, and what a bad one reveals.

Question 9 — to be written.

Rationale: what a good answer looks like, and what a bad one reveals.

B · What "quantum-ready" should mean in a contract

§1

Obligation 1 — lead-in phrase naming the obligation. One sentence.

Model language — not drafted, not reviewed by counsel. Set in mono because it is meant to be copied into a contract and read as fixed text.

§2

Obligation 2 — lead-in phrase naming the obligation. One sentence.

Model language — not drafted, not reviewed by counsel. Set in mono because it is meant to be copied into a contract and read as fixed text.

§3

Obligation 3 — lead-in phrase naming the obligation. One sentence.

Model language — not drafted, not reviewed by counsel. Set in mono because it is meant to be copied into a contract and read as fixed text.

§4

Obligation 4 — lead-in phrase naming the obligation. One sentence.

Model language — not drafted, not reviewed by counsel. Set in mono because it is meant to be copied into a contract and read as fixed text.

§5

Obligation 5 — lead-in phrase naming the obligation. One sentence.

Model language — not drafted, not reviewed by counsel. Set in mono because it is meant to be copied into a contract and read as fixed text.

C · Migration order

Priority	Holdings class	Why first
1	To be written.	Ordered by value at risk per unit of effort, not by size.
2	To be written.	Ordered by value at risk per unit of effort, not by size.
3	To be written.	Ordered by value at risk per unit of effort, not by size.
4	To be written.	Ordered by value at risk per unit of effort, not by size.
5	To be written.	Ordered by value at risk per unit of effort, not by size.

This section discusses the security properties of custody architectures as a class, not the implementations of any named provider. Statements about threshold signature schemes follow from the underlying cryptography and are not assessments of any specific product, vendor, or deployment. Providers should be evaluated on their own documentation and audits.