Skip to content

feat(094): 0.4.0 — split-key by default in createIntent#8

Merged
ValidPay-io merged 1 commit into
mainfrom
feat/094-split-key-default
Jun 12, 2026
Merged

feat(094): 0.4.0 — split-key by default in createIntent#8
ValidPay-io merged 1 commit into
mainfrom
feat/094-split-key-default

Conversation

@ValidPay-io

Copy link
Copy Markdown
Owner

Prompt 094 Task 1 (Node half). Mirrors ValidPay-io/validpay-python-sdk#3.

  • createIntent() now defaults to split-key (Patent C): key is Share A, Share B (key_fragment_b) goes to the server. splitKey: false preserves the 0.3.x single-key flow.
  • verifyIntent() transparently handles split-key intents (fetches Share B from the fragment endpoint, XOR-combines) — createIntent → verifyIntent round trips work without callers knowing about shares.
  • createSplitKeyIntent() deprecated alias (one-shot process.emitWarning).
  • Version 0.4.0. 57/57 tests pass; tsc -p tsconfig.build.json clean. (Root tsc --noEmit over tests fails on main already — pre-existing mock typing, untouched.)

After merge: GitHub Release v0.4.0 triggers the npm publish workflow (NPM_TOKEN).

🤖 Generated with Claude Code

- createIntent() gains splitKey (default true): returns Share A, sends
  Share B (key_fragment_b) to the server; splitKey:false = legacy flow.
- verifyIntent() transparently verifies split-key intents (fetches the
  fragment and XOR-combines) so create -> verify round-trips keep working.
- createSplitKeyIntent() deprecated -> alias of createIntent().
- Version 0.4.0; CHANGELOG + README updated.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@ValidPay-io
ValidPay-io merged commit 5c69bfd into main Jun 12, 2026
1 check passed
@ValidPay-io
ValidPay-io deleted the feat/094-split-key-default branch June 12, 2026 09:43
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.

1 participant