You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my use case, I need to sign transactions with a relative lock-time using nSequence with the 1 << 31 bit off (See: BIP68).
When some of the inputs have an nSequence with the 1 << 31 bit off, I want to see the transaction-id of that input, and the time-lock whether it is defined in seconds or blocks.
It is highly important in my case not to sign a transaction unless I know that the relative lock-time is set. This is similar to absolute lock-times that are already implemented and displayed on my Trezor One screen - except that relative lock-times depend on a previous transaction-id.
If this feature is already implemented in the more modern trezors, please let me know.
In my use case, I need to sign transactions with a relative lock-time using
nSequence
with the1 << 31
bit off (See: BIP68).When some of the inputs have an
nSequence
with the1 << 31
bit off, I want to see the transaction-id of that input, and the time-lock whether it is defined in seconds or blocks.It is highly important in my case not to sign a transaction unless I know that the relative lock-time is set. This is similar to absolute lock-times that are already implemented and displayed on my Trezor One screen - except that relative lock-times depend on a previous transaction-id.
If this feature is already implemented in the more modern trezors, please let me know.
More information on my use-case can be found here: https://timelockrecovery.com
The text was updated successfully, but these errors were encountered: