KarpelesLab / libwallet / 28576182463

25%

push

github

wltwallet: fail reshare fast on remote-reported ceremony errors

Companion to wdrone b5fde7d ("reject stale reshare shares at init + report
runner failures to client"). The fleet now broadcasts a "walletsign:error"
JsonMessage when a reshare runner fails terminally (e.g. its stored share is
stale relative to the requested committee); previously those failures were
fleet-log-only and the client waited out the 2-minute rounds deadline in
silence.

Client side:
- spotPeer.messageHandler intercepts Type=="walletsign:error" and routes the
  reason to tssHub.fail (once-guarded tssHub.onError hook).
- reshareRoundsContext gains a fail(reason) func: cancels the rounds via
  context.WithCancelCause with the remote's reason as cause; wrap surfaces it
  as "reshare failed — remote participant reported: <reason>; the wallet
  committee is unchanged" instead of the generic deadline message. Caller
  cancel and plain deadline behavior are unchanged (unit-tested, including a
  guard against mislabelling a remote failure as a timeout).
- All four reshare variants wire hub.onError = failRounds.

Wire-compatible in both directions: an old fleet never sends the frame (the
deadline still applies); an old client ignores the frame.

Full wltwallet suite green against the live fleet, including the healthy
reshare ceremonies (dkls/FROST/legacy old-side + repair cycle).

Part of unreleased 0.4.77.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

25 of 40 new or added lines in 2 files covered. (62.5%)

5027 of 20381 relevant lines covered (24.67%)

92.51 hits per line