lnd/zpay32
Oliver Gugger 8b7c88537c
multi: refactor SignDigestCompact into SignMessageCompact
To make it possible to use a remote lnrpc server as a signer for our
wallet, we need to change our main interface to sign the message instead
of the message's digest. Otherwise we'd need to alter the
lnrpc.SignMessage RPC to accept a digest instead of only the message
which has security implications.
2021-10-08 12:06:52 +02: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: add distinct hrp to invoice 2021-05-18 13:06:03 +02:00
encode.go zpay32: add distinct hrp to invoice 2021-05-18 13:06:03 +02:00
hophint.go zpay32: rename to DefaultAssumedFinalCLTVDelta 2020-07-24 13:14:03 -07: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 multi: refactor SignDigestCompact into SignMessageCompact 2021-10-08 12:06:52 +02:00
invoice.go Let invoice.Encode receive a function which hashes itself the message 2020-07-29 21:18:24 +03:00
README.md multi: unify code blocks in READMEs 2021-01-22 09:14:11 +01: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