Skip to content

bring signatory up to date with the remote signer spec#1257

Merged
thesimplekid merged 17 commits intocashubtc:mainfrom
lescuer97:signatory_up_to_spec
Feb 25, 2026
Merged

bring signatory up to date with the remote signer spec#1257
thesimplekid merged 17 commits intocashubtc:mainfrom
lescuer97:signatory_up_to_spec

Conversation

@lescuer97
Copy link
Copy Markdown
Contributor

@lescuer97 lescuer97 commented Nov 8, 2025

Description

Changes the signatory keyset generation and updates the proto spec to follow this pr

1- Generates new keysets with the correct derivations paths.
2- returns the derivation_index as version
3- add test vectors from remote signer


Notes to the reviewers

This should not affect any already created keyset.


Suggested CHANGELOG Updates

CHANGED

ADDED

REMOVED

FIXED


Checklist

@lescuer97 lescuer97 changed the title bring signatory up to date with the signatory spec bring signatory up to date with the remote signer spec Nov 8, 2025
@lescuer97 lescuer97 force-pushed the signatory_up_to_spec branch from e44ec92 to 4e26d87 Compare November 8, 2025 19:21
@thesimplekid thesimplekid requested a review from crodas November 11, 2025 15:59
@thesimplekid thesimplekid added this to the 0.14.0 milestone Nov 12, 2025
@thesimplekid
Copy link
Copy Markdown
Collaborator

Are there still open questions on this should we bump it to 0.15?

@thesimplekid thesimplekid removed this from the 0.14.0 milestone Nov 17, 2025
@lescuer97 lescuer97 force-pushed the signatory_up_to_spec branch from 891ac38 to 473d6c1 Compare December 3, 2025 14:13
@lescuer97
Copy link
Copy Markdown
Contributor Author

@vnprc @crodas could you take a look at this pr again pls. I think it is ready now

@lescuer97 lescuer97 requested a review from vnprc December 5, 2025 12:43
@lescuer97
Copy link
Copy Markdown
Contributor Author

@crodas could you re run the test? I think there was an error

@thesimplekid
Copy link
Copy Markdown
Collaborator

@crodas could you re run the test? I think there was an error

Its not an error. Cargo.lock file needs to be updated since you added a dep.

@thesimplekid
Copy link
Copy Markdown
Collaborator

@crodas tests are now passing can you review?

@crodas
Copy link
Copy Markdown
Collaborator

crodas commented Jan 6, 2026

Absolutely!

crodas
crodas previously approved these changes Jan 9, 2026
@lescuer97
Copy link
Copy Markdown
Contributor Author

@thesimplekid rebased.

I will do some final tests around compatibility and it should be ready

crodas
crodas previously approved these changes Jan 14, 2026
@lescuer97
Copy link
Copy Markdown
Contributor Author

lescuer97 commented Jan 16, 2026

demo of the spec:

remote_signer_demo_compresed_free_convert.mp4

@lescuer97 lescuer97 requested a review from crodas February 3, 2026 14:31
@ye0man ye0man moved this from Backlog to In Review in CDK Feb 4, 2026
@lescuer97 lescuer97 force-pushed the signatory_up_to_spec branch from 7e694a8 to 00ae02c Compare February 10, 2026 11:23
@lescuer97
Copy link
Copy Markdown
Contributor Author

adding as reference #1556 (review)

@lescuer97 lescuer97 force-pushed the signatory_up_to_spec branch from 48a0c6a to db3eaab Compare February 16, 2026 15:01
@lescuer97
Copy link
Copy Markdown
Contributor Author

Because of interoperability we now send a x-signatory-schema-version header made out of an enum in the proto file called CONSTANTS_SCHEMA_VERSION.

When the protofile is changed this version should be upped.

@thesimplekid
Copy link
Copy Markdown
Collaborator

@crodas can you review

crodas
crodas previously approved these changes Feb 19, 2026
@lescuer97 lescuer97 force-pushed the signatory_up_to_spec branch from 702ad0b to b3b3ffe Compare February 24, 2026 12:43
@thesimplekid thesimplekid merged commit 046ea2b into cashubtc:main Feb 25, 2026
85 checks passed
@github-project-automation github-project-automation bot moved this from In Review to Done in CDK Feb 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

5 participants