lnd.xprv/zpay32
Conner Fromknecht 49c601e62a
zpay32: split off encoding/decoding into own files
As a preliminary step to isolating zpay32 in migrations 01-11, we'll
split out the encoding and decoding logic into separate files. Migration
11 only requires invoice decoding, so this prevents us from needing to
copy in the encoding logic that would otherwise be unused.
2020-07-24 13:13:29 -07:00
..
amountunits.go zpay32: invoice.MilliSat is uint64 which cannot be negative 2020-04-24 19:15:08 +02:00
bech32.go multi: comprehensive typo fixes across all packages 2018-02-06 19:11:11 -08:00
decode.go zpay32: split off encoding/decoding into own files 2020-07-24 13:13:29 -07:00
encode.go zpay32: split off encoding/decoding into own files 2020-07-24 13:13:29 -07: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/invoice: remove unknown required fbit check from decode 2020-01-08 12:25:21 -08:00
invoice.go zpay32: split off encoding/decoding into own files 2020-07-24 13:13:29 -07: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