Minibits

Left: Battle-hardened gear that has carried Minibits through many fights.
Right: Shiny new tooling for the iOS frontline.
Can't promise the deadline, but Minibits on iPhone is slowly heating up.
https://image.nostr.build/826fa5987e79171d8f1255a7a337998c3a213f4cc8f8d543da377aacf47a2c4c.jpg

2025-03-19 07:43:42

- reply

Settings > Recovery > Remove spent ecash

2025-02-18 20:51:21

- reply

The url is /Bitcoin (not great idea, but here we are, plan to change it to all lowercase /btc-sat or so).
Did not tested what conflicts that might bring so I'd recommend to start fresh, Minibits mint with correct URL is added by default on firat start.

2025-02-10 16:31:09

- reply

Not sure that is possible, Minibits mint has max mint and melt balance 1mio sats and there are some 20 channels with min 10mio sats each.
Issue could be on wallet side / network related. Try to turn off all network connections and restart wallet, then turn them on again amd restart again.
As well, there is a new native version 0.2.0 where I hope to resolve some reported network issues that seem to be related to ipv4/ipv6 bugs in react native on android - I recommend to upgrade.

2025-02-10 16:14:01

- reply

Sorry for the headache. Not sure I'll resolve all nostr relays' mysteries but will add links to github and to minibits web.

2025-02-07 21:25:55

Almost like we can do both - stay connected, but keep our money private.
New @nprofile…mdf3 Nostr Wallet Connect from browser plays with @nprofile…dcd7 so nicely! https://m.primal.net/OVOU.mp4

2025-02-07 17:53:11

- reply

That sounds awful. I searched a lot around reported freezes / slowdowns, mostly mentioned by users from US. They are apparently network related - network calls to the mint neither fail nor succeed, hang for minutes causing such failures.
What I've found so far could be related to some ISPs not handling IPv6 networking in the way that android's native library / react native fetch expect.
I am now trying to make new build with some recommended changes, would love to discuss with somebody that dealt wity that already.
What I can do is to make you test build with changes available, dm me if you are interested (either as an apk or as an internal google play build depending on how you install).

2025-02-03 15:03:00

- reply

Did it work for you?

2025-01-30 22:17:48

- reply

Thanks, that's completely reasonable, should be done in two batches in few seconds. If you let it run, does it eventually complete and unfreezes or is that full crash?

2025-01-28 18:29:28

- reply

Sorry for troubles. If a notification about payment to lightning address / zap is delivered it means sats were received by the minibits lightning node and ecash for your wallet has been generated. It then waits on the server for the wallet to claim it.
There are unfortunately situations when wallet state gets out of order and claiming fails. There are now multiple fail safes now imolemented to resolve that on wallet side, in any case you're right it's critical to make this expereience flawless.

2025-01-24 17:15:27

- reply

Hi! Do you have push notifications enabled and can you see device token generated on Settings screen?

2025-01-17 17:00:39

New native Minibits release is out. This is mostly maintenance release, bundling all features, fixes and stability improvements that have been released in incremental over the air releases from december last year.
Makes sense to me to level the playground and to have a stable base to work on what's coming.
Sure there is something new and highly experimental:
Minibits is now the first ecash wallet that auto-recovers ecash lost due to mint responses not coming back to device via re-playing the requests and utilizing new Nutshell mint cached responses (works only with latest mints and with caching responses turned on, such as Minibits mint)
Step by step towards safer ecash!
https://image.nostr.build/1fe6571c01b86571860ca8bba2c639a9f675cf2fe02e6fcdc51694eb2ba20731.jpg

2025-01-11 09:54:06

- reply

Reserve is 1% min 1 sat I believe.

2025-01-10 20:57:02

- reply

Test zap on me!

2025-01-10 19:51:51

- reply

DM me the payment hash, I can check the exact route.

2025-01-10 14:50:18

First this year's over-the-air release is shipping!
@Minibits is now sending ecash using much more privacy preserving type of Nostr direct messages (NIP17).
@Minibits supports recent addition to Cashu protocol: you can now scan and pay Cashu Payment Requests (creating not yet ready)
And few fixes coming along as well. Enjoy 2025!
https://image.nostr.build/b4159b028dd332d8a0b3b7cf26346ae947e885a324ee6de3948efcea9ee8318d.jpg

2025-01-10 14:09:05

- reply

Check dm. You have created your profile before seed based recovery was even ideated :)
I can fix it for you as for the oldest minibits user still alive manually.

2025-01-10 14:07:20

- reply

To which lightning address? There are only lightning routing fees when zapping, so nothing I can control. No ecash melt/swap fees on Minibits.

2025-01-10 07:49:20

- reply

Ok, I'll check the state of the topup on the mint side and come back over the DM.
Please if you have, DM me the preimage (proof of payment) ftom the sending wallet.
Thanks!

2025-01-10 07:39:11

- reply

If you keep original seed phrase you'd book your address with, go to Settings > Recovery > Wallet address recovery.
This recovers wallet address only, without the balance.
From the last release, it keeps existing wallet seed (not rotating to the provide one, just getting the address back).

2025-01-07 19:49:35

- reply

Should not be the case

2025-01-06 15:23:58

- reply

App coming in foreground or visiring Wallet screen, once per 60s

2025-01-06 15:23:10

- reply

Please dm me the payment hash / invoice I'll check it on the mint side.

2025-01-04 16:03:15

- reply

Yes it is, but lightning address can't work then. Only pure ecash.

2025-01-04 16:01:28

- reply

I used to have 30 min expiry on minibits mint when used lnbits as a node middleware but now the mint is directly integrated to lnd with their 24h default.
Raised an issue to nutshell to enable to set custom expiry but not yet implemented afaik.
That's why I raised significantly the unpaid invoices dos limit per address yesterday.

2025-01-04 15:43:19

- reply

Please make sure which version you run in Setting > Developer screen.
You should be on 0.1.10 native version and beta.16 on the fly update. Should not make any popups.

2025-01-04 15:30:25

- reply

Minibits provides both nostr identity to which ecash can be sent over encrypted messages and a lightning address to receive payments or zaps.
Nostr address can not be used anywhere else because nsec key is never exposed and is solely used for decrypting incoming ecash.
Lightning address is meant to be added to your public nostr profile in order to receive zaps converted to ecash into your Minibits wallet.

2025-01-03 23:49:12

- reply

Zaps from Primal over nwc should now be fixed!

2025-01-03 23:23:51

Zaps from #Primal paid from #Minibits wallets over Nostr Wallet Connect should now be back in full force to roll through 2025!
They did not work for some time due to an unexpected format of NWC event tags sent from Primal app.
This has just been fixed on Minibits server which is listening for zap commands and routing them to the sender's wallet to be paid. Try them out!

2025-01-03 12:08:27

- reply

Ok see dm.

2025-01-03 09:28:49

- reply

Did you generated invoice in Primal wallet or did you send to minibits lightning address?

2025-01-03 09:27:08

- reply

What I can confirm is that Minibits NWC from Primal stopped working, works OK with Amethyst.
On travel now, so I have limited options to dig in, will do once back home.

2025-01-02 22:58:01

- reply

It's a random address generated on wallet first start. If you change your wallet address later, this stays the same and is used for crashes and errors monitoring (if kept enabled).

2025-01-02 13:21:41

- reply

Zapped yoy w/o issues

2025-01-02 09:46:06

- reply

What went wrong?

2025-01-02 08:45:03

- reply

Zapped you just fine from Minibits

2025-01-01 20:08:00

- reply

Received

2025-01-01 14:10:48

- reply

From latest beta.16 version, address only recovery from settings menu keeps existing wallet seed, so it's not necessary to keep the one used to recover.
Full ecash balance recovery (after fresh install) sets the wallet seed to the one used for recovery so that both recovered and future ecash is derived from a single seed.

2025-01-01 13:44:49

- reply

Thanks for reporting. Seems like the process succefully completes, will try to simulate it on my end.
Anyway, from wallet performance point of view, no need to optimize unless above around 1000 proofs or you need to export a smaller backup.

2025-01-01 13:39:34

- reply

If that's the case it may trigger dos protection on Minibits mint already when requesting invoiced and ban the source ip address for few hours.

2025-01-01 12:17:07

- reply

From Samsung device experience no need to tinker with battery settings and special permissions, just allow Push notifications in settings (disabled by default on new install).
But this varies per device type. To be sure NWC commads are received, one need to see the generated device token in Settings.

2025-01-01 12:09:42

- reply

I'd like to solve that asap. Latest is 0.1.10-beta.16.
There were freezes reported likely due to some android/okhttp ipv6 related issues, seems to be solved by reconfiguration on minibits server.
You might make copy of seed phrase and check how many ecash proofs your wallet holds in Settings > Backup > Export.
Then export as a backup or just send whole balance to another wallet (both do not require mint interaction) and factory reset.
Then import backup from last onboarding screen or just send back from another wallet. If you had custom wallet address, use original seed phrase in Settings > Recovery to get it back.
If above does not work for whatever reason, do factory reset and use seed phrase to do full ecash balance recovery, this can be longer process in case of long wallet history.

2025-01-01 11:53:32

- reply

From what I hear it would be great to have NWC setup accessible from menu / App settings, people can't figure out long press on zap icon to get there.

2025-01-01 11:48:34

- reply

To break down where the issue is, try to send few sats from Minibits directly to make sure wallet is operational.

2024-12-31 22:48:00

- reply

That's indeed a good idea. In some cases, when there are zaps to be claimed, wallet can't do that due to some error. That case can be handled better, it's not obvious.
In any case zaps should not be lost. If you've seen notifications, try to check if you see some error receive transactions. If so, dm me their audit trail from tx detail.

2024-12-31 22:43:03

- reply

Settings > Recovery > Recover wallet address.
Paste the seed phrase.

2024-12-30 21:23:57

- reply

Zapped the note from Amethyst with Minibits connected over NWC. Payment completed, seems that receiving node does not publish zap receipts, so zap did not show under the note.

2024-12-30 21:11:12

Yes, minibits wallet address works for both protocol. Nostr identity allows to deliver ecash to the wallet over nostr encrypted messages.
It is not assumed to become your public nostr address - private key is never exposed and can't be imported to any nostr client.
So normal usage is that you add your minibits address to your existing public nostr profile to be able to receive zaps or other payments.
When you send ecash to someone else with nostr address, you can skip lightning and send it as an ecash token - you can keep nostr profiles in contacts.

2024-12-30 21:03:31

- reply

https://github.com/minibits-cash/minibits_wallet/issues/129

2024-12-30 21:01:09

- reply

There is a preparation for that feature done in Settings > Backup but due to the backup data size limit to copy, transactions are not exported for now.
Would need a native app upgrade with more permissions so that the backup is not copied but stored to device storage.
I'll add it as a feature request to the github so we can track it but can not promise to deliver anytime soon.

2024-12-30 20:56:41

- reply

Inbound liquidity on minibits node should not be an issue, there's a lot. There is a max mint / melt limit set as you can see on mint info screen.

2024-12-30 07:50:51

- reply

Ecash is similar to paper bills and so is the role of a wallet. Only the wallet knows how much ecash is in, issuer (mint) has no idea where the ecash is kept, only how much was issued in total.

2024-12-29 23:34:29

- reply

To receive zaps into Minibits, set your lightning address on your public nostr profile to your minibits wallet address.

2024-12-29 19:41:45

- reply

IPv6 should now be configured on the minibits reverse proxy.
Thanks for heads up!

2024-12-29 19:23:39

- reply

Both errors are unhandled javascript errors (not returned by the mint)

2024-12-29 11:28:40

- reply

Do you remind how many ecash proofs did you have before running the optimization? It runs in batches.
Will monitor the issue, pretty sure that the freezing is caused by network connections over ipv6 to hang out but not failing.
Ipv6 is now properly configured on minibits reverse proxy server, so hope it'll be gone.

2024-12-28 21:59:17

- reply

I did some network related changes on Minibits server, you might retest if it helped. To get the proper result, please test with Minibits as the only mint (to avoid that the freeze remains due to similar issue on another mint server).

2024-12-28 20:01:08

- reply

I am aware of the issue, based on help with debugging from user experiemcing the issue seems to be network related issue - wallet freezes as a result of very slow but not failed network connections that resolve after 10-20s.
It's random nature, I could not simulate it unfortunately. I have a hypothesis it is caused by ipv6 connectivity issues.
Will try to reconfigure the reverse proxy tonight and see if it helps and does not break anything else.

2024-12-24 18:46:04

- reply

Check this maybe?
https://github.com/minibits-cash/minibits_wallet/issues/128

2024-12-24 09:03:10

- reply

Checked that. Error means there are more then 50 unpaid LNURL invoices to yuki@minibits.cash.
It's a kind of dos protection limit, however as minibits invoices now have much longer expiry, I might set it higher.

2024-12-23 22:40:44

- reply

Thank you; very appreciated. All the best!

2024-12-22 22:13:46

- reply

Did investigate some time ago. Seemed to have been possible on Android but the support was terminated.

2024-12-21 07:34:51

- reply

Sorry, what is the display size setting about? Do not have it on my samsung and would like to see if I can somehow adapt the dimensions to that. Simple screenshot of that setting options woild help. Thanks!

2024-12-21 07:24:58

- reply

Could you please try to test the setting of smaller android wide font size? If that resolves the issue I can be sure it is a screen dimensions related. Thanks!

2024-12-21 00:24:22

- reply

Small bugfix released just now, I've added some more margin to the button, please check if you can now see it.

2024-12-21 00:22:02

- reply

I now have another two folks with what looks like network issues connecting to the mint, while there are no bans on minibits firewall, so you might have a point.
Easy way to check is to write
ping mint.minibits.cash
to any command line.

2024-12-20 15:20:28

- reply

If you do not see view more below the list, could it be that the device has some unusual resolution?
Please send the device screen width x height ratio so I can try it on simulator.

2024-12-20 07:54:37

- reply

Ouch that's the first case I know about. Could not it be that your IP/ISP's shared IP got temporarily banned on Minibits firewall?
There are cases here and there where folks use Minibits mint as their development environment and do bad things to it, so firewall has rules in place to protect it.

2024-12-18 14:25:37

- reply

The message in Minibits is incorrect, it should be Mimimum payment amount ...
Will be fixed in the next release. Min/max amounts are defined by server hosting the lightning address (bancolibre in this case)

2024-12-18 14:16:58

- reply

If you zap another user using Minibits, zap does not touch lightning and is settled within the same mint, so without routing fee.
Over lightning, you gerally see some single sats fees for typical zap amounts.

2024-12-13 21:10:18

- reply

What would be the inspiration for a new one?

2024-12-13 21:03:01

- reply

Happy to hear, have fun and keep ecash balances low no matter the wallet / mint.

2024-12-13 18:37:04

- reply

Let's settle on #Minibits tag, so I do not miss.
Sats for sure not lost if you see receiving transactions. DM me the audit trail of one of those ended as error.

2024-12-13 10:55:59

- reply

Find follow up steps to recover the sats in reply, thanks for report.

2024-12-13 07:25:36

- reply

Good to hear. Reasonable point to stop is when you won't find any (spent or unspent) ecash in two to three intervals or when you are ok with the recovered balance + 1 round.
Exception would be only if you increased recovery index manually before - that might cause longer gaps.
For extremely long histories (thousands) there is and option to set starting index to avoid going through from 0, but there you should check their values from mint info screen before starting the recovery and set it to a reasonably loeer one.

2024-12-13 06:09:27

- reply

Sorry for troubles. Please send me the payment hash, I can check the lightning payment and that mint issued ecash on server side.
As well check the topup transaction detail screen and copy me the audit trail from the bottom of the screen. We'll sort it out.

2024-12-12 21:36:31

- reply

The modal should close on tap elsewhere or on pressing back button.
Could you try to change the internet connection from wifi to data or vice versa?

2024-12-12 21:28:45

- reply

Sorry never received those. I'll try to ping you over the DM now.

2024-12-12 21:27:32

- reply

Some possible crashes / freezes related to nwc commands processing not being terminated. That should be fixed in recent update, do not see them anymore in crash monitoring.
If hard restart won't help (normally should be enough) and you have your seed you can just make full reinstall and use the seed phrase to recover the balance. That way you skip the minor update you have issues with (you upgrade from native release directly to latest)

2024-12-12 21:09:40

- reply

Hi, this is the last message you did not respond to. May be you missed itvdue to some relay change?
There is no reason to lose 50k sats if you hold your seed.
https://image.nostr.build/88ae4f8bc50077b872a3e318a5460f15a2432e2f4a1e369cf05f504a4b145fbc.jpg

2024-12-12 19:43:00

- reply

Yes that's an added memo if none is provided by the payer. It might help to differentiate that the payer used lightning address to pay.

2024-12-12 08:42:26

- reply

Sent you a bailout in the hardest money.

2024-12-12 08:33:03

- reply

Don't you see small View more button below?

2024-12-11 13:23:40

- reply

If I'll be able to get some help, doable next year. Can not now promise the full feature set because of possible limitations on iOS.

2024-12-11 11:05:49

- reply

However still working to improve the reliability of what we have despite the quite extreme complexity.
Nwc zaps on minibits combine lightning, mint, wallet with on device held ecash, nostr relays and firebase data push messages to wake up the wallet on incoming nwc command.
It's a beast but when it works, experience is so goood.

2024-12-11 11:01:12

- reply

I believe future will be ecash zaps. Too much complexity with lightning for such small amounts, kinda like pushing micropayments over the SWIFT network. Zaps are now basically subsidized by lightning node operators.

2024-12-11 10:36:54

- reply

I've found potential cause. In case that a payment processed over NWC fails for whatever reason, I did not stop the android service for long lasting tasks.
This leads to Application not responding state.
Will release a fix 0.1.10-beta.8 now, let's see if it helps.

2024-12-09 16:04:30

- reply

It migh be gone if you do not have your seed. With seed, you can recover from any wallet failure while the mint is operational.
However in the above case we need to figure out what exactly hapoen on the wallet side to fix it for all.

2024-12-09 15:44:20

- reply

Did that happen within some transaction? If so please dm me the audit trail. Thanks!

2024-12-09 07:53:33

- reply

Please DM me related transaction audit trail and short description what happened, we'll sort it out I believe. Thanks

2024-12-08 20:14:14

- reply

If you mean the relay that is a part of nwc string then yes, it's only Minibits now.
Initial implementation supported more tgen one as per the spec, but encoding them into URI broke some nwc clients. After discussing with their devs I fall back to a single one.

2024-12-08 10:39:19

- reply

Thank you for reviewing Minibits. I think issues with nwc were mostly related to Android interrupting sometimes the background processing. As a result, further transactions often stopped working as well.
This should be improved with latest natove release 0.1.10-beta, where the implementation changed to proper support for long term background tasks.

2024-12-08 07:32:49

- reply

Sane approach. Appreciate.

2024-12-08 07:29:16

- reply

What use case did it fail you?

2024-12-08 06:47:55

- reply

Create #Minibits NWC connection in Settings, you might name it Amethyst, set daily limit and copy it.
Then long preess zap amount in Amethyst, everything to setup is on a screen you go.

2024-12-07 18:39:08

- reply

I feel ya. Lost 3 BTC many years ago due to my own stupidity as well.

2024-12-04 22:37:57

- reply

Depends on being able to engage some help, then sometimes next year could be on the table

2024-12-04 22:36:07

- reply

Check that recovery was done on the active keyset id - the one starting 005...
Alternatively try to use another web based wallet to recover - for some reasons it's faster: wallet.cashu.me or v2.nutstash.app.
Sats need to come back!

2024-12-04 13:25:55

- reply

You are right that a simple deeplink is still rock stable option how to zap.