lnd/zpay32
Conner Fromknecht e745798a6e
zpay32: update spec test vectors, write features last
This commit updates the BOLT11 test vectors to use the updated versions
from the spec (with TLV bit set). This also pointed out that the
ordering was inconsistent with the spec, in that the payment secret
should be serialized before the feature vector.
2019-12-19 14:36:28 -08: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/invoice: consolidate 32-byte array parsing and encoding logic 2019-12-05 07:58:55 -08:00
invoice_test.go zpay32: update spec test vectors, write features last 2019-12-19 14:36:28 -08:00
invoice.go zpay32: update spec test vectors, write features last 2019-12-19 14:36:28 -08: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