secp256k1

secp256k1 copied to clipboard

This PR starts using the [new](https://github.blog/changelog/2024-01-30-github-actions-introducing-the-new-m1-macos-runner-available-to-open-source/) M1 macOS runner. The alternative approach might be using a matrix, but it is not trivial to implement.

hebasto

ci: Future of CI after Cirrus pricing change

37

Roadmap (keeping this up to date): I think the natural way forward for us is: - [x] Move native Windows tasks to GitHub Actions (#1389 and #1397) - [x] Move...

real-or-random

Be stricter with side effects in VERIFY

2

Adds a rule to CONTRIBUTING.md and makes the code adhere to it.

real-or-random

tests: Make CHECK enforce 1 instead of just "!= 0"

1

This ensures that we don't omit the "== 1" in tests accidentally, and thus also strengthens existing tests in which it has been omitted. We want to check "== 1"...

real-or-random

Rework or get rid of scratch space

4

Our confidence in the scratch space code isn't particularly high. It reinvents bump allocation, but it had a few issues in the past. All the code that uses scratch space...

real-or-random

Don't #include standard library headers unconditionally

7

This is supposed to resolve #1095 and help with restricted settings such as embedded systems or WASM. The approach is to detect the availability of `` and ``, both when...

real-or-random

Add MuSig2 module

6

I think a module for MuSig2 would be in the scope of libsecp256k1. Its relevance for the Bitcoin ecosystem is demonstrated by several factors: - MuSig2 is already being adopted...

jonasnick

Replace ASM with CryptOpt generated

17

In this PR the auto detection of x86_64 is removed and the configure file will default to the C implementation. Further, if asm has explicitly been requested with `--with-asm=x86_64`, the...

dderjoel

We prefix all global names with `secp256k1_` to avoid name collisions and ensure that the library can be header-only. If we believe in this, we should probably do the same...

real-or-random

Replace the 64-bit C field implementation by fiat-crypto output

18

This PR is result of https://github.com/bitcoin-core/secp256k1/issues/1261 In a nutshell, it replaces the current C-Implementation for the field arithmetic multiply and Square with the proven-correct implementation from the Fiat Cryptography Framework.

dderjoel