doc: update secp256k1 documentation links#342
Open
zhanzhao-h wants to merge 1 commit into
Open
Conversation
|
Maintainer review note for the #32/#81 bounty queue: This docs-only PR looks safe and useful: I checked the current head
The acceptance boundary I would use is narrow: keep this as link-retargeting only, with no copied upstream secp256k1 content and no semantic build/test guidance changes beyond pointing readers to the vendored Bitgesell tree. The PR body already has No wallet, node, key, dependency, or live-chain scope is involved. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Updates stale secp256k1 documentation links.
The project already vendors secp256k1 under
src/secp256k1; this points contributors and readers to the in-tree documentation instead of the old external Bitcoin Core path.Notes
Docs-only change.
BTC/BGL PR reward address
To be provided if applicable.
Validation:
Refs #32