secp256k1 VS crypto-numbers

Compare secp256k1 vs crypto-numbers and see what are their differences.

secp256k1

Haskell bindings for secp256k1 library (by haskoin)

crypto-numbers

DEPRECATED - use cryptonite - Cryptographic number related function and algorithms (by vincenthz)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
secp256k1 crypto-numbers
- 1
23 5
- -
5.7 0.0
about 1 month ago about 9 years ago
Haskell Haskell
GNU General Public License v3.0 or later BSD 3-clause "New" or "Revised" License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

secp256k1

Posts with mentions or reviews of secp256k1. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning secp256k1 yet.
Tracking mentions began in Dec 2020.

crypto-numbers

Posts with mentions or reviews of crypto-numbers. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-07-12.
  • Rolling your own crypto: Everything you need to build AES from scratch
    5 projects | news.ycombinator.com | 12 Jul 2022
    But you're approaching it from the wrong perspective: the idea isn't to use the crypto you implement yourself, the idea is to gain a better understanding of how the "magic" works. Of course my hand-rolled RSA/AES crypto is breakable, I know that because that's the default assumption.

    It's akin to saying, "you're not allowed to build your own smoke detector because it will be unsafe!". Of course I know that, I want to understand the differences between a photoelectric and ionization smoke detector, how they work in practice, because reading some PDF schematics just doesn't cut it for me.

    I honestly don't understand the line of reasoning of all this crypto gatekeeping.

    Fun fact: while I was doing my crypto deep dive in 2015, my language of choice being Haskell, I found issues in several libraries, specifically around entropy, and even one library with modulo bias [1]. They were acknowledged and addressed. It was a super fun learning exercise, and seeing all these comments how it's supposedly almost illegal to do this misses the point of people exploring and learning in their own ways.

    https://github.com/vincenthz/hs-crypto-numbers/commit/bceb54...

What are some alternatives?

When comparing secp256k1 and crypto-numbers you can also consider the following projects:

ed25519 - Minimal ed25519 Haskell package, binding to the ref10 SUPERCOP implementation.

keccak - Keccak hash functions

elocrypt - Generate easy-to-remember, hard-to-guess passwords

ecdsa - ECDSA stuff in Haskell

crypto-pubkey - DEPRECATED - use cryptonite - Cryptographic public key related algorithms in haskell (RSA,DSA,DH,ElGamal)

pairing - Optimised bilinear pairings over elliptic curves

cryptoconditions - Interledger Crypto-Conditions in Haskell

crypto-pubkey-types - Crypto Public Key algorithm generic types.

ripple - Implementation of Ripple client protocol in Haskell

NaCl

crypto-rng - Cryptographic random number generator.