MinibitsCash
Minibits

https://minibits.cash

Public Key

npub1kvaln6tm0re4d99q9e4ma788wpvnw0jzkz595cljtfgwhldd75xsj9tkzv

NIP-05 Address

[email protected]

NIP-57 Address

[email protected]

Profile Code

nprofile1qqstxwlea9ah3u6kjjszu6a7lrnhqkfh8eptp2z6v0e9558tlkkl2rgpz4mhxue69uhk2er9dchxummnw3ezumrpdejqzrthwden5te0dehhxtnvdakqf55krv

Publishing to

eden.nostr.land

nos.lol

nostr-pub.wellorder.net

Author Public Key

npub1kvaln6tm0re4d99q9e4ma788wpvnw0jzkz595cljtfgwhldd75xsj9tkzv

Show more details

Last Notes

2024-09-13 09:56:49

Urgent user call got me back to work!
#Minibits now displays profile pictures of zaps or ecash senders and 🔗links 🔗 to the zapped note from transaction detail.
https://m.primal.net/KoZB.jpg

2024-09-13 07:34:11

- reply

Good point. Was meant no to lose individual sender info when the number of incoming is not hindering perf.
However now it batches only from >5 incoming so making it default makes sense.

2024-09-04 23: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-08-27 11:26:23

- reply

Thank you for headsup, checked ntfy, nice project. It would be unfortunately unusable for NWC use case, as the wallet do not have access to the received notifications.
In case of NWC my server subscribes to encrypted NWC commands published to minibits relay, reencrypts them with own keys and routes them to the right device based on event recepient tag. They are not shown to the user, just used as data carrier passing the commands from relays to the device.

2024-08-27 08: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-27 00: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 23:26:18

- reply

I will gladly dissapoint you over the next two weeks of fam holiday!
Nevertheless kraXen will work on it over the next week.

2024-08-26 23:11:55

- reply

If you're interested to get the name back, dm me what it was. I can delete it from lnurl/nostr address server so that you can book it again. I'll send you your sats back for the second donation back.

2024-08-26 23:05:49

- reply

You'll find the seed phrase in settings. Keep it somewhere outside the device. Recovery from seed is last resort, mostly in case you lose the device.
For other wallet hiccups that might come due to heavy both protocol and wallet development, there is still local backup of ecash in separate database that can quickly help in some cases.
Enjoy and keep only small amounts in ecash and in r&d focused wallets.

2024-08-26 22: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 12:10:25

- reply

Not really, you just keep your balance pegged to usd as promised by mint in some way

2024-08-26 12:00:08

- reply

Do you have push notifications enabled and working?

2024-08-26 11: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 11:03:41

- reply

I see that in Amethyst as well, even I see that zap receipt is published. When I just scroll the note out of sight and back, zap is shown there.
Doesn't happen when zapping from Minibits over the deeplink, perhaps because the screen is re-rendered when coming back to Amethyst.

2024-08-26 10:53:48

- reply

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

2024-08-26 08: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 08: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-24 08:09:40

- reply

Sounds good.

2024-08-23 15:44:35

- reply

Ah, I see :)
Minibits contacts are currently stored only on device. There is another open github feature request to provide contacts backup that could be implemented via private kind of list as per NIP-51.
When this comes on the table I'll think how to get max out of it.

2024-08-23 08:12:23

- reply

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

2024-08-22 20:16:05

- reply

Thanks! iOS for sure doable (code is react native), just outside of my time possibilities.
There is a plan in the making on how to onboard another dev. So consider it being part of the roadmap, just would not expect it this year.

2024-08-22 14: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 14: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 09: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-12 22: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 22:31:57

- reply

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

2024-08-12 22:25:59

- reply

Hi, just in case please make sure you run the latest version beta.47 - check for it in Dev options.
If that's the case, try to move your balance elsewhere (another mint within the wallet or another ecash wallet) and remove+add mint again.
Feel free to dropme a dm if in need of more help, thank you for trying Minibits!

2024-08-04 10:00:44

- reply

Sorry for troubles, something's badly broken. Would you have few seconds to followup on the dm I've sent you? Have a fix ready but need some technical info from your device to be sure it will fix this ugliness.

2024-08-04 00:44:23

Minibits is now a sleek and fast as a canoe for those receiving lots of zaps. You can claim all your pending ecash in a single batch transaction. Plus, sending is faster and often offline, avoiding ecash splits unless absolutely necessary 🚀.
https://image.nostr.build/c06f42b8c14523ea84a33862df97430c56673957e202000b718cfaffd760fe1a.jpg

2024-08-03 09: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-08-01 08:22:34

- reply

I'll make a special "exchage" kind of UX and transaction type if there will be more USD mints.

2024-07-31 20: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-25 00: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-25 00:22:18

- reply

This. Thanks.

2024-07-23 00:43:05

- reply

We are back up!

2024-07-23 00:29:14

- reply

Thanks for pinging me!

2024-07-16 07:01:11

- reply

#eNuts should have a setting called "increase proofs counter / recovery index" or so. Press it to fix it.

2024-07-15 23: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 22: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 22: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 15: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 18:03:04

Spectacular #Minibits users
#nevent1q…tsc7

2024-06-30 16:37:06

- reply

Ecash in Minibits lives directly on device, so for nwc to work, wallet would need to be in foreground or implement some background processing that is quite constrained by operating system. That seems quite impractical.
There might be parts of the spec that could work like requesting a payment that I'll get to in the future.

2024-06-30 16: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 23:54:24

- reply

I checked the address server and see the issue. You had really old wallet from before seed recovery of addresses was born.
I'll coordinate the fix over DM.

2024-06-28 23:38:12

- reply

If you enter the seed from the old duck wallet to new wallet's address recovery, you should get the duck fly to the new wallet.

2024-06-28 22:59:45

- reply

Ecash can not correctly live in two wallets in parallel. Ability to recover from seed phrase brings unfortunately the need, that each ecash secret key is derived using sequence number.
If you set up two wallets with the same seed, those sequencers will collide, resulting to mint complaints you mention.
Current way to move #Minibits to new device if the old one is available and avoiding the full seed recovery is:
1. Check mint info page > on device info > proofsCounter for highest sequencer value on old device
2. Install wallet on new device. Do not enter Recovery from seed. Get to the wallet and add your mint(s).
3. Go to Backup and recovery. Push Increase recovery indexes so that you reach above the value from old wallet
4. Send ecash from old to new wallet, e.g. using auto-assigned new wallet address as recepient.
5. Enter your seed from the old wallet to Recover wallet address option in Backup and recovery
You're done, uninstall old wallet with zero balance. Other option is to go through full seed recovery, that increases sequencers in the process. However it's much slower, mainky in case old wallet had long history.

2024-06-28 19:04:41

- reply

You're definitely right that it's not ideal. However available react native tor lib broke the build and is not further maintained so I had to abandon it from v0.1.6.
Otoh, Orbot is easier than thought at first glance: Just put Minibits into the list of proxied apps and go. Minibits niw warns to turn it on if user forgot to.

2024-06-28 15: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-27 22:14:34

- reply

It's not burnt if you still keep the seed phrase. Yes there are cases when recovery is not trivial, namely with older wallets.
I suggest to give it another try using the best and fastest recovery tool out there: https://v2alpha.nutstash.app/

2024-06-25 22:23:12

- reply

The flow is as follows:
1. Address is parsed by the wallet and Lnurl well-known link is constructed
2. Lnurl link is requested by sender wallet, retrieving min/max limits and an url to get invoice next
3. Invoice for specific amount is requested by wallet. Server requests quote from the mint that includes an invoice and est fee and passes that to the senderwallet. Server stores related data.
4. Server checks with the mint if an invoice has been paid.
5. If so, server constructs blinded messages for paid amount and asks mint for ecash
6. Server stores retrieved ecash and uses some way (push message+claim api or nostr dm) to send the ecash to the receiving wallet.
7. Wallet receives (swaps ecash for fresh notes with the mint)
So eventually this could be generalized in terms of mints. Because server needs to know how to reach recieving wallet, not sure it can be easily done on the receiving wallet side.

2024-06-24 08:56:19

- reply

Give us some time, it's in the making / testing by community contributors, instructions will follow.

2024-06-24 08:50:20

- reply

Have you been using it with your own mint behind tor so far?

2024-06-23 23:38:39

- reply

If you're not on v0.1.8 please get native upgrade from Play or github. Namely v0.1.6 and before are not safe to be used, missing many fixes and changes.

2024-06-23 23:36:02

- reply

You're right, as per 0.1.8 release notes, tor daemon had to go (not maintained and broke the app build).
However in the process to make v0.1.8 work with mints behind tor using Orbot. Once successfully tested and released, there will be how-to added to the github readme.

2024-06-23 23: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-19 15:02:20

- reply

Hi write me a dm and add version you are running and eventually audit trail of related error transactions if any.

2024-06-16 15:48:09

- reply

As well check you use latest version in dev settings - 0.1.8-beta.28

2024-06-16 15: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 18: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-15 18:26:57

- reply

Do you run latest version 0.1.8-beta.27 and if so do you see any popup with error message on app start?
Please check. There are cases where claiming fails an latest version prints a warning.

2024-06-11 14:07:29

- reply

Ok will check the lnurl server data in the evening

2024-06-11 12: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-11 12:04:58

- reply

No error. Receiving wallet never received so tx stays pending. Legend server mints are likely not live anymore, if that's the case then receiving won't work.

2024-06-10 13: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 13:30:34

- reply

Send it.

2024-06-07 17: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-06 16:17:40

- reply

The best.

2024-06-04 10:30:58

- reply

Submitted as #78 to our github.

2024-06-03 14: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-06-01 18:25:27

- reply

I believe the framing is still in the making. Personally I imagined at the beginning the concept of "buying" ecash for sats and in early version of minibits, the unit itself meant to be <something>sat.
After short discussion with calle roughly a year ago I released the wallet without unit at all.
Later I've just aligned with convention in order to not bring mess into early protocol.
From regulatory pov, idea of buying something could be more easy going for the mint legal structure even it is likely that not all jurisdictions will accept it.
The other model of providing "sats" sounds to be clearly a banking service.

2024-06-01 00: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 21:07:11

Did you? I'll zap you to test it then.
#nevent1q…nuya

2024-05-29 18:49:32

- reply

Sent you 21 sats so I can check it if it won't pass through

2024-05-29 18:46:45

- reply

Wallet address recovery recovers intentionally address only. For full recovery you'd need to make new install and get into it from last onboarding screen. However this is overkill when e.g. just moving to new device without losing old one.

2024-05-29 15:03:55

- reply

There's a brand new recovery tool to recover your address using your original seed without recovering balance - visit Backup and recovery in Settings to try it (you'll be definitely the first one).
DM me your random address or the address you recover to so we can test the zaps.
Please note, that when app is open, zaps are claimed not more often then every minute, require to be on wallet screen. Notifications should work in any wallet state.

2024-05-29 13:05:10

- reply

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

2024-05-29 12:56:35

- reply

Try to put it to your nostr profile so we can zap in 2 taps!

2024-05-29 11:56:20

- reply

Get the new version from Google Play or as an apk from Github.
https://github.com/minibits-cash
https://play.google.com/store/apps/details?id=com.minibits_wallet

2024-05-29 11:53:37

- reply

This concept replaces current sending over #nostr relays that works only when app is open and tend to be very slow for heavy zap collectors.
Ecash is now claimed encrypted + over TLS, leaving no footprint on relays. Notifications are optional, encrypted and carry no ecash.

2024-05-29 11: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 11: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-28 11:18:35

- reply

Hi could you dm me a copy of audit trail of "pending" recovery transaction? Thanks

2024-05-27 11:04:32

Not happy that fast pace of development brings glitches (hope not as much as last upgrade anytime soon!).
Very happy that #minibits built-in failsafes help to quickly get the sats back.
#cashu wallets are not mere clients talking to the servers as your typical custodial wallet or banking app. They hold ecash physically, so being resilient is crucial.
#nevent1q…42sk

2024-05-27 00: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 19:19:49

- reply

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

2024-05-19 20:41:02

- reply

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

2024-05-16 20: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-16 16:30:39

- reply

Which Minibits version are you at? Check in developer options.

2024-05-15 22:37:18

- reply

Great, I'll come to you through dm.

2024-05-15 22:24:37

- reply

Hi, sorry for troubles. Are you able to copy encoded tokens from local backup?
We can follow up over dm to sort it out.

2024-05-15 21: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 21:13:28

- reply

Hi, sorry for troubles. Please go to Backup and recovery > Recovery tool.
If you see backup of your ecash, try to recover them back to wallet or copy them as encoded token to recover in another wallet.
If not, dm me, we'll sort it out.

2024-05-15 17:26:14

- reply

@npub12rv…85vg this one's yours :)

2024-05-15 16:25:00

- reply

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

2024-05-15 16:00:47

- reply

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

2024-05-15 15:01:13

- reply

Seed and nostr key is always stored in Android keystore. Optional encryption encrypts all wallet data

2024-05-15 14: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 14:49:22

- reply

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

2024-05-15 01:00:05

- reply

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