KarpelesLab / libwallet / 26093031309

22%

push

github

wltwallet: add Wallet.Protocol field + dispatch scaffolding

Step 2/5 of the protocol-modernization track. Adds the Protocol
field to the Wallet row (default empty for backwards compat) plus a
resolveProtocol() helper that callsites will branch on as dkls23 /
frost paths land in steps 3 + 4.

  Wallet.Protocol values:
    ""         (legacy row — resolves to curve-appropriate legacy)
    "gg18"     legacy threshold ECDSA on secp256k1 (ecdsatss)
    "eddsa"    legacy GG18-style Schnorr on ed25519 (eddsatss)
    "dkls23"   modern threshold ECDSA via DKLs23 — step 3
    "frost"    modern Schnorr/Ed25519 via FROST — step 4

Existing rows pre-date this field; resolveProtocol() maps their
empty Protocol to the legacy constant matching their Curve so every
existing wallet continues to sign through the same code path it
always has. New wallets created today still go through the legacy
path but have their Protocol stamped explicitly (gg18 / eddsa) so
the field is populated going forward and the empty-string branch
becomes a closed set that goes to zero as old wallets churn out.

ClawdWallet's apiInitiateKeygen also stamps Protocol = eddsa for
the same reason.

Dart Wallet model gains a `protocol` field reading from the new
JSON key — hosts can now branch on the TSS protocol for any
protocol-aware UX (e.g. "this wallet is on the modern protocol").

Steps 3 + 4 will add the actual dkls23 / frost adapters; step 5
flips the default for new wallets.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

25 of 29 new or added lines in 2 files covered. (86.21%)

3670 of 16574 relevant lines covered (22.14%)

112.62 hits per line