Skip to content

Choice of secp256k1 interface #69

@ofek

Description

@ofek

Hello there! I'm a maintainer of coincurve, a provider of libsecp256k1.

As of v21.0.0 there are zero runtime dependencies and we started to maintain benchmarks against other libraries. I didn't have time to add your ctypes-based code although I would love if you could share the results of benchmarks that you might have done recently.

I think we would be a good fit for this project because we frequently update to upstream releases 1 and we provide precompiled wheels which would make installation much easier 2, although I am relatively unfamiliar with your target audience.

Please let me know if you are interested in switching to coincurve for performance reasons or to free up the maintenance you have to do, or both! Definitely let me know if there is something you require which I have not yet implemented.

Footnotes

  1. I think that would solve this issue https://github.com/diybitcoinhardware/embit/issues/55

  2. This might be useful for users who wish to use the same upstream reference as what Bitcoin Core uses like this issue https://github.com/diybitcoinhardware/embit/issues/56

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions