Minibits on Nostr: With the New year, Minibits mint rotated to the new keyset with id starting 001... ...
With the New year, Minibits mint rotated to the new keyset with id starting 001...
For most wallets, handling keyset change should be automatic and should not cause any issues.
Former keyset, with id starting 005... is now not active, but stays available for ecash swaps or melts - that allows wallets to rotate to the new one over time seamlessly.
In case you'd need to recover some ecash generated with previous keyset, make sure to set the keyset id to recover from to the previous 005... value as well (if using Minibits wallet)
Reason for this change is to be able to handle the database growth: there is more then 2.5m of issued ecash notes and 2.2m of spent ones, that the mint needs to keep to prevent double spend.
For now, I've implemented mutiple database optimizations to keep it performing + have realtime backups in place, but to be able to reduce the db size in the future, I'll rotate to new keysets at least once per year.
Enjoy the winter as I do!
Published at
2026-01-03 23:49:26 CETEvent JSON
{
"id": "52e6ce6835af0a38ebd275c666918735d22cb1a6fbc61ce4b064be7ae16ab0a6",
"pubkey": "b33bf9e97b78f35694a02e6bbef8e77059373e42b0a85a63f25a50ebfdadf50d",
"created_at": 1767480566,
"kind": 1,
"tags": [
[
"alt",
"A short note: With the New year, Minibits mint rotated to the ne..."
],
[
"r",
"https://2.5m/"
],
[
"r",
"https://2.2m/"
],
[
"r",
"https://nostr.download/ae9102c4186688accc4f4c30482b1aa684bf7c08fe82a706a51d1e456ca81224.jpg"
],
[
"imeta",
"url https://nostr.download/ae9102c4186688accc4f4c30482b1aa684bf7c08fe82a706a51d1e456ca81224.jpg",
"x ae9102c4186688accc4f4c30482b1aa684bf7c08fe82a706a51d1e456ca81224",
"size 272859",
"m image/jpeg",
"dim 2000x924",
"blurhash ZeF?U}9at7bxtSogV@WBbH%%IVWDbcbIj[ayayayMdt6RkjEV@f5kCj[WBxBo#kDn$j@oJayaybH",
"ox ae9102c4186688accc4f4c30482b1aa684bf7c08fe82a706a51d1e456ca81224",
"alt "
]
],
"content": "With the New year, Minibits mint rotated to the new keyset with id starting 001...\n\nFor most wallets, handling keyset change should be automatic and should not cause any issues.\n\nFormer keyset, with id starting 005... is now not active, but stays available for ecash swaps or melts - that allows wallets to rotate to the new one over time seamlessly.\n\nIn case you'd need to recover some ecash generated with previous keyset, make sure to set the keyset id to recover from to the previous 005... value as well (if using Minibits wallet)\n\nReason for this change is to be able to handle the database growth: there is more then 2.5m of issued ecash notes and 2.2m of spent ones, that the mint needs to keep to prevent double spend.\n\nFor now, I've implemented mutiple database optimizations to keep it performing + have realtime backups in place, but to be able to reduce the db size in the future, I'll rotate to new keysets at least once per year.\n\nEnjoy the winter as I do!\n\nhttps://nostr.download/ae9102c4186688accc4f4c30482b1aa684bf7c08fe82a706a51d1e456ca81224.jpg",
"sig": "e326f603ccd98053a5e4ceb05b44caebfa7ec4c3c680aedc905afb79f328494c22f220c2414d73c0b593e0cc93dc19b6231dd88c04038ea21c74c580c45b5736"
}
