secp256k1: Field64 API parity.#3738
Merged
Merged
Conversation
jholdstock
approved these changes
Jul 17, 2026
dcr-approvals-proxy
approved these changes
Jul 21, 2026
This modifies the new FieldVal64 type have API parity with the existing FieldVal type with the goal of ultimately allowing the backend to be dynamically replaced.
davecgh
force-pushed
the
secp256k1_field64_api_parity
branch
from
July 22, 2026 07:09
e2898c1 to
2163ef5
Compare
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
3 participants
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.
This modifies the new FieldVal64 type have API parity with the existing FieldVal type with the goal of ultimately allowing the backend to be dynamically replaced.