Skip to content

docs: define regulated custody design - #9728

Draft
ralph-bitgo[bot] wants to merge 1 commit into
masterfrom
WCI-1619-regulated-custody-design
Draft

ralph-bitgo[bot] wants to merge 1 commit into
masterfrom
WCI-1619-regulated-custody-design

Conversation

@ralph-bitgo

@ralph-bitgo ralph-bitgo Bot commented Sep 14, 2026

Copy link
Copy Markdown

What

  • Add docs/regulated-custody-design.md for Wallet Core India.
  • Define custodial wallet creation and transaction-routing boundaries for TSS and non-TSS wallets.
  • Document jurisdiction capability handling, security/audit invariants, failure behavior, rollout sequencing, and open service-contract decisions.

Why

WCI-1619 needs a shared engineering boundary for BitGo regulated custody before adding more entities, MPC versions, or chain-specific flows. The design keeps policy and key control on BitGo services and prevents SDK capability metadata from being treated as custody authorization.

Verification

  • Structural validation confirmed all referenced implementation paths exist and required design sections are present.
  • git diff --check and git show --check pass.
  • No runtime code changed; no unit-test suite was applicable.

Ticket: WCI-1619

Document the SDK and service boundary for custodial wallet creation, transaction routing, jurisdiction capability checks, security invariants, failure handling, and rollout sequencing.\n\nThis gives Wallet Core India a shared contract for regulated custody work without introducing client-side key handling or treating SDK capability data as authorization.\n\nTicket: WCI-1619

Session-Id: 2187f9f5-04aa-4c71-ba85-f0b4274bffb4
Task-Id: d4f8df53-d99a-4a88-9d8e-b072aba582a3
@ralph-bitgo
ralph-bitgo Bot force-pushed the WCI-1619-regulated-custody-design branch from 6866472 to 416bcf1 Compare September 14, 2026 13:23
@linear-code

linear-code Bot commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

WCI-1619

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants