[Marzooqa]

What

• For EdDSA TSS coins, handleGenerateWallet reads the enterprise's wallet creation multiSigTypeVersion from GET /api/v2/tss/settings (the same setting and call BitGoJS uses in keychains.createMpc and the ECDSA external signer path).
  • MPCv2 -> the SDK gets eddsaMPCv2Callbacks (createEddsaMPCv2KeyGenCallbacks)
  • anything else -> eddsaCallbacks, the existing MPCv1 flow
• ECDSA and onchain generation are unchanged (ECDSA never looks up the setting).
• No new request field: the caller does not choose the MPC version.

Why

• WCI-918 of the WCI-888 plan. We want to end up on MPCv2 only. Because the version comes from the server-side setting, flipping it is a server-side change with no Master Express deploy and no change for API callers; dropping MPCv1 later means removing the else-branch.

Dependencies

• Stacked on feat(mbe): add EdDSA MPCv2 key generation callback factory #286 (callback factory), which is stacked on feat(awm): add EdDSA MPCv2 key generation to the mpcv2 routes #282.

Test plan

• 4 new routing tests in generateWallet.test.ts (SDK call stubbed, /tss/settings nocked): MPCv2 setting uses eddsaMPCv2Callbacks only; absent setting keeps eddsaCallbacks; a setting for a different coin family is ignored; ECDSA does not read the setting
• The two existing EdDSA MPCv1 generate tests now mock /tss/settings (no MPCv2 setting)
• tsc --noEmit, ESLint, commitlint and the OpenAPI drift check clean; full suite passing (467 tests)

Ticket: WCI-918

[linear-code]

WCI-918

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.

_{Tip: disable this comment in your organization's Code Review settings.}