I think Fedimint goes even firther and offloads payment gateways (in Cashu it's a mint's lightning node) yet to separate entities.

You can think of it as: ultimate accountability + radical simplicity + multimint wallets = cashu ecash

vs

potentially more resilient federation + related technical and social complexity = fedimint.

I think both have some merits and it's yet unclear what will work best for what.

#Minibits is an ecash + lightning wallet. You own ecash notes with specific amounts in your wallet that can be sent to anybody or exchanged with the mint that issued them for bitcoin.

Mint is a sort of "account-less" bank. It issues new ecash against incoming lightning network payment and give you back bitcoin against returning the ecash.

While bitcoin is held in custody and you trust the mint honoring its obligations, ecash can circulate with much privacy guarantees, as the mint can not trace actual transactions.

Ecash note is a random number and denomination digitally signed by mint that can be sent in any way, even while offline to receiver. Receiver then exchanges it for fresh one with the mint (eliminating double spend risk) and transaction is complete.

Ecash in combination with instant topups / withdrawals to Liggtning can be passed as a self-bearing token easily over the network or any other communication mean and thus seems to represent viable alternative to scale bitcoin for smaller payments.

Hm only thing that comes to my mind (if wipe and reinstall does not help) without having the device is if you'd try to download and install .apk from minibits github releases page.

It's the same native app code, but react native code is updated to recent version.

Does it crash immediately on start or when you visit Contact screen?

What device? Google Play or .apk from Github?

Thanks for posting, wallet address change apparently failed for you.

Please make sure that you are on the latest wallet version in Dev options. You should see v0.1.6-beta.28 there.

If not, head to Settings > Update manager, you should see over the air update you need to get. Then the wallet address change should work ok.

Write me back how it went, feel free to use dm if you'd need to share more.

Do you see your chosen wallet name in the app header in Contacts?

Not yet, but on the roadmap.

Yes, with built-in lightning address.

Zap from #cashu wallet on the way.

Please check the DMs for followup steps

Not "auto mode" yet. To do that now in Minibits involves creating and pasting the invoice.

On my todo list, there is demand. However would think of and discuss an idea of transfers once user set limit is reached (batching of multiple small ecash receives to lightning withdrawal - either to preferred mint or any lightning wallet).

Do it for every receive means that success rate of such transactions becomes below that of lightning.

As I think of it, you're right - scheman provides ability for the receiver to be offline.

For sender to be offline as well, he would need to prepare the locked token upfront in order to get mint's sig.

I think you'd scan / nfc the receiver pubkey in an offline use case (if receiver is unknown to you).

For techies and why we need this stress test:

Minibits started to have issues with keeping properly incremented recovery indexes (simple counters per each mint keyset) when zaps were introduced.

They kept flowing from nostr relays in parallel, racing the counter that needs to be strictly ordered otherwise blinded ecash sent to the mint will fail and cause the wallet to brick.

Few weeks ago Minibits implemented pessimistic lock on counters. It has improved the situation, however waiting for locks to release blocks singlethread js processing making wallet unresponsive and there were troubles on how to solve edge cases like force-releasing the lock. Simply said, they are great as last resort safety net, but should not play prime.

Enter new synchronous queue that orders coming zaps into strict order a process them one by one, offloading not critical but time consuming tasks to asynchronous event handlers...

This is what we were testing, now released in #minibits over the air update.

So, all heavy zap collectors, head to Settings to get an update!

We made it to 53 zaps!

Let's make #minibits zap queue stress test!

Post me the transaction audit trail to the DM.

If you are sending to minibits.cash lightning address, payment is converted on the lnurl2ecash bridge server to minibits.cash mint's ecash. So the mint will be added on receive.

You can't issue invoice from wallet without having a mint, so that can't go to the void.

Do you know how many transactions your wallet had before recovery? It starts from index 0, so first rounds are usually filled by already spent ecash that is then filtered out. Unspent follows later based on hoe long history wallet had.