-
As a pre-req to https://github.com/p2pderivatives/rust-dlc/issues/221
I don't see a specific reason for using `secp25k1_zkp`
-
Consider the following diff:
```diff
--- a/src/secp256k1.c
+++ b/src/secp256k1.c
@@ -765,7 +765,9 @@ int secp256k1_ec_pubkey_tweak_mul(const secp256k1_context* ctx, secp256k1_pubkey
return r…
-
There are some applications that need to parse the timechain but don't need to verify signatures (they get the blocks from bitcoind), nor do they need to sign (they are not wallets). For these applica…
-
"secp256k1-proto" sounds good to me
-
These tests fail due to the format method, which adds a "04" value and doesn't have a space between x and y in `to_hex_string()`.
```rust
---- secp256k1::tests::secp256k1_add_poins stdout ----
t…
-
No File Secp256k1.h ,,, unable to compile the program with make.
-
See discussion at https://gnusha.org/secp256k1/2024-07-01.log, also mentioned in https://github.com/bitcoin-core/secp256k1/issues/1549.
-
Introduce field element type, called `Felt`, to circumvent having to bound scalar to Q manually. This should generally increase crysol's reliability, especially with regared to future curves.
Note …
-
The common operation to do on a `SegwitV0Sighash` is to convert it to a secp256k1 `Message` for signing, it seems like we'd benefit from having that be available directly.
-
Seems **C library from Rust compiled to WASM** is [not quite impossible](https://stackoverflow.com/questions/51666736/how-do-i-use-a-c-library-in-a-rust-library-compiled-to-webassembly/51804070) but m…