input-output-hk/musig2

Issues

• Requirement of Multiple messages when signing in musig2

  #44 opened a year ago by jainanubha
  0

• Implement fuzz testing

  #38 opened a year ago by curiecrypt
  0

• Check the code for coding rules

  #11 opened 2 years ago by curiecrypt
  0

• Re-organize the folders

  #27 opened 2 years ago by curiecrypt
  0

• Use decorators on functions to enforce conditions when applicable

  #23 opened 2 years ago by iquerejeta
  0

• Last line check

  #40 opened 2 years ago by curiecrypt
  0

• More granular error handling

  #14 opened 2 years ago by iquerejeta
  0

• Consistency in API

  #21 opened 2 years ago by iquerejeta
  0

• Abstract library users completely from bitcoin-core/secp256k1

  #30 opened 2 years ago by iquerejeta
  0

• Remove print functions from library functions

  #20 opened 2 years ago by iquerejeta
  0

• Break down test file

  #24 opened 2 years ago by iquerejeta
  0

• Signer pre-computation

  #26 opened 2 years ago by curiecrypt
  0

• Add Valgrind checks to CI

  #18 opened 2 years ago by iquerejeta
  1

• Include the testing in Github actions

  #6 opened 2 years ago by iquerejeta
  0

• Improve the testing

  #5 opened 2 years ago by iquerejeta
  0

• Update the functions for proper error handling

  #10 opened 2 years ago by curiecrypt
  0

• Detailed documentation to explain compatibility of MuSig2 with Schnorr 340

  #15 opened 2 years ago by curiecrypt
  0

• Implement serialization/deserialization for structures

  #13 opened 2 years ago by curiecrypt
  0

• What if we remove the secp256k1 context, and use a MuSig2 context instead?

  #7 opened 2 years ago by iquerejeta
  0

• Simplify the API

  #4 opened 2 years ago by iquerejeta
  0

• Handle the memory allocation internally

  #3 opened 2 years ago by iquerejeta
  1