lnd/zpay32
Johan T. Halseth 386f8ece54
routing+zpay32: copy pubkeys before nilling Curve and spewing
Since nilling the pubkey curve will lead to a nil-pointer exception if
the key is later used for signature verification, we make sure to make a
copy before nilling and spewing.
2019-06-12 12:19:43 +02:00
..
amountunits.go multi: comprehensive typo fixes across all packages 2018-02-06 19:11:11 -08:00
bech32.go multi: comprehensive typo fixes across all packages 2018-02-06 19:11:11 -08:00
hophint.go routing+zpay32: copy pubkeys before nilling Curve and spewing 2019-06-12 12:19:43 +02:00
invoice_internal_test.go zpay32: move HopHint and DefaultFinalCLTVDelta 2019-03-15 10:08:32 +01:00
invoice_test.go zpay32: move HopHint and DefaultFinalCLTVDelta 2019-03-15 10:08:32 +01:00
invoice.go zpay32: move HopHint and DefaultFinalCLTVDelta 2019-03-15 10:08:32 +01:00
README.md multi: fix formatting issues in packge README's 2017-03-27 16:25:25 -07:00

zpay32

Build Status MIT licensed GoDoc

The zpay32 package implements a basic scheme for the encoding of payment requests between two lnd nodes within the Lightning Network. The zpay32 encoding scheme uses the zbase32 scheme along with a checksum to encode a serialized payment request.

The payment request serialized by the package consist of: the destination's public key, the payment hash to use for the payment, and the value of payment to send.

Installation and Updating

$ go get -u github.com/lightningnetwork/lnd/zpay32