frost/secp256k1-zkp
3
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

docs: simplify README description, fix musig docs

Browse Source
This commit is contained in:
mllwchrry
2026-02-16 13:01:42 +02:00
parent 8d443b8030
commit 8c7c24eb8a
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@@ -3,7 +3,7 @@ libsecp256k1-zkp
![Dependencies: None](https://img.shields.io/badge/dependencies-none-success)
A fork of [libsecp256k1](https://github.com/bitcoin-core/secp256k1) with support for advanced and experimental features such as Confidential Assets and Bulletproofs++ range proofs
A fork of [libsecp256k1](https://github.com/bitcoin-core/secp256k1) with support for advanced and experimental features
Added features:
* Experimental module for ECDSA adaptor signatures.

2
doc/musig.md
View File

@@ -54,7 +54,7 @@ Similarly, the API supports an alternative protocol flow where generating the ag
A participant who wants to verify the partial signatures, but does not sign itself may do so using the above instructions except that the verifier skips steps 1, 4 and 7.
# Atomic Swaps
## Atomic Swaps
The signing API supports the production of "adaptor signatures", modified partial signatures
which are offset by an auxiliary secret known to one party. That is,

2
include/secp256k1_musig.h
View File

@@ -544,7 +544,7 @@ SECP256K1_API int secp256k1_musig_partial_sign(
* create the `session` with `musig_nonce_process`.
*
* This function is essential when using protocols with adaptor signatures.
* It is not required to call this function in regular MuSig sessions, because
* Without adaptor signatures, it is not required to call this function in regular MuSig sessions, because
* if any partial signature does not verify, the final signature will not
* verify either, so the problem will be caught. However, this function
* provides the ability to identify which specific partial signature fails