Skip to content

Conversation

@oleonardolima
Copy link
Contributor

backports #863

  • Fixes the implementation of GetKey for KeyRequest::Bip32 when there's Xpriv has an origin, and it matches with the given KeyRequest::Bip32 derivation_path. It should strip the matching part, to correctly derive the key at the correct child number.
  • Updates the existing test to the correct and expected behavior.

…origin

- Fixes the implementation of `GetKey` for `KeyRequest::Bip32` when
  there's `Xpriv` has an origin, and it matches with the given
`KeyRequest::Bip32` derivation_path. It should strip the matching part,
to correctly derive the key at the correct child number.
- Updates the existing test to the correct and expected behavior.
@tcharding
Copy link
Member

Do you want review mate? Why's it draft?

@oleonardolima oleonardolima marked this pull request as ready for review October 18, 2025 21:19
@oleonardolima
Copy link
Contributor Author

Do you want review mate? Why's it draft?

Yeah, I was just waiting for CI, it should be ready to go.

Copy link
Member

@tcharding tcharding left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK 10fd701

@oleonardolima
Copy link
Contributor Author

I'll move this one back to draft while I fix the issue mentioned at the summit, and backport all the fixes at once.

@oleonardolima oleonardolima marked this pull request as draft October 27, 2025 14:04
- fixes the implementation of `GetKey` for `Xprv` with
  `KeyRequest::Bip32` and a key_origin information.
- adds a new test for a scenario where no wildcard is used, and an
  specific derivation index is used.
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