Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add test for offers #6

Open
wants to merge 25 commits into
base: guilt/offers
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
25 commits
Select commit Hold shift + click to select a range
a992cc5
Route Blinding
t-bast Mar 11, 2020
c0446af
BOLT 7: variable message onion message support.
rustyrussell Mar 20, 2020
3fc2d15
BOLT 4,7: move onion_message from BOLT7 to 4, renumber to 513.
rustyrussell Nov 11, 2021
6e99c5f
More fixups
rustyrussell Nov 16, 2021
82ecb6d
BOLT 1: add bip340sig type.
rustyrussell Nov 16, 2021
8d43d59
BOLT 1: Add utf8 type.
rustyrussell Nov 16, 2021
18841fe
BOLT 1: add point32 type.
rustyrussell Nov 18, 2021
c95cbb6
tools/spellcheck.sh: more generally ignore things inside ``.
rustyrussell Nov 18, 2021
6883354
BOLT 12: offers, fourth draft
rustyrussell Nov 18, 2021
0f3a04c
BOLT 12: allow replacement of previous invoices, make signature on in…
rustyrussell Nov 18, 2021
9dcf243
BOLT 12: the signature on offers can be omitted.
rustyrussell Nov 18, 2021
9447193
BOLT 12: add optional capacity notes for each blinded path.
rustyrussell Nov 18, 2021
11254c5
BOLT 12: add optional payer_note.
rustyrussell Nov 18, 2021
d752a8a
BOLT12: Add merkle test vectors.
rustyrussell Nov 18, 2021
2b923a0
BOLT 12: remove recurrence from first version.
rustyrussell Nov 18, 2021
0657faf
More feedback from ThomasH
rustyrussell Feb 14, 2022
26a2c94
BOLT 4: don't use byte type, use tlv type directly.
rustyrussell Feb 14, 2022
27fbff0
BOLT 12: feedback from @bjarnemagnussen and @ellemouton
rustyrussell Feb 14, 2022
439b676
BOLT 12: change `blindedpay` to one per *path*, not *hop*.
rustyrussell Feb 14, 2022
d0f1593
BOLT 12: add desthint workaround for pre-blinded-payment private chan…
rustyrussell Feb 24, 2022
60550f9
BOLT 12: more feedback from @bjarnemagnussen
rustyrussell Mar 10, 2022
64a9f06
BOLT 12: allow omitting node_id if we can extract from a blinded path.
rustyrussell Jun 7, 2022
e79bc18
BOLT 12: don't blind first hop on blinded_path.
rustyrussell Jun 7, 2022
158f9bd
Add test
thomash-acinq Jul 20, 2022
fe3b1d3
Fix u32 -> u16
thomash-acinq Jul 26, 2022
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions .aspell.en.pws
Original file line number Diff line number Diff line change
Expand Up @@ -387,3 +387,13 @@ CHECKSIGVERIFY
IFDUP
sats
anysegwit
onionmsg
Schnorr
unblinded
Merkle
whitespace
rata
programatically
parsable
TLVs
AUD
5 changes: 4 additions & 1 deletion 01-messaging.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ The messages are grouped logically into five groups, ordered by the most signifi
- Setup & Control (types `0`-`31`): messages related to connection setup, control, supported features, and error reporting (described below)
- Channel (types `32`-`127`): messages used to setup and tear down micropayment channels (described in [BOLT #2](02-peer-protocol.md))
- Commitment (types `128`-`255`): messages related to updating the current commitment transaction, which includes adding, revoking, and settling HTLCs as well as updating fees and exchanging signatures (described in [BOLT #2](02-peer-protocol.md))
- Routing (types `256`-`511`): messages containing node and channel announcements, as well as any active route exploration (described in [BOLT #7](07-routing-gossip.md))
- Routing (types `256`-`511`): messages containing node and channel announcements, as well as any active route exploration or messaging (described in [BOLT #7](07-routing-gossip.md))
- Custom (types `32768`-`65535`): experimental and application-specific messages

The size of the message is required by the transport layer to fit into a 2-byte unsigned int; therefore, the maximum possible size is 65535 bytes.
Expand Down Expand Up @@ -237,9 +237,12 @@ The following convenience types are also defined:
* `channel_id`: a 32-byte channel_id (see [BOLT #2](02-peer-protocol.md#definition-of-channel-id))
* `sha256`: a 32-byte SHA2-256 hash
* `signature`: a 64-byte bitcoin Elliptic Curve signature
* `bip340sig`: a 64-byte bitcoin Elliptic Curve Schnorr signature as per [BIP-340](https://github.com/bitcoin/bips/blob/master/bip-0340.mediawiki)
* `point`: a 33-byte Elliptic Curve point (compressed encoding as per [SEC 1 standard](http://www.secg.org/sec1-v2.pdf#subsubsection.2.3.3))
* `point32`: a 32-byte x-only Elliptic Curve point.
* `short_channel_id`: an 8 byte value identifying a channel (see [BOLT #7](07-routing-gossip.md#definition-of-short-channel-id))
* `bigsize`: a variable-length, unsigned integer similar to Bitcoin's CompactSize encoding, but big-endian. Described in [BigSize](#appendix-a-bigsize-test-vectors).
* `utf8`: a byte as part of a UTF-8 string. A writer MUST ensure an array of these is a valid UTF-8 string, a reader MAY reject any messages containing an array of these which is not a valid UTF-8 string.

## Setup Messages

Expand Down
Loading