You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -33,6 +33,7 @@ Build the most reliable, secure, and developer-friendly Swift secp256k1 library
33
33
|**Module-rename migration & version adoption**| Most downstream consumers are stranded on the legacy `secp256k1` product name and old pins (e.g., 0.12.2, 0.18.0, 0.19.0). Primitives added only to `P256K` cannot reach them. Provide a migration path / compatibility story so new APIs are actually adoptable — the single highest adoption lever. | 🔜 Planned |
34
34
|**swift-crypto 4.2.0 Update**| Update vendored swift-crypto via subtree plugin from 3.11.1 to 4.2.0. Resolve breaking availability attribute changes in `Sources/Shared/` on a case-by-case basis (e.g., `UInt256.swift` retains current attributes due to `StaticBigInt` dependency). | 🔜 Planned |
35
35
|**UInt256 SecurityTests**| Add security test vectors for `UInt256`/`SIMDWordsInteger` to `Projects/Sources/SecurityTests/`: overflow detection, boundary correctness, power-of-two multiply paths, Codable parsing hardening. _(The `SecurityTests` target exists with DER/InvalidCurve/PointValidation/ScalarValidation/SignatureMalleability/ZeroSignature/Nonce coverage; UInt256 vectors are still absent.)_| 🔜 Planned |
36
+
|**Vendir migration**| Adopt vendir-driven vendoring (the pattern proven in swift-openssl), retiring `subtree.yaml`, the subtree CLI/plugin workflows, and most Dependabot configuration. Scheduled in Q1 of the 2026 funding window (shared 2026 roadmap). | 🔜 Planned |
36
37
37
38
---
38
39
@@ -73,10 +74,13 @@ Phases are **theme-based capability slices**, ordered by **downstream-consumer r
_Funding note (2026-08-01):_ Phases 3, 8, and 9 sit outside the current 2026 funding window; Phase 9.5 (Q5) and Phase 10's Silent Payments (Q1) are scheduled inside it, per the shared 2026 outreach roadmap.
83
+
80
84
### Phase Summaries
81
85
82
86
-**Phase 0 — Tooling Foundation** ✅ — SPM pre-build plugin sharing code between P256K and ZKP targets from one source.
@@ -89,9 +93,10 @@ Phases are **theme-based capability slices**, ordered by **downstream-consumer r
-**Phase 9.5 — Command-Line Tool** — key generation, signing, verification, and address/npub encoding in the terminal; Homebrew distribution. Promoted from the backlog for the 2026 funding window.
**Promoted 2026-08-01**: the CLI tools (MuSig2 CLI, address generator, ECDSA signing CLI, Schnorr verifier) were promoted from this backlog to **Phase 9.5 — Command-Line Tool** for the 2026 funding window (Q5 of the shared 2026 roadmap). See [phase-9.5-cli-tool.md](phase-9.5-cli-tool.md).
**Funding**: Inside the 2026 funding window — Q5 (months 13–15) of the shared 2026 roadmap
9
+
**Last Updated**: 2026-08-01
10
+
11
+
Promoted from the [backlog](backlog.md) on 2026-08-01: the deferred CLI apps (MuSig2 CLI, address generator, ECDSA signing CLI, Schnorr verifier) merge into one executable. Scheduled in the 2026 funding round as scriptable access for developers and a low-friction demo surface for the encodings and primitives shipped in year one.
12
+
13
+
---
14
+
15
+
## Features
16
+
17
+
### Core CLI
18
+
19
+
**Purpose & User Value**: Key generation, signing (ECDSA + Schnorr), verification, and address/npub encoding from the terminal — scriptable access without writing Swift.
20
+
21
+
**Success Metrics**:
22
+
- One CLI executable with keygen / sign / verify / encode subcommands
23
+
- Address and npub output matches the Phase 4 encoding vectors
24
+
- Zero runtime dependencies maintained (Constitution)
25
+
26
+
### MuSig2 Ceremony Mode
27
+
28
+
**Purpose & User Value**: Command-line MuSig2 ceremony for scripting (the backlog's medium-priority item): key aggregation, nonce exchange, partial signing, aggregation.
29
+
30
+
**Success Metrics**:
31
+
- Ceremony state export/import between steps, so scripts can drive each stage
32
+
- Matches the existing MuSig2 test vectors
33
+
34
+
### Homebrew Formula
35
+
36
+
**Purpose & User Value**: `brew install` distribution — the demo surface for the year's shipped primitives.
37
+
38
+
**Success Metrics**:
39
+
- Formula published in a tap; `brew install` produces a working binary on macOS
40
+
- Versioned releases track package tags
41
+
42
+
---
43
+
44
+
## Phase Dependencies & Sequencing
45
+
46
+
1.**Core CLI** — after Phase 4 encodings (address/npub output)
0 commit comments