Skip to content

Conversation

@roconnor-blockstream
Copy link
Collaborator

Fixes #325.

The specifications for some of the relative time lock jets are nonsensical and
based on a gross misunderstanding of how relative time locks work.  They should
not be used.

However, they are already consensus in Liquid so we cannot elimiante them.  But
what we can do is rename them in order to dissuade their use.

Users can and should use other jets to parse the sequence numbers of individual
inputs in order to properly validate relative timelocks.
These fields are only used to implement broken jets.
They only remain here because they are not part of consensus and cannot be removed.
The previous version was not the expected behaviour.

This new version is more similar to Bitcoin's CSV op-codes, though there are
some subtle difference when passed a 0 argument.
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.

Relative timelock jets have broken semantics

2 participants