Good point. Was meant no to lose individual sender info when the number of incoming is not hindering perf.

However now it batches only from >5 incoming so making it default makes sense.

Hey, dm me if you see any transactions with error and their audit trail you'll find in errored tx detail. Thanks!

Ah sorry, if you do not run high volumes of scripted/automated swaps or melts against the mints, just ignore my comment, I misunderstood yours then.

By dev env I mean that you could quite easily setup your own mint (even one not backed by real sats) for development or testing purposes.

I'd kindly recommend to setup a dev environment for any higher amounts of algo tests. It unnecessarily bloats involved mints state.

Will just validate "ws"

That's tricky as the wallet needs to provide ecash to the mint with request to pay an invoice, but fees are not known upfront. So there is a fee buffer where mint returns not spent / saved fees.

In the next release, the valodation will be relaxed for relay .onion addresses (no wss needed) and url length expanded so they fit in.

It's not 100% sure that the zap sender profile name is tracked within the transaction. Public sender profile is requested from relays at the moment of zap conversion to ecash, but there are cases when it fails and is skipped.

Please try to select another keyset (option in recovery screen just above button to kick off recovery)

Older ecash was typically issued with 9ml... keyset or so.

Check Security settings. With storage encryption on, biometric auth is needed for Minibits to start.

However I do not recommend it for frequent usage, and generally better practice is to keep balances small enough in ecash to not mind such corner case.

Retried and succeeded now. Was something temporary on Wos side serving invoices.

I can't either with nwc from amethyst. Not sure about why for now but will look at it.

Happy we found this workaround and that it worked for both of you.

Nevertheless there is code in Minibits that automates this for at least 6 months deployed that works in most cases.

Hodl invoices are quite hard/time intensive to test so I could not yet simulate your issue where they do not clear out.

Will work on some intermediary solution that will least help to log and investigate such cases.

Thanks for helping to make ecash better!

Could you restart the wallet and then dm me an audit trail of pending tx (copy from tx detail screen)? Thanks

Thank you for headsup, checked ntfy, nice project. It would be unfortunately unusable for NWC use case, as the wallet do not have access to the received notifications.

In case of NWC my server subscribes to encrypted NWC commands published to minibits relay, reencrypts them with own keys and routes them to the right device based on event recepient tag. They are not shown to the user, just used as data carrier passing the commands from relays to the device.

Go to Settings > Backup and Recovery > Scroll down > Tap remove spent ecash.

If you see any other error before this happened, send me the copy of audit trail to the dm. Thanks!

Token is obtained automatically on granting the permission and refrehed on wallet start - user is not involved in it. If it fails to do so, it means that the device has no Play services installed / available.

I've released yesterday a small fix that will fallback to websocket nwc connection in that case (permission granted and device token missing).

Unfortunately this is really a "demo" solution as it will work only when app is in the foreground (means zaps are sent from app on other device / pc).

For cypherpunks there is of course a fallback - if notification permission is not granted, NWC messages keep going over the standard websocket subscription.

Now it is upon the real ones to kick their OS not to close it when the app is backgrounded and then open source that for all others.

I will gladly dissapoint you over the next two weeks of fam holiday!

Nevertheless kraXen will work on it over the next week.

If you're interested to get the name back, dm me what it was. I can delete it from lnurl/nostr address server so that you can book it again. I'll send you your sats back for the second donation back.