Settings > NWC, create connection and copy it. In Amethyst long press zap icon then paste and save.

Requires push notifications to work on your device so that minibits can wake up on incoming encrypted nwc command.

Get to Settings > Backup and Recovery and press Increase recovery indexes. Should be ok then.

Expand params or copy me whole audit trail of such error

Just got your zap, thanks.

Do you see error transactions in the wallet?

Are you sure you have pish notifications enabled and working on your device?

If yes try to zap your own nostr note (with minibits lightning address on your profile) so you can filter out lightning routing errors.

Where do you see Minibits charging a fee? If you pay some, they are for routing the lightning payment.

Fixed just now in the first over the air release for this new version. Just accept an update notified in Settings > Update manager

Minibits is an ecash wallet fully interoperable with lightning. Ecash are digitally signed notes issued by mints, backed by bitcoin in mints lightning channels.

Ecash has few nice properties like low friction onboarding, fast, private and mostly free transactions, working even offline as it is physically stored on device.

Price paid for this is necessary trust to issuing mints that their ecash can be redeemed back for bitcoin on demand.

Minibits wallet adds to that mix lightning addresses and good fit for nostr zaps giving and receiving including nostr wallet connect and more.

Thanks, will check it!

Next year if I manage to get some help.

Now it's more clear. When you try to send to a lightning address directly from the wallet, you should get transaction with error. Go to transaction detail and DM me the audit trail from the bottom of the screen.

I'll then see exact error that we can sort out. After nwc will resume to work as well.

New Minibits is here!

Redesigned wallet screen, fiat rates, improved performance and storage reliability. And new golden theme for true gold bugs - until we'll get gold ecash!

This is a native release so upgrade from Google Play or grab it from our Github.

v4 format is now default in new Minibits release.

To run your owm mint, check cashubtc/nutshell om github.

If it happened after recent native version upgrade, just restart to refresh it, no need to do any recovery. Sorry for troubles, dm me if you need more assistance.

Last upgrade makes heavy storage migrations to improve reliability but brings this issue along - still working on it.

New v4 ecash encoding format is more efficient, so it fits more ecash into standard QR code.

I prioritize that over the animated codes, because they are much less interoperable (can't be scanned easily with standard readers etc).

Will see how far we can get with that, if there will be the need I'll implement animated ones.

As well make sure in Settings you have notifications enabled + you see device token below the label.

Zapped you from Amethyst. Can you try to pay to your own lightning address from the wallet directly to make sure basic wallet and paying to an address is ok? Dm me any error if you'd get one.

On Graphene OS you might not be able to receive push notifications (requires Google Play services). If that's the case, background processing of incoming nwc commands can't work.

Backup option is to receive commands over nostr relays, but that works reliably only if the app is running and foreground - not really practical.

QR code fails to show if the amount of data the token takes is too big for QR code to be rendered. This depend on how many ecash notes are selected by the wallet to match requested amount.

In such case, there is option to copy or send ecash to another wallet address (contact) over nostr.

If you select another amount resulting on less ecash notes, QR code will show again.

Cashu mints are connected to Lightning so you can withdraw to any Lightning wallet but not directly onchain.