mirror of https://github.com/lightningnetwork/lnd.git synced 2025-03-29 19:22:40 +01:00

History

The Core devs decided to us the same bech32 HRP for Signet as is used
for the current Testnet3. This might be okay for on-chain addresses
since they are compatible in theory. But for invoices we want to use a
distinct HRP to distinguish testnet from signet.
Also see spec PR
https://github.com/lightningnetwork/lightning-rfc/pull/844 for more
information about the reasoning.

2021-05-18 13:06:03 +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

Let invoice.Encode receive a function which hashes itself the message

2020-07-29 21:18:24 +03: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

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