History

Wilmer Paulino 07ac278771 invoice: properly parse the field data length When accessing a value from a byte slice, the value is returned as a byte, which is just a uint8. When the first byte takes more than 3 bits of space, shifting 5 bits left results in data loss.		2018-01-19 10:52:24 -05:00
..
amountunits.go	zpay32: move the BOLT-11 compatible invoice format to zpay32 namespace	2017-09-27 12:26:06 +02:00
bech32.go	zpay32: move the BOLT-11 compatible invoice format to zpay32 namespace	2017-09-27 12:26:06 +02:00
invoice_internal_test.go	zpay32: move the BOLT-11 compatible invoice format to zpay32 namespace	2017-09-27 12:26:06 +02:00
invoice_test.go	bolt11: handle r field fee spec change	2018-01-04 13:23:56 +01:00
invoice.go	invoice: properly parse the field data length	2018-01-19 10:52:24 -05:00
README.md	multi: fix formatting issues in packge README's	2017-03-27 16:25:25 -07:00

README.md

zpay32

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