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

sphinx: return error source as integer #37

Merged
merged 1 commit into from
Jul 3, 2019

Conversation

joostjager
Copy link
Contributor

Returning as an integer allows a node to occur in the payment path
multiple times.

Copy link
Member

@Roasbeef Roasbeef left a comment

Choose a reason for hiding this comment

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

How is this better than just using the pubkey as is? If they appear multiple times in the path, then they'll be present multiple times in the payment path's circuit.

crypto.go Show resolved Hide resolved
@joostjager
Copy link
Contributor Author

How is this better than just using the pubkey as is? If they appear multiple times in the path, then they'll be present multiple times in the payment path's circuit.

The sender doesn't know whether the failure happened on the first or the second visit of that node.

crypto.go Show resolved Hide resolved
crypto.go Outdated Show resolved Hide resolved
@joostjager
Copy link
Contributor Author

@Roasbeef fixup pushed that adds return struct. I still don't think it is good, for the reasons pointed out above. But it is a small change and the most important thing is to expose the index one way or the other.

@joostjager
Copy link
Contributor Author

@Roasbeef ptal

Copy link
Member

@Roasbeef Roasbeef left a comment

Choose a reason for hiding this comment

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

LGTM 🧬

Returning as an integer allows a node to occur in the payment path
multiple times.
Copy link
Contributor

@cfromknecht cfromknecht left a comment

Choose a reason for hiding this comment

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

LGTM, nice change! ✅

if err != nil {
t.Fatalf("unable to de-obfuscate the onion failure: %v", err)
}

// We should understand the node from which error have been received.
if !bytes.Equal(pubKey.SerializeCompressed(),
errorPath[len(errorPath)-1].SerializeCompressed()) {
if source != len(errorPath) {
Copy link
Contributor

Choose a reason for hiding this comment

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

definitely makes these comparisons simpler 👍

@Roasbeef Roasbeef merged commit ecc936d into lightningnetwork:master Jul 3, 2019
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.

None yet

3 participants