<unnamed>

Public Key

npub1kvaln6tm0re4d99q9e4ma788wpvnw0jzkz595cljtfgwhldd75xsj9tkzv

Profile Code

nprofile1qqstxwlea9ah3u6kjjszu6a7lrnhqkfh8eptp2z6v0e9558tlkkl2rgpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq32amnwvaz7tmjv4kxz7fwdehhxarj9ehx2aqvysg9l

Publishing to

relay.damus.io

relay.nostr.net

Last Notes

2026-03-09 10:20:20 CET

- reply

I believe than you'd need to trust that the TLS certificate + domain name matches the mint's domain.
You've had trusted the mint already when you've minted the ecash.

2026-03-06 22:31:17 CET

- reply

Any estimate how many proofs token was that?

2026-03-04 20:35:53 CET

- reply

Apps are compiled from source code - that's what programmer writes. By inspecting the source code, you can see how your seed is processed.

2026-03-03 07:19:08 CET

- reply

What about checking the github before making conclusions?

2026-03-03 07:18:24 CET

- reply

On minibits-cash github. Still early version, missing readme.
All minibits related variables are in the .env, so that it can be deployed by other mint operators without code change, to speedup recovery from their owm mint.

2026-03-02 16:10:18 CET

- reply

Yes indeed! Make sure to run 0.3.4-beta latest version.

2026-03-02 16:08:01 CET

- reply

Wallet needs to handle such case and return pending ecash back to spendable balance.

2026-03-02 14:18:08 CET

- reply

Well my nostr keys could be stolen but the tool still runs on minibits domain if that helps.

2026-03-02 14:15:09 CET

- reply

I hear you and that's correct. Use when really needed and rotate to a new seed after. Sourcr code is available.

2026-03-02 14:12:15 CET

- reply

What a promo!

2026-03-02 08:37:54 CET

- reply

Your seed prase never leaves your browser, yet most of the process happens on the server, vastly improving performance.
Single recovery round scans up to 2500 recovery indexes, that should be enough for most wallets.
To prevent attack on mint resources,
further recovery rounds cost 100 sats, charged using brand new HTTP 402 standard (NUT 24 spec) - pay for api use with an ecash token.
Free use then resumes after 15 minutes, based on ip address.

2026-03-02 08:29:21 CET

Nobody likes losing hard-earned cash — zaps even less so!
Unlike paper cash, ecash can be recovered using your seed phrase, but until now the process has been painful, especially on mobile devices.
Meet recovery.minibits.cash 🚀
A re-architected recovery tool for the Minibits mint, optimized for performance.
https://blossom.primal.net/6eac13f1e19d003ee602ee79b361ad6c9bc18845a6942bdd42e5483a4527a8e6.jpg

2026-02-13 21:42:40 CET

- reply

Looks like some internal app state / navigation issue. I do not expect compromised device to behave like this. Try to restart the app and retry with few sats. If it persists, would be of great help to make a video and dm it to me or send it to support at minibits dot cash.

2026-02-11 23:04:48 CET

- reply

Both still in-flight on lightning side. Such long delay indicates some failure during routing. In extreme cases, resolution takes time up to few days (depending on cltv delta setting on related channel)
https://blossom.primal.net/6559592c47c99e8d929c2821823ba277192b3dd6f3c6e6bd0f237628cf3f06f4.jpg

2026-02-07 09:14:25 CET

- reply

You're right it's not optimal for few reasons:
- you've hit a combo of a bug and long history
- unfortuntely on mobile device the recovery ops take few secs for each round
- fresh wallet nor mint can't know where the unspent is, unless we know the last counter values (you can check them in mint screen before you reinstall and set the starting point in Minibits - if you do not deal with device loss that can help).
I have some idea on how to make complex recoveries much easier. Will think of it more.

2026-02-06 16:31:37 CET

- reply

DM me the payment hash or an invoice please

2026-02-03 08:23:03 CET

- reply

Checked your payment, thank to the not typical amount. It is failed on lnd node and on the mint side so your sats should not be blocked anymore.
Do clean recovery again.
Lightning can keep payment in flight / pending for some time in rare cases until it finally fails.

2026-02-03 08:07:28 CET

- reply

Everybody should have own 24s. Cash is funny and useful but only with little amounts.

2026-02-03 02:09:02 CET

Minibits went through an unplanned outage of the server running the mint's lightning node. It is now back up and operational.
However, as a result of the outage part of the lightning channels are in the closing process. Most remain operational with enough liquidity and I do not expect user issues when reaching Minibits node.
I am really sorry notably for troubles caused to partner lightning node operators with whom the channels are force closing.

2026-02-03 01:32:35 CET

- reply

Please try the recovery again and make sure you are on the latest 0.3.4-beta.23 version - there was a bug that should be fixed now.

2026-02-02 20:29:31 CET

- reply

Minibits can write the token to the nfc tag and lock it to the public key (Send ecash > Lock to pubkey > Create token > Tap on nfc icon below QR).
Need to be NFCTagType4.

2026-02-02 19:39:49 CET

- reply

Definitely move out of 0.3.2, missing critical fixes.

2026-02-02 17:29:14 CET

- reply

Restart the wallet to get an update 0.3.4-beta.23

2026-02-02 17:20:45 CET

How about having a pro Pay with NFC screen in Minibits ✨️
Payment card mimics is so oldschool, but don't we all keep nice little things we do not really need anymore?
https://blossom.primal.net/13a062df8ec375dbc315334d91fa1c3848f024e59abec4838e61cd0bbe8ed753.jpg

2026-01-30 13:54:08 CET

- reply

Please restart the wallet so that it force syncs pending proofs with the mint.

2026-01-30 00:18:47 CET

- reply

#nevent1q…wane

2026-01-28 08:26:42 CET

- reply

Yor wallet likely contains ecash generated using older mint keyset.
After recovering what you have now, still on recovery screen, choose Select keyset at the bottom of the card. Then select previous keyset starting 005... and go through necessary recovery intervals again to get the second half of your balance.

2026-01-28 00:28:13 CET

- reply

I don't think zapstore can break it.

2026-01-27 17:41:26 CET

- reply

Then it's still 0.3.2
#nevent1q…f5uz

2026-01-27 17:39:47 CET

- reply

Mints are part of the backup if you did not exclude them.

2026-01-27 15:01:22 CET

- reply

I've retested that and indeed have the same result. Not sure why, because I can download the APK from both Github and Zapstore CDN without issues.
Here is the APK published on Github that Zapstore downloads when publishing new release:
https://github.com/minibits-cash/minibits_wallet/releases/download/v0.3.4-beta.19/app-arm64-v8a-release.apk
Here is the link to Zapstore CDN download:
https://cdn.zapstore.dev/01a40098cec0e5eff3cf570752c356daabdbffc31536fa9cca162ce83dabee5b
SHA256: 01a40098cec0e5eff3cf570752c356daabdbffc31536fa9cca162ce83dabee5b
Sorry for troubles not sure why it's not downloading from Zapstore app, links on thir web https://zapstore.dev/apps are updated and pointing to the new release.

2026-01-27 14:03:14 CET

- reply

I you are using Zapstore, check if there is an update again, I've re-published the release events.

2026-01-27 13:45:49 CET

- reply

Do you see NFC icon in the top right corner of the main wallet screen?

2026-01-27 13:23:42 CET

There are reports that users installing Minibits on Android from Github and Zapstore are not getting over-the-air wallet updates.
I therefore released a new cumulative update of current native version including all OTA updates as an APK package to Github and Zapstore, tagged v0.3.4-beta.19.
Please check the version you are running in Settings > Developer options:
👉 if you still run old release 0.3.2-beta.x, please update immediately, there were important bugfixes released over time in 0.3.4. This is valid for all users, including those that use Google Play.
👉 if you run 0.3.4-beta.8 or beta.11 and you are not offered OTA update in Settings > Update manager, please check Github or Zapstore and upgrade to the new version
✌️ if you run 0.3.4-beta.19, you are running the best Minibits out there.
Enjoy!

2026-01-15 21:41:35 CET

Happy to share that @nprofile…vavr has been selected for continued grant support from @nprofile…uazd 🎉
Grateful for the trust and excited to keep pushing open-source ecash R&D for #Bitcoin forward!
https://blossom.primal.net/1980bbca25e3e6b6073e0ff17c5ff7ad9ed3c2bc5cd70ba83e264defca5e32dd.jpg

2026-01-08 19:55:10 CET

- reply

I might have the fix by tommorow, will update you.

2026-01-08 18:54:44 CET

- reply

Do you have the seed from previous device?
You still can:
1. Wait for the fix and try to import the backup file again, later recover wallet address only using the seed.
2. Use your seed to re-create the balance doing full scale balance recovery (can take longer with wallet with a long history, that's why backup option exists)

2026-01-08 16:29:17 CET

- reply

Sorry there is a bug in the recovery from backup. Will work on the fix.
In the meantime, if you have old device and app still on, move your balance to another ecash wallet, e.g. web based cashu.me and then back to new device.
If you had your own address, use the seed to recover address only (no need to go through full balance recovery).

2026-01-04 17:28:08 CET

- reply

Which wallet?

2026-01-04 13:28:59 CET

- reply

Yes, send to yourself or between two different ecash wallets. Every receive swaps full amount received to new keyset.

2026-01-04 00:11:50 CET

- reply

Ignore the bot.

2026-01-03 23:49:26 CET

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!
https://nostr.download/ae9102c4186688accc4f4c30482b1aa684bf7c08fe82a706a51d1e456ca81224.jpg

2025-12-20 15:50:35 CET

- reply

Hi, after you restart, do you see any receiving transactions with error status in the list?
As well, try to make regular send / receive transaction within the wallet (not nwc) to make sure wallet itself is operational.
Minibits batches received tx if there is more then 5 to claim when wallet starts. Batching can be turned off.

2025-12-03 22:24:47 CET

- reply

Checked the payment, it was paid and server says that it issued the ecash just after.
Either wallet might have missed the response, very rare but happens.
Or you might have an incoming transaction with error (if wallet failed to swap for fresh ecash for any reason).
In any case I set the ecash as unclaimed to force the wallet to claim it again. Restart and dm me any transaction details / error you'll get.

2025-11-30 17:43:33 CET

- reply

Wallet tries to heal that, but if there is more it could repeat.

2025-11-30 17:42:35 CET

- reply

NWC is not an ecash mint feature, so you can't switch unfortunately.
Pending means some of your balance is pending on the mint side, linked to some previous lightning payment that did not complete.
Try Recovery > Remove spent ecash.

2024-12-02 23:19:38 CET

Let's keep the zaps flowing 💦 !
Latest update brings single but important architectural change: Nostr Wallet Connect (NWC) commands now run via Android's foreground service. This should help to reduce interruptions and ensure smoother transactions. You may even see the NWC activity in the status bar 🚀 !
As this is a native release, get it on Google Play or grab the APK from our Github.
https://m.primal.net/MmSH.mp4