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

Show relative lock-time #4709

Open
oren-z0 opened this issue Mar 1, 2025 · 1 comment
Open

Show relative lock-time #4709

oren-z0 opened this issue Mar 1, 2025 · 1 comment

Comments

@oren-z0
Copy link

oren-z0 commented Mar 1, 2025

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.

More information on my use-case can be found here: https://timelockrecovery.com

@matejcik
Copy link
Contributor

matejcik commented Mar 3, 2025

just as a heads-up, even if we do implement the feature, at this point it is highly unlikely to make it back to Trezor One

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants