Minibits

https://minibits.cash

Public Key

npub1kvaln6tm0re4d99q9e4ma788wpvnw0jzkz595cljtfgwhldd75xsj9tkzv

NIP-05 Address

dev@minibits.cash

NIP-57 Address

minibits@minibits.cash

Profile Code

nprofile1qqstxwlea9ah3u6kjjszu6a7lrnhqkfh8eptp2z6v0e9558tlkkl2rgpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5qy2hwumn8ghj7etyv4hzumn0wd68ytnvv9hxgmqa992

Publishing to

nostr-pub.wellorder.net

eden.nostr.land

nos.lol

Author Public Key

npub1kvaln6tm0re4d99q9e4ma788wpvnw0jzkz595cljtfgwhldd75xsj9tkzv

Show more details

Last Notes

2025-03-28 16:02:59

- reply

If the invoice has been paid it can be claimed in Minibits even if expired.

2025-03-25 20:19:41

- reply

As the receive transactions (which are in effect swaps of incoming tokens for fresh ecash) failed, you can copy those from tx detail screen ("input token").
After setting up new wallet, just paste them to recieve.

2025-03-25 20:17:05

- reply

Will look at it, thanks

2025-03-24 20:50:24

- reply

Issue happens when for some reason background processing is interrupted (e.g. by OS or due to network glitch), mostly over longer running nwc commands.
In such case already spent ecash might not get cleaned from spendable balance.

2025-03-24 20:35:45

- reply

Settings > Recovery > Remove spent ecash

2025-03-23 08:23:50

- reply

Hi that should not have happened, mint is operational and it can't make selective balance dissapear. Very likely a wallet state issue.
Do not let it be, use your seed phrase to recover the balance - at least you'll learn how to do that and hopefully will feel safer with ecash afterwards.

2025-03-21 19:46:27

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 20:26:02

- reply

You're connected to your minibits wallet from zeus over NWC or else? Invoice was likely settled by minibits mint so I think so.

2025-03-19 18:04:23

- reply

Paid

2025-03-19 07:43:42

- reply

Settings > Recovery > Remove spent ecash

2025-03-16 19:50:37

- reply

I understand you are recovering your balance from seed (with mint assistance). Ecash is recoverable that way thanks to sequencer, and wallet needs to try from beginning as nobody knows which indexes belongs to not yet spent balance.
So mint returns re-created ecash and wallet then tests which of tokens are unspent. With longer wallet history unspent ecash is further away.
There is than wallet backup feature that works differently - you can export exact state of your mints and ecash - easier e.g. when moving to new device, because you do not need to play hide and seek with the mint.

2025-03-15 19:52:53

- reply

https://github.com/minibits-cash/minibits_wallet/tree/main/src/i18n_messages
You can fork the repo, and submit pull request adding jp.json derived from en.json.
I'll test then the UI so that you do not need to setup the whole dev environment.
Thank you for any contribution!

2025-03-15 12:45:07

- reply

Sounds great. Not much of a team here, just me and few time to time contributors. Would be glad for any help. App source code provides translation files with most texts, if you are familiar with Git, it's easy to make a pull request.
If not, I can prepare the file, may be auto-translated to review and finalize. I expect the most tricky part might be to fit the sizes and lenghts of the translated terms in those part of app where they matter to not break the UI - we'll see once deployed.
Currently app loads automatically the translation matching the device locale, if such exists.

2025-03-15 10:16:00

- reply

There was a minibits relay issue at the time, now fixed.

2025-03-15 10:14:55

- reply

Would it make sense to make a japanese wallet translation or something else?

2025-03-15 10:12:01

- reply

They work for sending ecash over nostr. For NWC, spec allows to specify more relays in the connection, but client generally did not support that at the time. So I had to switch to a single relay, agree not optimal.

2025-03-15 10:07:52

- reply

Slightly longer processing of Minibits NWC is as well due to the need to transport incoming nwc command over the (double) encrypted push notification and process the payment directly on device where the ecash lives.

2025-03-15 10:04:22

- reply

Sorry to hear that. Most errors are logged in transactions audit trail and are recoverable or can be fixed fast. If you mind share such log through the dm, happy to check those.

2025-03-15 10:01:00

- reply

To start, put your minibits address to your nostr profile so that I can zap you!

2025-03-13 21:09:50

- reply

That's yet something else then. Please pass me the tran audit trail ftom thrm detail screen over the dm.

2025-03-13 08:52:59

- reply

Zaps retested successfully, should be ok now.

2025-03-07 20:47:02

- reply

Check please if you see non zero number of proofs in Settings > Backup > Wallet backup. Seems like wallet lost the state, however proofs might still be in the database (separate storage)
In worst case, use your seed to recover the balance.

2025-02-21 19:35:30

- reply

I would need to see what happened, hard to tell. Will DM you the next steps so we do not spam public with debugging.

2025-02-20 21:16:04

- reply

Got them all. Not happy about your troubles, cause due to few similar reports, v0.2.0 includes some network tweaks that were intended to solve it (ipv4 preference for dns lookups).
As well the fact that you're not offered an update to the latest resembles to https calls failing (potentially only when fired early after app starts). Will check for crash logs if any tommorow.

2025-02-20 20:41:39

- reply

Got single 5 sats zap. As you mentioned freezing, from some reports it seems to be network related.
You might prove it by disconnecting the device from all networks and restart the app while offline - any freezing should stop.
Then get back online again. As well check the version you're running, should be 0.2.0-beta.9

2025-02-20 16:02:27

- reply

Are your push notifications enabled and working otherwise? If you send to your minibits lightning address with wallet killed, do you get notified?

2025-02-20 08:16:28

- reply

You mean when using over NWC from Amethyst? How does it manifest?

2025-02-19 07:26:44

- reply

So far not sure it's a good idea. Wallets have often above 1k proofs so I'd be cautious about the limits / reliability when used at scale.
But it might work as a quite neat wallet backup option I'll think of that.

2025-02-18 20:53:22

- reply

BTW current lightning address on your profile is not reachable for zaps.

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-18 08:23:55

- reply

Checked the code. There might be a rare case when previous install failed, that retry is allowed after some time. So please restart and try to update again.

2025-02-17 22:02:11

- reply

Sounds bad. There are no accounts with ecash, it is stored directly on device. Lightning addresses work thank to a server but it does not hold users' ecash balances.
To recover you need the seed, that allows the wallet to re-generate lost ecash with mint assistance, or a wallet backup.

2025-02-17 20:04:08

- reply

Minibits uses push notifications for NWC to work when app is backgrouned or killed.
But there is websocket fallback in case notifications are disabled. Still with minibits relay but should be faster.
However, android tends to kill network connections if app goes to background so not sure it's suitable when both nostr client app and Minibits are on the same device.

2025-02-17 19:54:49

- reply

Great work and makes a lot of sense. How about prototype it in Minibits?

2025-02-17 19:32:55

- reply

NWC relay must be accessible for both parties, so local on device relay would not work as a part of NWC connecton string.

2025-02-17 19:09:37

- reply

Thanks for report. I'll check what might be the reason because I see majority of active devices already on beta.9 in lightning address server logs.

2025-02-16 14:06:10

- reply

Nostr client <-> Relay <-> Minibits server <-> FCM <-> Device <-> Mint, Relay

2025-02-16 00:07:43

- reply

Until the ligthning address server is alive and the data not lost - it is operated on best effort basis as a part of ecash R&D.
As well, the mint must keep the support for keysets used for generating of ecash and not rotate to new ones.
There are push notifications available to be notified about incoming lightning address payments.

2025-02-15 23:58:46

- reply

Ecash is not an account-based concept. It's similar to physical cash. Once you give a dime to your kid, you can't control it anymore.
Wallet holds the ecash notes in its own on-device storage (or should do to get any of ecash advantages).

2025-02-15 22:00:06

- reply

In my experience Primal highlights the zap icon immediately and later adjusts it based on the result.
You should see Minibits push notification showing the result of the nwc payment in few seconds. If not, make sure notifications are enabled and working on your device (google play services are needed if you use graphene os)

2025-02-14 21:58:00

- reply

This is the seed phrase wordlist used in Minibits, check against it if your words have a match:
https://github.com/paulmillr/scure-bip39/blob/main/src/wordlists/english.ts

2025-02-14 15:25:54

- reply

No commas, single spaces, just paste as you've copied. I now tried to retype manually on android device to make sure that spaces between words are the same unicode that the device keyboard enters and it works.

2025-02-14 07:34:30

- reply

If you moved your balance elsewhere before deleting, go to Settings > Recovery > Wallet address to get your address back. You need to backup the new wallet seed then.
If you had some ecash in, go to seed recovery from last onboarding screen ("Recover lost wallet")

2025-02-13 22:42:17

- reply

Received zaps are converted to ecash on lightning address server, your wallet can be offline when they come.
Push notification is sent immediately, but ecash is claimed once you open the wallet.
For sending zaps over NWC from #Minibits you need push notifications working and device online. App can be closed, will process NWC payment in the background.
Just play with it with few sats.

2025-02-13 18:16:17

- reply

I've published 0.2.0-beta.8 as a new native package to github and google play (pending approval there).
Not sure why that happened but hope this will fix it.

2025-02-13 13:12:00

- reply

Which version is it?

2025-02-10 16:52:01

- reply

#nevent1q…gyh9

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-06 22:02:23

- reply

Tap the transaction with error and press copy Audit trail at the bottom of the detail screen.

2025-02-06 18:46:23

- reply

DM me the audit trail of such error receive transaction please. Thanks!

2025-02-05 17:35:17

- reply

True. Minibits mint honors 1M sats limits for minting / melting ecash. However it is still R&D project and I recommend to keep you funds limited to petty cash amounts.

2025-02-05 15:44:15

- reply

What would be your usecase for multiple wallets?

2025-02-04 06:19:34

- reply

Sure, welcome! It's a react native app.
https://github.com/minibits-cash/minibits_wallet

2025-02-03 23:00:25

- reply

Have fun! If you'd plan to use Nostr wallet connect, make sure that push notifications are enabled and working in Settings.

2025-02-03 19:38:30

- reply

Sure, tap profile icon then choose change. You can choose your own for small donation or select from random ones at will.

2025-02-03 16:23:18

- reply

On new install / after factory reset go into Recover lost wallet from last onboarding screen. Choose Import backup option.

2025-02-03 15:03:00

- reply

Did it work for you?

2025-02-02 23:13:48

- reply

So make a wallet backup as well bedore trying. That way yiu can avoid often lenghty recovery of ecash from seed only (which requires to go through whole wallet history with the mint)

2025-02-01 00:50:53

- reply

If you made full reinstall and then the recovery, you've got the version released with the last native package, so it's ok when app offers over the air update to the latest.

2025-01-31 15:59:59

- reply

I love cashu.me as well, just have used it on desktop so far.

2025-01-31 15:57:44

- reply

Yes I fixed the retry so that it clears the spent ecash within the notes reserved for transaction.
Actually the fact that those lots are usually small enough it allows you to clean it over time without hitting the performance bottleneck when trying it from recovery.
Definitely not ideal, but if you have longer wallet history, still might be less time consuming then full recovery.
Happy you are on track to fix the issue.
Regarding the unfortunate perf issue, if you don't mind dm or reply with what android device are you using.

2025-01-31 14:03:06

- reply

To be precise, Minibits holds ecash from cashu mints. However, bitcoin reserves backing the ecash are held by mints' lightning nodes custodially. You trust your mints until you redeem your sats over lightning.

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-30 12:44:39

- reply

Fixed the sending of more zaps over the short period of time in the latest over the air update!

2025-01-30 12:42:31

- reply

Have been working on that. It's tricky due to the way android handles long running background tasks, but latest over the air update should handle multiple zaps sent over short time more nicely!

2025-01-30 12:39:25

- reply

Hm that sounds really bad. Cleaning runs in batches, can take some time, but should not crash.
Could you check how many proofs does your wallet hold as shown in Settings > Backup > Export backup screen?

2025-01-28 21:42:24

- reply

Go to Settings > Recovery > Remove spent ecash

2025-01-28 21:36:44

- reply

You should have the steps to recover in your DMs. Maybe we have some relays mismatch?

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-28 16:30:38

- reply

See DM, thanks!

2025-01-28 05:55:31

- reply

Some os allow to run play services in separate jail / compartment, but not sure about privacy implications.
To at least try nwc on minibits, there is a fallback websocket connection, that should receive nwc commands while app is foregrounded. Could be used to "taste" nwc with connection added to nostr client on another device (not much tested)

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:53:43

- reply

I've checked it. Your minibits lightning address returned error because you had dozens of unpaid not yet expired invoices (likely never paid zaps) and they hit the limit set as a dos attack precaution.
I've increased the limit few times up, so should not be an issue anymore.

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-03 09:22:55

- reply

DM me your sentry id, I'll check.

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