Skip to content

unify secp256k1 api to use just pure-rust libsecp256k1#7296

Closed
rob-stacks wants to merge 6 commits into
stacks-network:developfrom
rob-stacks:feat/unified_secp256k1
Closed

unify secp256k1 api to use just pure-rust libsecp256k1#7296
rob-stacks wants to merge 6 commits into
stacks-network:developfrom
rob-stacks:feat/unified_secp256k1

Conversation

@rob-stacks

Copy link
Copy Markdown
Contributor

Description

This patch unifies the secp256k1 api to only use libsecp256k1 (pure rust).

The same structure is used for wasm.

More unit tests have been added included a new one for checking high-S signatures

Applicable issues

  • fixes #

Additional info (benefits, drawbacks, caveats)

Checklist

  • Test coverage for new or modified code paths
  • For new Clarity features or consensus changes, add property tests (see docs/property-testing.md)
  • Changelog fragment(s) or "no changelog" label added (see changelog.d/README.md)
  • Required documentation changes (e.g., rpc/openapi.yaml for RPC endpoints, event-dispatcher.md for new events)
  • New clarity functions have corresponding PR in clarity-benchmarking repo

Comment thread stacks-common/Cargo.toml
ed25519-dalek = { workspace = true }
hashbrown = { workspace = true }
lazy_static = { workspace = true }
libsecp256k1 = { version = "0.7.2", default-features = false, features = ["hmac", "lazy-static-context"] }

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I believe we should use this one instead: k256. It is more widely accepted and audited.

@rob-stacks

Copy link
Copy Markdown
Contributor Author

Closing this. New PR here: #7305

@rob-stacks rob-stacks closed this Jun 15, 2026
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