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

BOLT2: rephrase cltv_expiry_delta text about accepting HTLCs #595

Open
wants to merge 1 commit into
base: master
from

Conversation

Projects
None yet
3 participants
@harding
Copy link

commented Apr 2, 2019

Saying "the risk is only to the node accepting the HTLC" is confusing
because merely accepting an HTLC is risk-free. The risk comes from
accepting responsibility to route the payment, i.e. offering an HTLC
of your own in the next channel on the path, where a too-small
difference in the HTLC values could end up with you cheated out of a
payment.

This revised paragraph hopefully makes that clearer.

(My thanks to @jnewbery and @cdecker for helping me understand what was going on here.)

@jnewbery

This comment has been minimized.

Copy link

commented Apr 2, 2019

This seems like a good clarification to me. ACK.

BOLT2: rephrase cltv_expiry_delta text about accepting HTLCs
Saying "the risk is only to the node *accepting* the HTLC" is confusing
because merely accepting an HTLC is risk-free.  The risk comes from
accepting *responsibility to route the payment*, i.e. offering an HTLC
of your own in the next channel on the path, where a too-small
difference in the HTLC values could end up with you cheated out of a
payment.

This revised paragraph hopefully makes that clearer.

@harding harding force-pushed the harding:2019-02-bolt2-cltv-delta branch from cca3723 to 3908829 Apr 2, 2019

@cdecker

This comment has been minimized.

Copy link
Collaborator

commented Apr 10, 2019

I like it 😃

ACK 3908829

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.