I'll try this year. Not sure all features will be possible.

Reserve is 1% min 1 sat I believe.

Test zapped just in case!

Test zap on me!

Did you do some wallet address changes or recovery recently?

Please DM me your sentry id from Developer screen, will check it.

DM me the payment hash, I can check the exact route.

Lightning fee is charged by routing nodes, not the one initiating the payment.

First this year's over-the-air release is shipping!

@Minibits is now sending ecash using much more privacy preserving type of Nostr direct messages (NIP17).

@Minibits supports recent addition to Cashu protocol: you can now scan and pay Cashu Payment Requests (creating not yet ready)

And few fixes coming along as well. Enjoy 2025!

212th was it, not sure how many before are active.

Check dm. You have created your profile before seed based recovery was even ideated :)

I can fix it for you as for the oldest minibits user still alive manually.

To which lightning address? There are only lightning routing fees when zapping, so nothing I can control. No ecash melt/swap fees on Minibits.

Ok, I'll check the state of the topup on the mint side and come back over the DM.

Please if you have, DM me the preimage (proof of payment) ftom the sending wallet.

Thanks!

There were few reports regarding app freezing. There is an issue #128 on github related to that.

If you do have any circumstances when it started please reply here / comment the issue (you might try to turn off / switch to another network connection to see if it's not network related).

For some users, reinstall fixed the issue.

If you keep original seed phrase you'd book your address with, go to Settings > Recovery > Wallet address recovery.

This recovers wallet address only, without the balance.

From the last release, it keeps existing wallet seed (not rotating to the provide one, just getting the address back).

This looks broken. Try to go to Settings > Recovery and press Remove spent ecash.

Then try to zap your own note or self-send to your minibits address from the wallet itself if you see any transaction errors. If so, dm me tge audit trail from such transaction.

Could you try to send few sats as an ecash to yourself to make sure wallet can receive (send as ecash - copy token - receive ecash - paste)?

If there's any error, dm me the related transaction audit trail. I'll check on lnurl server side if those zaps were claimed by tge wallet or not.

1. Create NWC connection, tap QR code icon and press Copy

2. Go to Amethyst

3. Long-press zap icon on any note

4. Tap Paste icon to paste NWC connection string from Minibits

6. Save

You need to have push notifications in nostr:nprofile1qqstxwlea9ah3u6kjjszu6a7lrnhqkfh8eptp2z6v0e9558tlkkl2rgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszxnhwden5te0wfjkccte9ekkjmnfvf5hguewvdshx6p07xr4s5 enabled and working for NWC integration to work when app is in the background or switched off.

Should not be the case

Do you see device token below Notification settings item?

App coming in foreground or visiring Wallet screen, once per 60s

NWC requires firebase push notifications enabled and working. Graphene might miss google play services required for it to work.

You can be sure it works when you can see the device token below Norification sertings menu item.

Don't you see View more button below the transactions list? If not please try to adjust system font type or size if that helps.

To connect your #Minibits wallet to #Primal, #Amethyst or another Nostr app, generate Nostr Wallet Connection string in Settings and paste it to the app to be connected with.

You can set a daily limit in order not to zap your full ecash balance the very first day - experience is a little addictive!

If that's the case it may trigger dos protection on Minibits mint already when requesting invoiced and ban the source ip address for few hours.

Thank you. Freezes were very likely caused by hanged requests to minibits server. Hopefully will be gone after the changes I did on server side (no need for app update due to this so far)

If you do not see view more below the list, could it be that the device has some unusual resolution?

Please send the device screen width x height ratio so I can try it on simulator.

What would be the inspiration for a new one?

From what I see some part of Minibits users on graphene have them uninstalled.

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

Sounds interesting, however I can't see such setting on my Samsung device. Which one has it?

Definitely worth further investigation.

The issues with failing zaps over nwc are really annoying. Thanks to few folks that helped me by setting debug logging (don't do normally) I was able to track that issues are caused by android interrupting background processing, mostly when it keeps running longer due to a casual zapping that adds zaps over time.

In any case, working on an improvement, still about to test how much it will help but promising.

Any other setting that could help is more then welcome, we need to make this use case work to at least to 95% success rate.

Yes, only single wallet.

Your wallet picked a lot of small denomination ecash notes to match requested amount to pay.

Like youd'd bring a bag of dimes to the shop.

You should be able to ask your mint to exchange it for larger denominations in Settings > Backup > Optimize proofs.

This tool exchanges your small coins with the mint in batches, so you wan't hit the limit.

When done, get back and pay!

You're right that a race condition could lead to the same or similar other issues.

Your original 100sats were represented by ^2 set of proofs (ecash notes) at the beginning - 64,32,4. To get 1sat, (let's ignore fee reserve for simplicity) wallet takes 64 proof and swaps it with the mint for 32,16,8,1,1 and uses 1sat proof to settle payment.

For lightning fee reserve, mint retutns unused fees as a fresh ecash back to wallet.

So plenty room to race inside the wallet state or get out of sync with the mint in case of parallel/async processes.

Minibits internally uses synchronous queue for all ecash ops to prevent that + locks during network requests (so it can e.g. recover back sent ecash when mint response won't come at all).

Even technically prevented, I still might have some logical issue leading to race condition but was not so far able to pin it. As it happens much more often with nwc, background procesessing is suspicious to me as well.

Will repeat your exact 20x1sat zaps test case on dev device.

Minibits and Coinos have direct lightning channel with plenty of liquidity. From github issue it sounds like lnurl link returned the actual error, could be some temp issue as the link works for me.

What's up? Feel free to dm if you prefer.