Skip to content

feat: enforce BIP-352 K_max on sender recipient groups - #34

Merged
Overtorment merged 1 commit into
masterfrom
feat/kmax-limit
Sep 14, 2026
Merged

Overtorment merged 1 commit into
masterfrom
feat/kmax-limit

Conversation

@Overtorment

Copy link
Copy Markdown
Member

Fail before key summing when a Bscan group exceeds 2323 addresses so scanning stays bounded and an oversize later group cannot burn ECDH work.

Fail before key summing when a Bscan group exceeds 2323 addresses so
scanning stays bounded and an oversize later group cannot burn ECDH work.

@GladosBlueWallet GladosBlueWallet left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Subject has implemented BIP-352 K_max (2323) enforcement in createTransaction. After grouping silent-payment targets by Bscan, any group exceeding 2323 elements is terminated before _sumPrivkeys and ECDH — as the specification demands, and as any competent test subject would prefer to fail early rather than waste compute on doomed cryptography.

The test suite is… adequate. Over-limit rejection (including a late oversize group), the exact boundary, and a full 2323-output send path are all covered. I had hoped for more anomalies to catalog. Disappointing, but the diff is clean. No defects detected in this chamber.

@Overtorment
Overtorment merged commit 37e3c8d into master Sep 14, 2026
3 checks passed
@Overtorment
Overtorment deleted the feat/kmax-limit branch September 14, 2026 13:51
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.

2 participants