MinibitsCash
Minibits

Minibits mint might show "Melt is disabled" error and fails to send payments over lightning.
Issue is caused by new (perhaps too defensive) protective feaure of mint sofware intended to prevent loss of funds.
Happened third time over 3 days, will be solved by a hotfix, ETA not yet known. Until then I've setup an alert and will restart the mint as necessary.
Sorry for all inconvenience, ecash too much safu.

2024-11-03 22:14:43

- reply

Yes, github.com/minibits-cash/minibits_wallet

2024-11-03 08:10:39

How to onboard when time is as scarce as bitcoin. Amazing story.
#nevent1q…57ta

2024-11-01 23:09:34

- reply

Around 1.5 hour. We are back now.

2024-11-01 22:08:24

- reply

Hm that's something related to the recent nuttshell mint upgrade. Will need to discuss.

2024-11-01 17:12:51

- reply

Check the error detail in related transaction audit trail in the wallet.

2024-10-31 21:56:38

- reply

Regarding the round trip duration: Minibits can't fully match the latencies of custodial / server side wallets.
When you zap someone with nwc, published event with encrypted command is read by the server but then encrypted again with server key and routed through remote data push message to target device with Minibits wallet.
After wakeup, Minibits asks mint for a mint quote, might need an ecash swap with the mint to prepare the ecash and forwards it to the mint.
The mint settles an invoice, it is then still upon receiver to figure that out and to publish the receipt.
I would say, one should not expect that to match custodial lightning wallet latency.

2024-10-29 19:15:47

- reply

Have no control over bitcoinmints, but the mint itself works quite ok (for keeping few sats for your zaps or casual lightning needs, not more than you'd regret over a minute)

2024-10-28 13:24:55

Some folks have just printed paperwallets out of Minibits.
Did they let their meetup visitors to geo-cache the vouchers for a welcome drink? Could not find the source of the vid to ask. Awesome.
https://video.nostr.build/b6d4e95d253086e957354766cefb9e7c907145e2854596481dd444f0b353c505.mp4

2024-10-18 14:46:31

- reply

DM me your minibits wallet address. I'll check if you have push device token registered and send you few sats to make sure notifications are working.

2024-10-18 14:06:55

- reply

Do you have push notifications working on your device? Requires Google play services installed.
If so, try to send few sats to some lightning address from the wallet to make sure that wallet is basically operational.
If you get some error, dm me transaction detail - audit trail data.

2024-10-18 13:50:55

Animated QR codes made it to Minibits wallet! ✨️
Good for sharing really big tokens or if your alternative ecash wallet scanner is barely half-blind. 🥸
Grab animated 121 sats now!
https://video.nostr.build/38e76adb571cce77d6441288b3813dd3fdf1abb82b6bfd08cbfa96cfbc99e280.mp4

2024-10-16 17:42:58

- reply

Please dm me the audit trail from related transaction detail. Thanks!

2024-10-15 08:52:36

- reply

Thank you for testing it! There is definitely a room to improve the process.
Will consider to add proofs swap as an option to the backup screen if the number of proofs is above some limit.
Another option is backup to file, but would require more app permissions and dependencies.
Yet thinking of to encrypt the backup to a seed by default so that it is safe to be copied/pasted in transit.
You've executed with a style with what we have now.

2024-10-14 05:50:58

- reply

This makes perfect sense. As we deal with ecash, I optimized for nostr addresses, so that sending pure ecash works.
But I see that having pure lnaddress contacts should be possible.
Will think of it how to do it without adding too much complexity (I validate contacts against profiles onnostr relays etc...)

2024-10-13 18:42:17

- reply

Switch QR to the new v4 format, makes QRs much more readable. It's the default on latest Minibits.

2024-10-05 08:10:21

- reply

Please check in the related errored transaction audit trail what was the error detail as stored in error.params.message.
If that's Token already spent, then remove spent ecash tool helps.
I have a bug there that it does not show the result correctly in the modal, but works anyway, will fix that.
If it's something else, dm me the audit trail and we'll sort it out.
I see more cases with spent ecash related to nwc usage. I'm afraid that android might kill the background app nwc process before it fully completes, but this is very difficult to simulate and even device and battery level specific. Will dig into that deeper over time.

2024-10-05 07:52:55

- reply

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.

2024-10-04 23:06:59

- reply

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

2024-10-04 22:59:50

- reply

Expand params or copy me whole audit trail of such error

2024-10-04 22:47:49

- reply

Just got your zap, thanks.

2024-10-04 22:38:11

- reply

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.

2024-10-03 13:22:14

- reply

Thanks, will check it!

2024-10-02 21:31:59

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.
https://m.primal.net/LJBA.jpg

2024-10-02 19:36:18

- reply

v4 format is now default in new Minibits release.
To run your owm mint, check cashubtc/nutshell om github.

2024-10-02 19:35:13

- reply

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.

2024-10-02 18:10:51

- reply

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.

2024-09-30 15:53:36

- reply

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.

2024-09-30 15:44:35

- reply

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

2024-09-24 17:57:24

Excited to announce that Minibits has become one of the @nprofile…uazd grantees 🎉! Grateful and dedicated to push forward with open-source ecash R&D for #Bitcoin!
https://image.nostr.build/4ced6dcfb4dda7861182250bb57fa655ea49f8752be988320c33c6589157f2d2.jpg

2024-09-22 18:30:35

- reply

Ok will change it in the next release.

2024-09-19 18:45:54

- reply

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

2024-09-18 17:03:48

- reply

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.

2024-09-18 16:59:12

- reply

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.

2024-09-15 21:38:05

- reply

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.

2024-09-09 18:31:08

- reply

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

2024-09-04 21:12:48

- reply

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.

2024-09-01 19:39:25

- reply

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.

2024-09-01 14:43:19

- reply

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

2024-08-27 06:57:42

- reply

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).

2024-08-26 22:28:10

- reply

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.

2024-08-26 20:57:13

- reply

If you see them only when wallet is in active use, those are local ones, trigerred by the app itself. Check if you see the device token under the push notification switch in the Settings.
https://image.nostr.build/3fb0945edb7e0a37a1950150df6b4962e96f5650e9f2097f0e1951cbd0d765d1.jpg
For NWC to work when Minibits is killed or backgrounded, you'd need to be able to recieve them from the server, through firebase messaging - the same way push are delivered on incoming zaps no matter the state Minibits is in.
Most android devices are supported, but there are some that don't: i.e. if you use a device that has no Google Play services installed (some chinese brands or privacy operating systems such as Graphene and similar). Those can not obtain the so called device token to which the messages are addressed.

2024-08-26 10:00:08

- reply

Do you have push notifications enabled and working?

2024-08-26 09:07:22

- reply

When Minibits is in killed state, in my tests the zap is paid reliably by ecash, however android suppresses or delays the nwc response sending - but not sure how Amethyst or others handle this case.
Still, zap receipt is published from the server, so not missing.

2024-08-26 08:53:48

- reply

Go to Settings > Wallet on primal, deactivate default wallet and add NWC connection string from #Minibits

2024-08-26 06:41:38

- reply

That's the recovery last step.
As well, if you still has old device with balance and just moving, you can just install on new device, send balance to new random address and the use "wallet address recovery" on new device using your seed.
That way you skip sometimes painful ecash recovery and move your address.
If that's not working for you, drop me a dm with screenshot of app details from developer settings.

2024-08-26 06:36:16

- reply

Certainly doable. In more generic way, could I put it that you'd like not to be bothered by notifications when app is in foreground /active?

2024-08-23 06:12:23

- reply

Agree, contacts are quite barebones. Could you please give an example what lists you mean?

2024-08-22 12:52:13

- reply

Requires to have push notifications enabled and working as they work as a data carrier to pass encrypted NWC requests to the device when wallet app is in the background or off.
Experimental, background processing is limited by Android OS, depends on many things such as battery level, there is no guarantee it will work on every device.
Use only with apps you trust and with small daily limits!
https://m.primal.net/KHwU.mp4

2024-08-22 12:47:49

https://m.primal.net/KHwG.jpg
I hesitated to add NWC to @npub1kva…tkzv for so long, deeming it bad choice for mobile devices… until I could not hear 'wen nwc🧐?' anymore.
Now, in reckless mode, you can connect to Minibits from your favorite #nostr apps and make payments, even when the wallet is asleep😴.

2024-08-22 07:32:28

- reply

That was meant as a silent launch :) Please use with caution, it is an early implementation meant for testing. Still a lot to polish

2024-08-13 05:29:56

- reply

I test on 4 years old Samsung A20 to check UI on low res displays. What's wrong on A15?

2024-08-12 20:40:17

- reply

Hi sorry for delay, been offline for few days.
If you still have the previous device I would not go through ecash recovery at all.
1. Install on new device, add mints
2. Move your balances by sending ecash to your random wallet address on new device (it might be too much data for qr code)
3. Go to Backup and recovery, enter your seed from the old phone to Recover wallet address
4. Uninstall Minibits from old device
That should do the trick with min pain.

2024-08-12 20:31:57

- reply

Checked the whole stack and seems working. Is the issue still a thing?

2024-08-12 20:30:29

- reply

What's your new phone?

2024-08-04 07:46:29

- reply

Thanks for trying!
New format requires that the mint uses new format of keysets as well (hex encoded). Minibits mint has mit yet migrated to new keysets.
In the meantime you can try e.g. stablenut.umint.cash
Here is 21sat token in new format, switch is below the QR code.
https://image.nostr.build/b4d1a3f8c58dce5eb0ea0fa44f24c9515e10f9761e96dd8ebc88a049b380bea4.jpg

2024-08-03 22:51:19

- reply

To receive ecash for your tons of zaps in a batch, turn on the setting on your wallet address screen. Wallet will then receive zaps as a batch if there are more then 5 pending to be claimed.

2024-08-03 12:01:17

- reply

Sorry to hear that no matter what amount. If you reinstalled we don't have much to investigate.
Hope Minibits will work for you, drop me a dm or ask in Minibits wallet tg group if you'd need help in the future.

2024-08-03 07:33:04

- reply

Re: receiving zaps in #Minibits. Wallet receives encrypted and encoded cashu tokens generated on the server once ln payment comes.
Wallet creates draft transaction and then calls mint to swap ecash for fresh. Received ecash is stored into wallet state and backed up in separate daatabase.
Then transaction completes.

2024-07-31 18:19:19

- reply

I've checked the mint, there are quite a lot of pending notes.
I've checked one on lightning node directly and related payment is still in flight.
So it's upon receiving node to fail or complete the lightning payment.
If you pass me melt_quote id, I can check precisely yours.

2024-07-24 22:29:41

- reply

Did you keep Minibits open while paying the invoice? It should detect the payment while in foreground.
You can retry and if the name is still free it should allow you to book again.
I'll check tommorow the server and if you'd donate twice I'll send you sats back. Gb

2024-07-22 22:29:14

- reply

Thanks for pinging me!

2024-07-15 21:14:56

- reply

#Minibits wallet holds the ecash on device, not on the server. So to work with NWC reliably, app would need to be in foreground.
Some workarounds could be designed. Does the deeplink bring too much friction?

2024-07-10 20:05:33

- reply

Sorry for trouble. Go to Settings > Backup and recovery, copy your seed phrase and go through wallet address recovery. It will solve the issue.

2024-07-10 20:04:01

- reply

Sorry for trouble. Go to Settings > Backup and recovery, copy your seed phrase and go through wallet address recovery. It will solve the issue.

2024-07-09 13:19:07

- reply

Hi, go to Backup and recovery, copy your seed phrase and go through wallet address recovery. This will sync necessary data for claiming zaps and other sats sent to your lightning address.

2024-06-30 14:30:52

- reply

Hi can you DM me the copied audit trail from errored tx detail screen? I'll look at the reason while after the ecash has been received by the wallet the subsequent swap for fresh ecash with the mint failed.

2024-06-28 13:28:34

#Minibits update packs a lot of smaller improvements + tor support is back! (with small hack)
New over the air update brings a bundle of fixes and UI polishing.
Subtle yet useful new feature is the ability to send comment alongside the payment to lightning address.
Minibits now supports mint URL change in case the mint would lose the domain. Just in case.
In previous version, Minibits had to sunset integrated Tor daemon to connect to the mints on .onion addresses.
Now, we are back and Minibits can connect to .onion mints again using VPN mode with Orbot!
https://image.nostr.build/cd2eff755da992dc7a2baba893df9a982262bb3ad160c29ba7a70cad5b09c1c6.jpg

2024-06-23 21:31:35

- reply

Easiest way to move ecash to another wallet is just send it there, no need to run the recovery from seed.
Another than Minibits wallet won't be able to receive funds sent to minibits.cash lightning address - seed recovery there regenerates ecash only with help of the mint.

2024-06-16 13:46:51

- reply

Zapped you just now. Try app restart and dm me any error you'd see. I'll check in the evening if there is some unclaimed to your address.

2024-06-15 16:30:29

- reply

Ah I see the pic up the thread. That's it. Please go to Backup and Recovery, copy seed phrase and run through Wallet address recovery. It will sync missing profile authentication params necessary for claim to pass and solve it - restart after to force claim.

2024-06-11 10:10:19

- reply

Sent you test zap. Please post which version you are running from dev options screen. Will check on server and re-publish any not yet claimed if any later when at the pc

2024-06-11 10:09:21

- reply

Sent you test zap. Please post which version you are running from dev options screen. Will check on server and re-publish any not yet claimed if any later when at the pc

2024-06-10 11:32:35

- reply

Means you are trying to access non existent mint. Legend lnbits team disabled cashu mints on their server some time ago.

2024-06-10 11:30:34

- reply

Send it.

2024-06-07 15:11:15

- reply

Hi Minibits dev here. Do you see transaction with error status in the wallet? If so, dm me copy of audit trail from the detail screen.

2024-06-04 08:30:58

- reply

Submitted as #78 to our github.

2024-06-03 12:51:41

- reply

That means your device is triggering local notifications on ecash coming still over nostr relays.
Make sure you run latest native release and over the air update (0.1.8-beta.20) and notifications are enabled in Settings.
As well check if your device supports delivery of notifications over firebase (requires google play services installed)

2024-05-31 22:14:24

- reply

Please get the native release hotfix released yesterday + over the air update.
There is a fix that makes sure your push token syncs and messages start to fly. You should be on 0.1.8-beta.20

2024-05-29 11:05:10

- reply

Sent some more! Check if notifications are enabled in Settings and if you see them coming!

2024-05-29 10:49:37

- reply

Thank you for your zaps coming! No better way to test that push notifications work!

2024-05-29 09:56:41

- reply

Please note, that notifications are disabled by default for new installs, enable them in Settings.

2024-05-29 09:52:11

Did not take long to have a new #Minibits wallet release out 🚀!
New, much faster and reliable receiving of zaps and other #lightning payments, now with real time and encrypted push notifications 💌.
https://m.primal.net/IRMW.jpg

2024-05-29 09:51:24

Content creators work hard to earn zaps. How should perfect receive into Ecash wallet work?
New #Minibits architecture for receiving zaps and all #lightning payments to minibits.cash addresses.
Realtime encrypted notifications, claim ⚡sats on wallet start 🚀
https://m.primal.net/IRMY.png

2024-05-26 22:28:27

- reply

Hi back online now. Annoying update modal is fixed, it was a bug related to the prep of new release.
Please dm me a copy (not screenshot) of the audit trail of the expired transaction, as it involves minibits mint, should be easy to investigate an solve.

2024-05-21 17:19:49

- reply

Did it, you have the steps to be taken in there.

2024-05-19 18:41:02

- reply

Wrote you a dm, we'll sort it out.

2024-05-16 18:49:07

Unfortunately there are cases where migration to new wallet version bricks it. As it uses to be, never happened in tests and there are subtle differencies on how bad it is.
As such, my fixes focus more on improving recovery steps.
If that's your case, there is general procedure in a related github issue. If that won't help, drop me a dm or visit tg support group. We can sort it out.
If you have not upgrade yet, check release notes on github to be on the safe side.
#nevent1q…q49p

2024-05-15 19:25:13

- reply

Hi, I'll check the profile name on the server and dm you steps how to get it back.

2024-05-15 14:25:00

- reply

You need to add a mint that issues USD ecash. Minibits mint does not.

2024-05-15 14:00:47

- reply

Does any of available options (proofs, tokens, reocvery) work for you?

2024-05-15 12:52:01

- reply

This looks really bad, sorry for troubles.
Please get todays update and add your mints again and head to Backup > Local recovery tool. If you have local backup, tap Recover to wallet.

2024-05-15 12:49:22

- reply

Try to restart the wallet, does not look like a mint issue.

2024-05-14 23:00:05

- reply

If you turn on wallet storage encryption in Security settings, biometric auth will be required to start

2024-05-14 14:06:57

- reply

In Cashu transaction between mints always includes Lightning.
Of course two-step process (creating an invoice on one mint and paying it from another) can be streamlined by the UX, some wallets do that.
When other than sats mint take off, I'll add it as well so there it good ux for "exchange" transaction.

2024-05-14 13:00:59

- reply

Yes, wallet supports multiple mints. Jus go to Settings > Manage mints to add some or scan mint URL encoded as QR code from main screen.

2024-05-14 12:47:47

- reply

Your Lightning address is now one tap away from Wallet screen. Transactions moved to their own bottom tab.
https://m.primal.net/IGeN.png

2024-05-14 12:35:17

Mints could issue almost anything desirable as Ecash.
And Minibits Wallet is ready to handle it.
Biggest upgrade so far with currency units support and related major UX and navigation revamp is now out!
https://m.primal.net/IGeD.png

2024-05-08 10:31:51

https://image.nostr.build/77555350eb1dc7a64c8ecb0d40b4599e3cab6971dbb55e90f5643e5cb0632989.jpg
Multiple currency units issued by mints are coming! Now released to alpha testers over closed testing program on Google Play.
Dear Alpha team, please read the release notes carefully before upgrading.