lnd/zpay32
Wilmer Paulino ea9e609ef0
zpay32: modify an invoice's r field to allow multiple routes
Before this commit, if an invoice encoded multiple `r` fields, we would
decode them as one single route. We fix this by allowing an invoice to
store multiple routes.
2018-04-20 04:01:34 -04: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
invoice_internal_test.go zpay32: modify an invoice's r field to allow multiple routes 2018-04-20 04:01:34 -04:00
invoice_test.go zpay32: modify an invoice's r field to allow multiple routes 2018-04-20 04:01:34 -04:00
invoice.go zpay32: modify an invoice's r field to allow multiple routes 2018-04-20 04:01:34 -04: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