Add keyset expiry field to /v1/keysets response #229

Open
opened 2025-02-20 14:01:59 +00:00 by callebtc · 2 comments
callebtc commented 2025-02-20 14:01:59 +00:00 (Migrated from github.com)

Keysets should have a pre-announced expiry so that wallets can either rotate to new keysets or recognize that a mint is shutting down.

Keysets should have a pre-announced expiry so that wallets can either rotate to new keysets or recognize that a mint is shutting down.
a1denvalu3 commented 2025-02-20 14:05:01 +00:00 (Migrated from github.com)
Related? https://github.com/davidcaseria/nuts/pull/1
ok300 commented 2025-02-21 13:32:45 +00:00 (Migrated from github.com)

Agree, I think this is redundant, as a keyset expiry field is already part of the Keyset ID V2 PR (#182) , thanks to @lollerfirst 's contribution to the PR (linked above).

Agree, I think this is redundant, as a keyset expiry field is already part of the Keyset ID V2 PR (#182) , thanks to @lollerfirst 's contribution to the PR (linked above).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo-admin/nuts#229
No description provided.