OVA — rusty-kaspa Version String Audit

Version. v0.1 · Date. 2026-06-22 · Status. Read-only find-and-classify. No edits, no staging, no commits. protocols/ova/README.md excluded per constraint. The Operator decides each occurrence after reading; this pass only locates and classifies. Scope. All OVA-relevant .md/.html in ~/Downloads (including pack/archive/bundle subtrees) and loomworks-record (committed copies + subtrees). 98 files scanned; 108 version-token / DAA occurrences found.

Headline (the resolution of the recurring confusion). Every occurrence is self-consistent by purpose, and nothing is mis-attributed. All v2.0.0 strings attribute the mainnet activation (hardcoded at DAA 474,165,565) — correct, v2.0.0 set activation. All v2.0.1 strings name the current substrate / SMT source / build target — correct, v2.0.1 is the SMT-current tag. No protocol doc uses both forms; no string needs correcting on its face. A naive "change all v2.0.0 → v2.0.1" would be wrong — it would corrupt correct activation attributions. The only items for Operator eyes are (1) one cross-doc punt (seed names v2.0.1 and defers to the spec, which names v2.0.0 — different facts, not a contradiction), and (2) the live spec never names v2.0.1 as the build/SMT-current version (an absence, not an error). Classification legend per task: ACTIVATION (v2.0.0 = activation, correct as written) · SDK/CURRENT (should be v2.0.1 — and already is) · AMBIGUOUS (meta/analysis/false-positive — do not bulk-edit).

Location legend. DL = ~/Downloads working copy · DL-pack = subtree inside a Downloads pack/archive/bundle dir · LR = committed in loomworks-record · LR-sub = loomworks-record subtree.

Duplicate copies are byte-identical; the sentence is quoted once per canonical doc, then all copy path:lines are enumerated. Every occurrence is located and classified.

GROUP A — Protocol / record docs (attribution-bearing)

A1. OVA_PROTOCOL_SPEC_V3_1.md — LIVE spec — 7 occ — all ACTIVATION

Only in DL (the live working copy; no other copy carries V3_1).

• L75 (Tech Stack): "KIP-16 ZK verification opcodes activate in the Toccata hard fork (mainnet activation ~June 30, 2026, rusty-kaspa v2.0.0, DAA score 474,165,565)." → ACTIVATION
• L242 / L244 / L273 / L275 (REQ-048/050/059/061 amendment flags): each reads "…is active post-Toccata hard fork (mainnet activation ~June 30, 2026, rusty-kaspa v2.0.0, DAA score 474,165,565)…" → ACTIVATION ×4
• L274 (REQ-060 [SCOPEGAS]): "…expected post-Toccata hard fork, mainnet activation ~June 30, 2026, rusty-kaspa v2.0.0, DAA score 474,165,565…" → ACTIVATION
• L310 (Grounding Notes): "Covenants/Toccata Hard Fork target: ~June 30, 2026 (rusty-kaspa v2.0.0, DAA score 474,165,565). Introduces KIP-16 ZK verification opcodes and SilverScript compiler SDK." → ACTIVATION (the fork/activation release; the "SDK introduced at the fork" is correct — the SDK ships with v2.0.0). Note: this is the one line where "v2.0.0" sits next to the word "SDK"; still ACTIVATION because it describes what the activation release introduced, not a build-against version.
• Observation (not a defect): V3_1 names only v2.0.0 (activation); it never states v2.0.1 as the SMT/build-current tag. Per the capability verification, the build target is v2.0.1. The Operator may wish to add a v2.0.1 build-target line — an addition, not a correction.

A2. OVA_PROTOCOL_SPEC_V3.md — superseded by V3_1 — 7 occ × 7 copies = 49 — all ACTIVATION

Same seven sentences as A1 (lines 74/239/241/270/271/272/307 in V3's numbering), byte-identical, all ACTIVATION. Copies:

• DL OVA_PROTOCOL_SPEC_V3.md
• DL-pack agentic-scope-pack-v0_1/… · grantha-working-files-v0_1/… · OVA_ARCHIVE_V3-2026-06-22/… · ova-build-pack-2026-06-22/… · stele-ova-source-bundle-2026-06-20/…
• LR-sub loomworks-record/protocols/ova/OVA_PROTOCOL_SPEC_V3.md
• Lines per copy: 74, 239, 241, 270, 271, 272, 307.
• Note: V3 is the prior version (V3_1 supersedes it). Edits here would be to a superseded doc — likely leave as historical record.

A3. OVA_PROTOCOL_SPEC_V0_6_AMENDMENT-v0_3.md — 1 occ × 2 copies = 2 — ACTIVATION

• L75: "Hard fork: 'Toccata, mainnet activation ~June 30, 2026 (rusty-kaspa v2.0.0, DAA score 474,165,565)'." → ACTIVATION
• Copies: DL · DL-pack OVA_ARCHIVE_V3-2026-06-22/. (Note: the -v0_2 amendment carries Toccata framing but no version token.)

A4. OVA_DISCOVERY_RECORD-v0_2.md — 1 occ × 6 copies = 6 — ACTIVATION

• L34: "The date moved from May 5 to a June 5–20 window, then to roughly June 30, 2026 (hardcoded in rusty-kaspa v2.0.0 at DAA score 474,165,565). The slips were to allow the sequencing commitment architecture to be finalized before circuits bind to it." → ACTIVATION (explicit "hardcoded … at DAA" — activation set by v2.0.0; correct).
• Copies: DL · DL-pack agentic-scope-pack · grantha-working-files · OVA_ARCHIVE · ova-build-pack · stele-ova-source-bundle.

A5. OVA_BUILD_PLAN-v0_2.md — 1 occ — ACTIVATION

• L22 (Mainnet milestone row): "Mainnet | Final numbers and decisions … | ~June 30 (DAA 474,165,565, rusty-kaspa v2.0.0)" → ACTIVATION (the activation milestone; correct). Only in DL.

A6. ova-project-handoff-v0_1.md — 1 occ × 4 copies = 4 — ACTIVATION

• L100: "Mainnet activation (~2026-06-30). Hardcoded in rusty-kaspa v2.0.0 at DAA score 474,165,565. The V3 spec carries no post-activation confirmation; pricing (ScopeGas benchmarks) and the STARK decision wait on it. This handoff predates activation." → ACTIVATION
• Copies: DL · DL-pack OVA_ARCHIVE · ova-build-pack · LR-sub loomworks-record/candidate-seeds/ova/.

A7. ova-candidate-seed-v0_1.md — 1 occ × 4 copies = 4 — SDK/CURRENT ⚠ cross-doc punt

• L112: "Kaspa substrate version specifics (rusty-kaspa v2.0.1, Toccata, testnet 12) are left to the spec, not the seed — the seed commits to 'standalone based-ZK application over Kaspa,' and the spec carries the version detail." → SDK/CURRENT (names v2.0.1 as the substrate version — already correct).
• ⚠ Cross-doc note for the Operator: this line names v2.0.1 and defers to the spec, but the spec (A1/A2) names v2.0.0. They are not in contradiction — the seed names the substrate/build version (v2.0.1) while the spec names the activation version (v2.0.0) — but a reader following the punt will see two different numbers. Worth a one-line reconciliation decision, not a blind edit.
• Copies: DL · DL-pack OVA_ARCHIVE · ova-build-pack · LR-sub loomworks-record/candidate-seeds/ova/.

A8. GRANTHA_PROJECT_HANDOFF-v0_1.md — 1 occ × 3 copies = 3 — SDK/CURRENT

• L52: "Substrate: Kaspa / rusty-kaspa v2.0.1 (post-Toccata). Grants are OVA eggs; live on-chain among indistinguishable decoys. SMT tooling = the revocation / membership-proof primitive (inclusion + non-inclusion, compressed, ZK-circuit-compatible)." → SDK/CURRENT (build/substrate version — correct at v2.0.1).
• Copies: DL · DL-pack agentic-scope-pack · grantha-working-files.

A9. GRANTHA_DISCOVERY_AND_SKETCH-v0_3 / v0_4 / v0_5 / v0_6 — 11 occ — all SDK/CURRENT

Two recurring sentences, both naming v2.0.1 as the source/substrate read this session — correct.

• "Sources read this session … rusty-kaspa v2.0.1 source (crypto/smt) … Kaspa source cloned from github.com/kaspanet/rusty-kaspa." → SDK/CURRENT
• "Substrate — Kaspa (rusty-kaspa v2.0.1, post-Toccata). DETERMINED (via OVA). … The rusty-kaspa SMT … inclusion and non-inclusion proofs, compressed, no_std…" → SDK/CURRENT
• Occurrences: v0_3 DL L11 (1); v0_4 DL L12+L218 (2); v0_5 DL L13+L219 (2); v0_6 L14+L220 × 3 copies = (6) — copies DL · DL-pack agentic-scope-pack · grantha-working-files.

GROUP B — Meta / audit-process docs (CC-authored; use both forms by design — DO NOT bulk-edit)

These discuss the v2.0.0-vs-v2.0.1 distinction deliberately; their mixed usage is the analysis, not an attribution error. Both-ways files — highest mis-edit risk if processed mechanically.

B1. RUSTY_KASPA_SMT_CAPABILITY_VERIFICATION-v0_1.md — 12 occ — AMBIGUOUS (meta)

DL only. Lines 6,10,12,16,17,19,20,21,23,53,73,79. Deliberately contrasts v2.0.0 (activation, 2026-06-05) with v2.0.1 (SMT-current, 2026-06-15) and concludes "canonical = v2.0.1." This is the resolution doc — leave intact.

B2. CC_BRIEF_OVA_VERSION_GREP-v0_1.md — 5 occ — AMBIGUOUS (meta)

DL only. Lines 6,15,21,30,31. The brief that commissioned this audit; states the v2.0.0/v2.0.1 question. Leave intact.

B3. OVA_F3_SPEC_ROWS-v0_1.md — 2 occ — SDK/CURRENT

DL only. L7 / L21: cite "rusty-kaspa v2.0.1 crypto/smt" as the verified SMT primitive source for the F-3 rows → SDK/CURRENT (correct).

GROUP C — False positives (NOT rusty-kaspa — DO NOT EDIT)

C1. foray-adapter-deep-read-v0_1 — 2 occ — AMBIGUOUS / false-positive

• LR loomworks-record/foray-reference/foray-adapter-deep-read-v0_1.md L231: "Header version: v2.0.0 (Corrected)" — this is the FORAY adapter's own header version, not rusty-kaspa. → false positive, do not touch.
• LR …/foray-adapter-deep-read-v0_1.html L202: same string, HTML copy. → false positive.

Files that use the string BOTH ways (mis-edit risk)

• No protocol/record doc (Group A) mixes v2.0.0 and v2.0.1. Each is internally consistent (specs/records → v2.0.0 activation; seed/GRANTHA → v2.0.1 current). Low intra-doc edit risk.
• Both-ways files are the two META docs B1 (RUSTY_KASPA_SMT_CAPABILITY_VERIFICATION) and B2 (CC_BRIEF_OVA_VERSION_GREP) — they contrast the two versions on purpose. These are the docs most likely to be "corrected" wrongly by a bulk pass; exclude them from any edit sweep.
• Cross-doc (not single-file) tension: A7 ova-candidate-seed L112 says v2.0.1 and defers to the spec, while A1/A2 specs say v2.0.0. Reconcile by decision, not by blind replace.

Counts

• Total occurrences (all copies, committed + subtrees): 108
• ACTIVATION: 69 — A1(7) + A2(49) + A3(2) + A4(6) + A5(1) + A6(4)
• SDK/CURRENT: 20 — A7(4) + A8(3) + A9(11) + B3(2)
• AMBIGUOUS (meta + false-positive): 19 — B1(12) + B2(5) + C1(2)
• Distinct canonical docs: 13 (Group A: 9 · Group B: 3 · Group C: 1). Remaining 95 file scans carried Toccata/activation framing without a version token, or no token at all.
• Net correction surface: 0 strings are wrong on their face. ACTIVATION (69) are correct activation attributions; SDK/CURRENT (20) already say v2.0.1; AMBIGUOUS (19) are meta/false-positive. The only Operator decisions are the A7 cross-doc punt and the optional addition of a v2.0.1 build-target line to the live spec (A1).

Read-only audit. protocols/ova/README.md deliberately not scanned. No file edited, staged, or committed. HALT — Operator decides each occurrence. DUNIN7 · Done In Seven LLC · Miami, Florida — OVA rusty-kaspa Version String Audit v0.1 — 2026-06-22