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

LightningPayment first hop custom records #8656

Closed

Conversation

GeorgeTsagk
Copy link
Collaborator

@GeorgeTsagk GeorgeTsagk commented Apr 16, 2024

Description

Based on #8633

This PR adds a new field for first hop custom records to LightningPayment. This allows the sender to specify a set of custom records to be delivered via the wire message update_add_htlc to the first hop peer.

ffranr and others added 9 commits April 9, 2024 18:42
This method adds encode and decode methods to type `CustomSet`. These
methods will allow us to serialise and deserialize a `CustomSet` map as
a byte slice.
- Introduce the field `CustomRecordsBlob` to the type
  `UpdateAddHtlc`.
- Encode and decode the new field into the `ExtraData` field of
  the `update_add_htlc` wire message.
Introduce `ResumeModified` action to resume standard behavior of a p2p
message with optional modifications as specified by the client during
interception.
This commit extends the forward HTLC intercept response with fields that
can be used in conjunction with a `ResumeModified` action to modify the
intercepted HTLC p2p message.
Implement an integration test where an HTLC is intercepted and the
interception response modifies fields in the resultant p2p message.
@GeorgeTsagk GeorgeTsagk self-assigned this Apr 16, 2024
Copy link
Contributor

coderabbitai bot commented Apr 16, 2024

Important

Auto Review Skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.


require.Eventually(ht, func() bool {
ctx := context.Background()
dbgInfo, err := bob.RPC.LN.GetDebugInfo(
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since there's not yet support to retrieve the custom blob from the interceptor, we'll assert that bob receives the first hop records by peeking at his logs

@dstadulis
Copy link
Collaborator

@carlaKC Would you still like to review this? based on your comment on #8618

@GeorgeTsagk
Copy link
Collaborator Author

@carlaKC Would you still like to review this? based on your comment on #8618

given the narrow context of this specific PR & since we're soon changing the base to custom-channel-integration, I think it's better to hold back the reviews for now

Also very closely related to this PR: #8660

@carlaKC carlaKC removed their request for review April 23, 2024 19:37
@carlaKC
Copy link
Collaborator

carlaKC commented Apr 23, 2024

it's better to hold back the reviews for now

Removing myself for now then, feel free to re-add!

if err := firstHopRecords.Validate(); err != nil {
return nil, err
}
payIntent.FirstHopCustomRecords = firstHopRecords
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like the FirstHopCustomRecords field was added in a later commit. I think this one is more temp, but if not, we should move the commit that adds the new field to before this one.

recordsBytes,
)

htlcAdd.CustomRecordsBlob = tlv.SomeRecordT(tlvRecord)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So I chatted with @ffranr about this offline, but instead we only want to be setting ExtraData. All the other logic (further down in the state machine), will only look inside of ExtraData, as it isn't expecting that extra layer of wrapping.

We do want the upfront validation here tho to ensure that w/e we're passed in is actually a canonical TLV stream.

@lightninglabs-deploy
Copy link

@GeorgeTsagk, remember to re-request review from reviewers when ready

@GeorgeTsagk
Copy link
Collaborator Author

These commits are now part of #8660
Closing this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants