Skip to content

feat(094): 1.1.0 — split-key by default in create_intent#3

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

feat(094): 1.1.0 — split-key by default in create_intent#3
ValidPay-io merged 1 commit into
mainfrom
feat/094-split-key-default

Conversation

@ValidPay-io

Copy link
Copy Markdown
Owner

Prompt 094 Task 1 (Python half).

  • create_intent() now defaults to split-key (Patent C): result.key is Share A, Share B (key_fragment_b) goes to the server. split_key=False preserves the 1.0.x single-key flow.
  • verify_intent() transparently handles split-key intents (fetches Share B from the fragment endpoint and XOR-combines) — the natural create_intent → verify_intent round trip works without callers knowing about shares. Legacy intents verify unchanged.
  • create_split_key_intent() is a deprecated alias (DeprecationWarning), per the prompt.
  • Version 1.1.0. 81 tests pass locally (binding tests need scipy, skipped — CI runs them).

After merge: GitHub Release v1.1.0 triggers the PyPI trusted-publishing workflow.

🤖 Generated with Claude Code

- create_intent() gains split_key=True default: returns Share A, sends
  Share B (key_fragment_b) to the server; split_key=False = legacy flow.
- verify_intent() transparently verifies split-key intents (fetches the
  fragment and XOR-combines) so create -> verify round-trips keep working.
- create_split_key_intent() deprecated -> alias of create_intent().
- Version 1.1.0; CHANGELOG + README updated.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@ValidPay-io
ValidPay-io merged commit 746703e into main Jun 12, 2026
4 checks 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