NUT-01: return keyset metadata #325
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Expose `active` and `input_fee_ppk` on keysets returned from `/v1/keys` and align the `/v1/keys/{keyset_id}` example accordingly.
This lets wallets derive the keyset ID and associated keyset metadata from the `/keys` payload without an extra round-trip to `/keysets`.
Collaborator
|
We probably need the |
Contributor
Author
yes, that would have to wait for or be merged into the keyset v2 PR |
Contributor
|
Will resolve issue: #289 |
prusnak
approved these changes
Jan 9, 2026
5 tasks
This was referenced Jan 11, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Expose
activeandinput_fee_ppkfields on keysets returned from/v1/keysendpoint and align the/v1/keys/{keyset_id}example accordingly.This allows wallets to compute the keyset ID and access associated keyset metadata directly from the
/keysresponse without requiring an additional round-trip to the/keysetsendpoint.closes #289