-
-
Notifications
You must be signed in to change notification settings - Fork 652
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
Investigate CSV (CHECKSEQUENCEVERIFY) usage #706
Comments
@romanz Can you help us with finding the right person to document how exactly does the scripts in Blockstream Green look like? (We don't like signing arbitrary scripts, so we have to understand the structure first and "teach" Trezor how to build transactions like these). |
Green wallet is using libwally-core for generating the Bitcoin scripts for CSV-based multisig. There are currently two types of such scripts (where
There is a proof-of-concept trezor-firmware branch that allows the user to create p2sh & bech32 addresses controlled by the first type of CSV-based multisig script above and spend from them. CC: @greenaddress |
Thanks for the code! We'll have a look at it |
I agree it makes sense to do this, but we need to refactor the |
Sounds good, thanks for the update! |
Updated and rebased |
Rebased over latest master and force-pushed 95979fc. |
Related to #416. |
Also the miniscript policy for a 2-of-2 that turns into a 1-of-2 after 90 days: |
Some wallets (such as Blockstream Green) use CSV (CHECKSEQUENCEVERIFY) in their scripts. Let's ask them how their scripts look like and see how we can integrate this into our protobuf messages.
The text was updated successfully, but these errors were encountered: