-
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…
-
upstream has improved performance: https://github.com/bitcoin-core/secp256k1/blob/master/CHANGELOG.md#041---2023-12-21
-
There is a need to store keys in the browser in a secure way, avoiding plaintext options like `localStorage`.
Brave Wallet supports only Ethereum signing options. But there is more potential, eg: h…
-
This crate uses qualifying paths for types eg, `bitcoin::PublicKey` and `secp256k1::PublicKey`. I understand that this adds clarity, especially for types that exist in multiple places (like the given …
-
If I'm understanding the API correctly, it's not currently possible to use this crate to sign or verify BIP340 messages that are not exactly 32 bytes long. Is this correct? If so is there any change o…
-
/go/pkg/mod/github.com/fbsobreira/gotron-sdk@v0.0.0-20230907131216-1e824406fe8c/pkg/keystore/recover.go:17:33: undefined: secp256k1.RecoverPubkey
```
FROM golang:alpine as builder
#FROM golang:1.…
-
In rust-secp256k1 we're exploring how we can best support a signing API for systems which potentially have no allocator, may be operating multiple threads, but which have very limited threading primit…
-
fix crystallib/crypt/secp256k1/secp256k_test.v
check examples in examples/crypt/secp256/secp256k1-example.vsh
-
Port libsecp256k1 v0.3.2, which addresses the issue of optimizing the code for ECDH side-channel protection after GCC v13.
https://github.com/bitcoin-core/secp256k1/blob/master/CHANGELOG.md