Make sure you are on latest 0.3.2-beta.9. Then please set logging level to DEBUG in developer settings. Restart the wallet and ping me once done + pass me your sentry id shown alongside wallet version over the DM. Move log kevel back to ERROR. Thanks!

I've rotated keys once more then a year ago, old ones are still there inactive (with ecash redeemable). You can count on min 1 year period to swap to new keys.

The mint can expire and rotate to new keysets over time to manage the db growth of spent ecash notes it needs to track to prevent double spend. Older keyset can still remain inactive but with ecash redeemable after the new one is introduced - up until the mint operator decides to remove it. Such period should be long enough for users to swap their ecash notes to new keyset - this is mostly handled by wallets while in use. Mint operator can not "use your ecash", as the mint does not keep any unspent - only wallets can. If you lose it for good, wallet operator has surplus BTC reserves on his lightning node.

Could you dm me an audit trail of the first transaction where you've got "proofs pending" error? Should be a lightning transfer. Message "proofs are pending" is returned by mint in case lightning stays in-flight. Wallet normally keeps such ecash notes reserved to settle the payment in ending state as well and moves them back o spendable balance only when mint confirms that related payment failed on lightning side. If you get this error, smthg broke, could be on the mint side. with an audit trail I can check mint/lightning node for specific payment status.

Somebody else did it apparently before - token is already spent

Test zappes

Do you see any prior lightning transaction in pending/error state? If so, dm me its audit trail from tx detail screen. As well, try to restart the app in case it failed somehow to sync proofs state with the mint.

Please see my prev message. Something is def broken but can be sorted out. Make sure to have seed backed up for now.

NWC supports mutiple commands that might have subtle differencies across implementations on both sides. Here it looks like passing the balance does not work properly. Nevertheless, I would not recommend to connect two apps on mobile devices over nwc unless testing - too many moving parts to keep it really stable.

Sorry for troubles. Please, if you see recent transaction in error status, DM me the audit trail from the tx detail screen.

Please get the latest over the air update and try again - I've fixed the regression bugs in recovery process as well as focus issue when entering fiat amount.

We are on 0.3.2. You're riding bond's aston martin! OTA updates are released only for specific native version to keep them compatible. Befor updating I strongly recommend to move your ecash to another wallet such as wallet.cashu.me, because the migration scripts might not cover such jump. Backup your seed. Then do not do standard natove update but uninstall. Go to google play or zapstore or get a 0.3.2-beta apk from github, install. After wallet starts, backup newly generated seed. Move your balance back and use your former seed to get back wallet address in Settings > Seed recovery > Wallet address recovery.

I’ve been rethinking how Contacts work in Minibits. First step: Public Contacts now let you search Nostr users by name or address — and see their follower count to avoid fakes.

Makes sense, but there is not yet an implementation of onchain - ecash swap on the side of mints.