044e1e692f
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. |
||
---|---|---|
.. | ||
amountunits.go | ||
bech32.go | ||
decode.go | ||
encode.go | ||
hophint.go | ||
invoice_internal_test.go | ||
invoice_test.go | ||
invoice.go | ||
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