lnd/zpay32
Olaoluwa Osuntokun b368e476c5
lnwire: update Sig to support both ECDSA and schnorr sigs
In this commit, we update the Sig type to support ECDSA and schnorr
signatures. We need to do this as the HTLC signatures will become
schnorr sigs for taproot channels. The current spec draft opts to
overload this field since both the sigs are actually 64 bytes in length.
The only consideration with this move is that callers need to "coerce" a
sig to the proper type if they need schnorr signatures.
2023-08-22 16:29:19 -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 lnwire: update Sig to support both ECDSA and schnorr sigs 2023-08-22 16:29:19 -07:00
encode.go lnwire: update Sig to support both ECDSA and schnorr sigs 2023-08-22 16:29:19 -07:00
fuzz_test.go zpay32: allow fuzzer to choose invoice net 2023-07-19 09:04:26 -05:00
hophint.go multi: use btcd's btcec/v2 and btcutil modules 2022-03-09 19:02:37 +01:00
invoice_internal_test.go multi: move many t.Fatalf calls to require.NoError 2022-06-17 04:26:55 +00:00
invoice_test.go zpay32: add payment metadata field 2022-04-13 22:55:38 +02:00
invoice.go zpay32: add payment metadata field 2022-04-13 22:55:38 +02:00
README.md scripted-diff: replace ⛰ emoji with $ [skip ci] 2022-10-28 12:06:49 -04: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