Not sure with this one for now, sorry.

Check if you see notifications enabled and device token shown in Settings.

As well send few sats to yourself so you are sure basic wallet works.

Please restart the wallet after upgrading.

Last update made more efficient v4 QR codes as default. You should be able to switch to legacy QR code format using an option below the code.

Please restart the wallet, there are migrations after the upgrade that cause in some cases the balance to not refresh. Next restart should solve it.

Sorry for troubles, working on that.

Please restart the wallet once again.

Dm'd you

Hey, if transactions remain in DRAFT and do not follow up try to send all your balance as ecash to yourself (send as ecash > enter whole balance > copy token > receive as ecash > paste to receive.

DM me if it won't help or you need further explanation.

Do you see any transaction with error in the wallet or you just don't receive zaps at all?

Successfully zapped.

How fast the zap appears (if ever) in Amethyst depends on the receiving lnurl server, that publishes so called zap receipt event when the zap invoice has been paid.

So Minibits can't influence it if receiving lightnig address is not a minibits address.

Excited to announce that Minibits has become one of the nostr:nprofile1qqs8suecw4luyht9ekff89x4uacneapk8r5dyk0gmn6uwwurf6u9ruspzpmhxue69uhkumewwd68ytnrwghszxthwden5te0wfjkccte9eekummjwsh8xmmrd9skctcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhs2juazd grantees 🎉! Grateful and dedicated to push forward with open-source ecash R&D for #Bitcoin!

Ok will change it in the next release.

Agree, relay[] is supported encoding in query strings, but I'm afraid it might not be what nwc clients expect.

Will consider to point it to my strfry instance relay.minibits.cash

There is indeed and was even made more accessible and with copy button in the last version.

However, if both payer and the payee use the Minibits mint, it settles invoice internally - in those cases preimage is missing.

Minibits addresses are as well nostr identifiers. However nsec key is never exposed to the user as it is meant to send and receive ecash, not to be used in other nostr clients.

Spec says that relay param may be more than one. You're right that multiple relay params in query string looks weird but that was what I've seen in some other implementation.

If it is indeed wrong encoding, I'd be happy to fix it but would prefer not to rely on a single relay.

Zeus lightning address works with so called hodl invoices - invoices do not settle immediately on receiving zeus node unless the payee opens the wallet. This breaks zaps flow, so I'd recommend using another lightning address provider for zaps.

Sounds like a network issue.

What comes to my mind that If you're using vpn, it could be that their exit ip could hit mint dos protection rate limits if many use the same one (?)

Please dm me related transaction audit trail from tx detail.

I have one another similar report and it's likely same bug, tx is wrongly completed, logs will confirm that.

I'll prepare the fix. Seed recovery should get your sats back until then.

Make sure you are on latest version beta.65 and restart.

If pending won't resolve after that, hack is to copy it from local recovery tool as encoded token and paste it to receive back to spendable balance.

Urgent user call got me back to work!

#Minibits now displays profile pictures of zaps or ecash senders and 🔗links 🔗 to the zapped note from transaction detail.