Minibits

Please dm me your former address and the newly generated address on new device.
Something went wrong when recovering the address, we'll sort it out.
Thanks for reporting.

2025-05-25 11:41:02

- reply

Reason for some latency compared to server-side custodial wallets is that if you want to zap using NWC (not deeplink), incoming NWC command must be routed to the device push message, wake it up in the background and process ecash payment - because ecash lives directly on device. After some optimization this is now faster then it used to be.

2025-05-21 22:22:00

- reply

On graphene, google play services needs to be installed for push messages to be delivered. Happy for you made it work!

2025-05-21 21:27:23

- reply

Do you have push notifications enabled and working? They are necessary for sending zaps over nwc to work.

2025-05-18 10:43:46

- reply

No reason to conclude you've lost funds. You can always recover unspent ecash using your seed phrase.
Displayed error is usually resolved through the recovery option I've gave to you.
It might require to press more times in case your wallet went through incomplete recovery before

2025-05-17 19:57:27

- reply

Sorry for the delay. Go to Settings > Recovery and press Increase recovery indexes. Then go to the failed transaction detail and you should be able to retry to complete it.

2025-05-13 10:54:49

- reply

I hear you. Will look at it once I finish the work on iOS release.

2025-05-11 19:21:18

- reply

Zaps are received by minibits lightning node and converted to ecash on lnurl server, where your address is reachable. Push notification is sent immediately, but ecash is claimed by the wallet once wallet becomes active. Try to restart whem in doubt.

2025-05-08 21:13:18

- reply

This message is returned by mint in case the previous lightning payment did not completed neither failed before. The reserved ecash to settle it will remain pending until inflight lightning payment finally clears, usually within 24 hours.

2025-05-06 19:23:15

- reply

Did you receive my dm with the instructions sent? Please check.

2025-05-04 19:27:07

- reply

Check back the answer. Thanks for reporting!

2025-05-03 14:12:23

- reply

https://njump.me/nevent1qqszk9cq6el58py88s7vnyt2adhal2dw70g87fv4cfyazzreu4xa4mcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtczyzenh70f0du0x4555qhxh0hcuac9jde7g2c2sknr7fd9p6la4h6s6qcyqqqqqqg4sslcj

2025-04-29 20:35:49

- reply

Thank's for report, that might be a bug. Will look at it. You can still make a fresh install to get back to minibits wallet address.

2025-04-29 20:32:46

- reply

Thank you! Still, please trust up to some sensible amount of sats, love indefinitely.

2025-04-28 12:13:14

- reply

Random one is created when initiating new wallet, automatically. You mean you are unable to change it to another random one?
If so, please tell me if you see any error shown. Thanks!

2025-04-27 18:03:48

- reply

Ok let's sort it out over TG, sorry for the issue

2025-04-27 18:02:05

- reply

That's a lot, Minibits has definitely not be tested with that number. Please report your findings!

2025-04-27 05:14:14

- reply

Ecash in Minibits lives on device and in order to make recovery possible, it is generated using sequencer and seed that are device-based as well.
So you can't use the same seed with another device as you'd with classic custodial architecture.
Minibits nostr/lightning addresses are linked to the seed as well so that they can be moved to new device as a part of recovery process.

2025-04-25 09:32:04

- reply

I see what you mean. How did you make it published and shown (I see it as empty note in Amethyst; do not remind to see that before)

2025-04-24 22:20:43

- reply

Vouchers with printed ecash tokens locked to an ice cream maker public key .

2025-04-24 21:16:32

- reply

We'll see but OTA updates are quite common in react native apps. May be they enforce for changing native code only.

2025-04-24 20:57:37

- reply

It's settled by the mint immediately, no lightning involved.

2025-04-24 11:49:16

Minibits is an ecash and Lightning wallet exploring how ₿-backed ecash can enable instant, cheap, and private value transfer.
Now, nearly 2 years since the first line of code, Minibits is expanding to iOS! Join the TestFlight:
https://testflight.apple.com/join/defJQgTD
https://m.primal.net/Qbby.png

2025-04-23 15:20:32

- reply

Should be fixed now!

2025-04-20 13:25:06

- reply

Not yet full nip61, but this feature is one of the building blocks.

2025-04-20 07:49:54

- reply

It can be a npub or public key in hex format.

2025-04-19 12:03:52

- reply

Here's the new feature on planned iOS release, still in the making.
https://image.nostr.build/6d61936fdcb96f9f795878a66e6363b2c53f48d02d1d6536830ab717e580ae9f.jpg

2025-04-19 12:02:49

Minibits now 🔒 locks your ecash to your intended recipient, so nobody can steal it on the way. Locks can expire, letting you recover a mistaken lock after some time. Lock the new release to yourself now!
https://image.nostr.build/f4e87061d7f0db132a42761fc9ef215f8cafec94d9785f5948da3d8333d86779.jpg

2025-03-29 22:29:01

- reply

Pass me one of errored transactions audit trail. Usually simple to fix.

2025-03-28 22:14:21

- reply

If mint says it's still unpaid even that sender paid the invoice, then please pass the invoice to the mint operator - he can check it directly on mint's lightning node.

2025-03-28 22:09:00

- reply

Very likely a bug, thanks for reporting.

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-25 06:47:52

- reply

Ah I see. When you recovered before a wallet with long history using your seed, you might have not come through up to the end of hostory - you still generated already "used" sequencers when making new transactions.
Would recommend to clean install, go into wallet (not recovery) and then use your seed to get back wallet address only. Then, backup your new seed that comes with new install.

2025-03-24 21:54:35

- reply

@nprofile…xnfk

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-24 17:36:41

- reply

Settings > Recovery > Increase recovery indexes

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 22:58:27

- reply

Could the zap split be sent over NWC as a multi_pay_invoice command, combining invoices to be paid into a single command?

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-15 09:59:08

- reply

Just an ecash and lightning wallet.

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-11 13:51:56

- reply

Please DM me if you did some operation that might have caused the wallet keys to rotate (move wallet from another device, recover address or balance using the seed etc).
Make sure to not use same profile / seed on more then one device.
To fix this I'd suggest to move balance into another ecash or lightning wallet and then factory reset / reinstall.

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-03-07 20:44:02

- reply

How did it happen? Already the first screenshot does not feel right - having 400k balance without any transaction.

2025-03-04 15:15:46

- reply

Do you have push notifications enabled and working on your device? Necessary for Minibits NWC to work.

2025-02-24 19:29:11

- reply

DM me the copied audit trail of the transaction from the detail screen. It's not clear where the error comes from whithout those details.

2025-02-23 16:19:09

- reply

Not as a public social identity. Nostr private key is never exposed by tye wallet.
It is meant to be your payment identifier: combined lightning address and a nostr address with a sole function - receiving and sending ecash over nostr encrypted messages as a more straightforward alternative to lightning.
I believe those two identites are betrer to be separated for security, privacy and flexibility reasons.
Ofc you can send ecash to any nip05 address, just than the receiver needs to paste it to the wallet on his own.

2025-02-22 20:28:24

- reply

Thank you! There is a lot of not-coding stuff missing. Will think of that during upcoming holidays and will come back to you!

2025-02-22 18:25:16

Thank you! And much of that goes to @nprofile…xnfk, the cashu protocol maker!
#nevent1q…wadc

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-21 13:44:43

- reply

There are folks that are running it that way. Minibits allows to enter unencrypted http relay url for that reason. In any case make sure that it is synced with relay.minibits.cash or that it is still in the list - nwc relies on that one.

2025-02-20 21:31:30

- reply

Minibits ecash wallet usage rose about 10 fold when this was implemented on Minibits LNURL server a year ago for zaps and for payments to minibits .cash lightning addressed (ofc not NIP-60).

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 20:46:28

- reply

No, lightning address is not a part of the ecash mint spec.

2025-02-18 17:05:25

- reply

Please set your wallet/lightning address on your public nostr profile so that I can zap you!

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 18:19:21

- reply

Minibits is an ecash and lightning wallet for Android.
https://github.com/minibits-cash/minibits_wallet

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