Skip to content

BLIP 42: increase payer offer size recommendation to 384 bytes #75

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.

Sign up for GitHub

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

Open
vincenzopalazzo wants to merge 1 commit into
base: master
Choose a base branch
from
Open

BLIP 42: increase payer offer size recommendation to 384 bytes #75

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions blip-0042.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,7 +109,7 @@ The writer of `invoice_request`:
as signature tag.
- If it includes `invreq_payer_offer`:
- MUST encode `payer_offer` as a TLV stream of its individual records.
- If the encoded offer is more than 300 bytes long:
- If the encoded offer is more than 384 bytes long:
- SHOULD NOT include `invreq_payer_offer`.
- SHOULD include `invreq_payer_bip_353_name` instead.
- Otherwise:
Expand Down Expand Up @@ -148,7 +148,7 @@ store in the `path_id` field of the blinded path(s) of the `invoice` they send
back. Since this `path_id` will then be included in payment onions, which are
limited to 1300 bytes, nodes must ensure that the resulting `path_id` isn't too
large, which would constrain the payment paths that can be used by the payer.
We thus recommend only including offers that are smaller than 300 bytes in
We thus recommend only including offers that are smaller than 384 bytes in
`invreq_payer_offer`, or a small BIP 353 HRN.

When a BIP 353 HRN is included, the node receiving `invoice_request` does not
Expand Down