Optimize ECDSA cracker: lazy pubkey derivation and partial sorting #29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Performance profiling revealed two bottlenecks: upfront EC public key derivation for all candidates (82% of runtime) and full sorting of matrix rows when only top N needed.
Changes
Lazy public key derivation with early exit (22.9x speedup)
find_allparameter for cases requiring all matchesBefore:
After:
Partial sorting with heapq (1.17x speedup)
heapq.nsmallest(max_rows, norms)instead of full sort whenmax_rows < matrix.nrowsCode quality
privkeys_from_reduced_matrix(15→9),display_keys(12→8)inttohex()to useformat(i, '064x')Performance
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.