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

descriptors: fix analysis of missing signatures post #575 #584

Merged
merged 2 commits into from
Aug 11, 2023

Conversation

darosior
Copy link
Member

Needs more testing but that should do the trick: we need to take into account the derivation path appended to the xpub in addition to the one from the origin!

@darosior
Copy link
Member Author

darosior commented Aug 7, 2023

Rebased on master to fix the flaky functional test in CI.

src/descriptors/analysis.rs Show resolved Hide resolved
src/descriptors/analysis.rs Outdated Show resolved Hide resolved
It's supposed to represent the number of signature per "master" key, i
guess. At the moment it would always be 1 because the origin changes
when we queried more keys from the signing device (because we increased
the account).
@darosior
Copy link
Member Author

darosior commented Aug 9, 2023

Addressed @edouardparis's review comments and rebased on master.

Since wizardsardine#575 we started using
xpubs with an appended derivation path, and the analysis was assuming
there wasn't any.
@darosior
Copy link
Member Author

Reverted the change that broke the MSRV.

@darosior
Copy link
Member Author

ACK 10acc48 -- Edouard ACK'd the child PR at #599 (review)

@darosior darosior merged commit aab328d into wizardsardine:master Aug 11, 2023
18 checks passed
@darosior darosior deleted the fix_spend_info branch August 11, 2023 08:26
darosior added a commit that referenced this pull request Aug 11, 2023
…m `<0;1>`

605c3f6 descriptors: allow the multipath step to be different than '<0;1>' (Antoine Poinsot)

Pull request description:

  Ledger and wallet policies disallow having more than 2 depth after the
  placeholder, therefore we can't do `@1/0/<0;1>/*`, `@1/1/<0;1>/*`, ..
  Instead we have to do `@1/<0;1>/*`, `@1/<2;3>/*`, ..

  Why not? Salvatore also says the cost of deriving another depth is
  non-trivial on a signing device.

  Don't pick a fight with Salvatore, instead just let the GUI (or whatever
  creates the desc) use different multipath steps for keys derived from
  the same xpubs.

  Based on #584. We need to make sure we don't make the assumptions of the multipath step always being `<0;1>` anywhere else the codebase.

ACKs for top commit:
  edouardparis:
    ACK 605c3f6

Tree-SHA512: acccc31730057a59cf0caccfb258c7b3ea2c27e4181636405e23b974952d6832b45a07f3ba9d627e09c3e9b58ab2d2ab95ba4a6d3c4f3d970f56cad981fa4aaf
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.

2 participants