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

keysend text fields #5619

Merged

Commits on Sep 21, 2022

  1. keysend: try to find description in TLV.

    "Who needs specs?"  FFS...
    
    Signed-off-by: Rusty Russell <[email protected]>
    Changelog-Added: Protocol: `keysend` will now attach the longest valid text field in the onion to the invoice (so you can have Sphinx.chat users spam you!)
    rustyrussell authored and cdecker committed Sep 21, 2022
    Configuration menu
    Copy the full SHA
    c3f24a6 View commit details
    Browse the repository at this point in the history
  2. keysend: allow extratlvs parameter, even in non-experimental mode.

    Signed-off-by: Rusty Russell <[email protected]>
    Changelog-Added: JSON-RPC: `keysend` now has `extratlvs` option in non-EXPERIMENTAL builds.
    rustyrussell authored and cdecker committed Sep 21, 2022
    Configuration menu
    Copy the full SHA
    76e340c View commit details
    Browse the repository at this point in the history
  3. lightningd: allow extra tlv types in non-experimental mode.

    The old `experimental-accept-extra-tlv-types` is now `accept-htlc-tlv-types`.
    
    Signed-off-by: Rusty Russell <[email protected]>
    Changelog-Added: Config: `accept-htlc-tlv-types` lets us accept unknown even HTLC TLV fields we would normally reject on parsing (was EXPERIMENTAL-only `experimental-accept-extra-tlv-types`).
    rustyrussell authored and cdecker committed Sep 21, 2022
    Configuration menu
    Copy the full SHA
    4e3ac28 View commit details
    Browse the repository at this point in the history