I did my first real-world economically-not-completely-insignificant ecash wallet recover process from a seed phrase with nostr:npub1kvaln6tm0re4d99q9e4ma788wpvnw0jzkz595cljtfgwhldd75xsj9tkzv wallet today and trust me β I really wanted this one to work.
I first exported all tokens I could access in Minibits and put them into a text file, just in case. I then backed up my mint URL list (I had 6 different mints in this wallet), and then wrote down the derivation path counter for each mint (not strictly necessary but just in case the app doesn't figure it out by itself). Then I made sure that I have my seed phrase stored securely and wiped the wallet app from my phone.
I started Minibits again set up a new wallet. I entered the seed phrase, and entered all my mint URLs that I had written down before the restore. Because I'm a power user, my wallet took quite some time to restore and I had to press the button to continue many times (I could give some UX feedback that the dev appreciated and indicated to make this process more seamless and automated in the future).
Eventually all my sats popped back in my wallet and I could use the wallet just like before! π₯
It's felt a bit like magic. I've spent so much of my time on crafting this seed phrase backup process, implementing testing it a thousand times, writing a spec and discussing it with other devs, but I never had to actually use it because of a real accident. Now, seeing it implemented so well by other developers and actually making ecash so more useful and safe to use is pretty amazing.
Ecash seed phrase restore is currently live or in dev in these wallets: Live: Nutshell, Minibits βΒ Dev: Nutstash, eNuts, Macadamia.
Onward π₯π«‘
Took some time and process can be improved for wallets with long history and many mints. But at the end calle's nuts were back!
There is already a working concept in command line wallets to lock the sent token to receiver's pubkey.
That way offline send can work without the risk of sender double spend before receiver comes online.
Will take some time until it lands in mobile wallets. Naive offline send/receive proof of concept is available in Minibits.
Were you able to complete the transaction? If not, please ping me into the DM.
Subtle redesign of public contacts (nostr follows) dropped in latest #minibits update.
Using it as an ongoing R&D to rethink how Lightning and Ecash UX flows should coexist in a way that makes sense for users, not builders. What works will later expand to core wallet navigation.
Minibits is an ecash wallet, so we keep big green one button dedicated to sending.
However minibits now retrieves lightning addresses from the followed profiles and adds option to pay to them on click. Asking for sats (payment request) becomes less prminent then before.
Hope you'll enjoy the direction!

I meant easier connectivity to the mint itself from the mobile wallet. Lightning node connectivity relates to other nodes in the network.
Love to hear that #minibits Tor daemon did find its users. It's quite niche feature because there are no well known mints available over Tor.
However for folks that do their own stuff mints and lightning nodes on their own hw, it can really simplify networking, as they do not need static public IP address.
More mints might have some advantages, not far from reasons why people hold accounts with more than one bank.
Ecash wallets like #minibits allow you to spread the trust in funds custody across more then one mint: typical custodial lightning wallets don't provide that.
In the longer term if ecash takes off, mints might differentiate by other features like providing ecash representing other assets like USD or having good lightning connectivity in specific regions thus providing reliable pay-ins and -outs etc.
We are very early.
Can't get any better. Thanks nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z!

Minibits now shows who you've received your zap from!
Just go to settings to get this small update over-the-air dedicated to zap-collectors.

Is there any way to set the lowest zap amount on #amethyst to less then 500 sats?
After first week of Minibits #nostr account I am getting squeezed of all sats donated for custom minibits.cash wallet addresses priced at 100 sats!
Please help, zaps on amerhyst feel too good to not to be sprayed.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z
Thanks you all, love it.
Is there any way to set the lowest zap amount on #amethyst to less then 500 sats?
After first week of Minibits #nostr account I am getting squeezed of all sats donated for custom minibits.cash wallet addresses priced at 100 sats!
Please help, zaps on amerhyst feel too good to not to be sprayed.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z
It *could* be web wallet communicating with nostr/lnurl servers, mints and relays.
Just keep in mind that to keep the wallet state safe and working, web is far from ideal.
For instance, Minibits uses 2 separate storage technologies (mmkv as fast read/write, sqlite as append only backup) to prevent / recover from storage failures. This is not possible on the web. Safe keys store is as well big challenge on the web.
Minibits is react native app, so there is no other showstopper than to spend enough time to kick the ios build until it's working.
I have appstore dev account, so should be possible to release if not stuck in approval.
Minibits tries hard to earn its first eagle feather:
1. Random transactions failures should be gone for good (at least once @calle won't be able to break it for a single day)
2. Nostr relays now reconnect nicely: no need to do it manually or even restart.
Go to settings to get the update over the air and enjoy!
#m=image%2Fjpeg&dim=1079x1322&blurhash=_JHnpT-%3AIo%3FGIo%252%251xtIVIV%252NGxat6%7EVNGIoNGj%40ayRk0Lt6jZNGxtRkM%7C-ojZRjkBt6R*WC9aayt6ofWVR*oLoeayofs%3AWBayayNGoLt6WCWVoLoLayj%40j%5Bj%5Bayj%5Bj%5B&x=b6b0732f56e50b2adb8cd9fe59e47ede77ee763d3c9913f128bc8eb3efe837c5
Your Minibits wallet font made me to zap instinctively!
Any reason for bluetooth instead of nfc?
I do and this is fresh new nostr account dedicated to Minibits.
Sorry, stumbled only now over your note.
Were you able to receive? Android kills websocket connections here and there so either reconnect to relays in settings or restart the wallet. According to lightning2ecash bridge logs the token has been published as an encrypted dm to default relays.
If nothing arrives, ping me and I'll send the token to you.
Minibits uses it's own relay and few public relays as a backup by default.
You might want to send ecash to somebody who's not using minibits and his nip05 address server does not announce his relays. Then you'd need to add manually.
Or you might want to publish all your wallet comms over nostr to your own relay.
Sorry for annoying error, has been due to the mint upgrade that required further patch. Fix landed yesterday, mint works as expected from then on.


#m=image%2Fjpeg&dim=1008x2244&blurhash=%5B%256lNHj%5DWEaygSaya%23j%5Bp2fka%23aybKazj%5Dj%5BjqfPf5ayacfRj%5Bj%5BjWfPjrayaxfRj%3FfkbJa%7Dj%3FfQ&x=2660b6228972cc789d4759b3f450ffe63ed86eefc86a64054018436868431f1e
#m=image%2Fjpeg&dim=1008x2244&blurhash=%5B14Bwaxt9txa%7EWs%3AI%3As%3A8_RjELoL4.M%7Bxvog%25%23RjwekC%25%23jZ%23mkC%3F%5Es.rWkCOWs%3A%3D%7CR%254nRj%25MWB&x=79ed1c729ad52378d1560fb2b071bf6cd9d4a97e4839b6039a45b2d227af151b
#m=image%2Fjpeg&dim=1008x2244&blurhash=%5Bs6b%24cj%5Bahayb%24j%5Bj%5DfQp2azafj%5Bbff6fij%40kEayayfQk8ayjsfQaJazj%40fRk6fkjufQaJfRkBa%7C&x=f897f5e15b0d0a527727ec3f24e8a4ee808a75316234d8e3b3a4b79d05242b83
#m=image%2Fjpeg&dim=952x1920&blurhash=%5Br5ryLj%5BWCaykvj%5Ba%23fQg7fQazj%5BkFfPazj%5BaxfQj%5BfQjWj%40jsayacfQfkfQawfQj%5BfQj%5Dj%40fPay&x=e36c18ab445bccd3f60c79e20f0f4c0576abc059941a6980ce32c001216bcab5