bitpay/jsonPaymentProtocol

Issues

• H

  #94 opened 3 months ago by Reeebecky
  0

• separate broadcast paymebt failures.

  #7 opened 7 years ago by monsterbitar
  1

• npm latest version is not updated

  #89 opened a year ago by omariosman
  0

• Bitcoin pibs json.codings

  #83 opened 2 years ago by Inxubis13
  0

• Duplicate declaration of parsePaymentRequestAsync

  #25 opened 6 years ago by micahriggan
  0

• `requiredFeeRate` is ambiguous

  #28 opened 6 years ago by swansontec
  1

• Second clause of if statement cannot hit

  #26 opened 6 years ago by micahriggan
  2

• Auth is a regression over current Bip70

  #18 opened 6 years ago by cpacia
  1

• Payment payload missing refund address

  #19 opened 6 years ago by cpacia
  1

• Why has required fee rate for BCH changed to 1.001?

  #24 opened 6 years ago by vinarmani
  6

• Signature is invalid

  #23 opened 6 years ago by elbelga
  1

• Bitpay error message uses inconsistent units

  #5 opened 7 years ago by zacleids
  7

• support unconfirmed chains

  #8 opened 7 years ago by monsterbitar
  1

• Suggestion for extension of JSON protocol.

  #13 opened 7 years ago by zhoujianfu
  7

• Question: Why not separate Authentication-only spec?

  #16 opened 7 years ago by joemphilips
  0

• Various issues

  #15 opened 7 years ago by jgriffiths
  1

• paymentUrlObject.protocol checking against wrong strings

  #6 opened 7 years ago by zacleids
  0

• medium agnostic

  #9 opened 7 years ago by monsterbitar
  1