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

BOLT 3: Explicit description of implicitly enforced timelocks on HTLC outputs #601

Open
wants to merge 3 commits into
base: master
from

Conversation

3 participants
@nkohen
Copy link

commented Apr 22, 2019

Added descriptions of how a 2-of-2 multisignature verification is used for enforcing timelocks when timing out on-chain offered HTLCs as well as spending on-chain received HTLCs in the success case.

I say implicitly enforced to mean that these timelocks do not show up explicitly in any of the HTLC output scripts.

It took me a lot of time and effort to reason these facts out of the existing documentation so I figured I'd propose to add it.

nkohen added some commits Apr 22, 2019

Added descriptions of how a 2-of-2 multisignature verification is use…
…d for enforcing timelocks when timing out on-chain offered HTLCs as well as spending on-chain received HTLCs in the success case.
@cdecker

This comment has been minimized.

Copy link
Collaborator

commented Apr 29, 2019

Thanks for the contribution @nkohen. While reading the PR we noticed that you mention committing to the time out but never mention how that timeout is specified. It would be nice to have a reference to the locktime specifying the time out in your description.

@nkohen

This comment has been minimized.

Copy link
Author

commented Apr 29, 2019

Thanks for the comment @cdecker! I changed my comment to reference the locktime field of the HTLC-timeout transaction :)

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.