Hi, did you attempted recovery of your wallet recently? I can not find justprint566 name on the lnurl server. Please check which wallet address you see in the wallet. DM me what you see.
You can send ecash as a nostr direct message. Minibits wallwt addresses work as both nostr identities (meant to receive ecash only, not for any other use as their private key is never revealed); and as lightning addresses (meant to be attached to users' public nostr profiles or for any lightning stuff.
I signed my first nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhs79prlk release. Admire well-thought and lean concept + perfect execution by zapstore team!
Try any Minibits wallet address, like mine:
Ok. Now please get to the detail of one of the errored transactions and copy and DM me the audit trail section.
There are details why those receiving txs failed. We'll then sort it out.
Will check the mint, if there are not some proofs stuck in pending state. Might not a wallet issue.
Hi, after you restart, do you see any receiving transactions with error status in the list?
As well, try to make regular send / receive transaction within the wallet (not nwc) to make sure wallet itself is operational.
Minibits batches received tx if there is more then 5 to claim when wallet starts. Batching can be turned off.
I have not yet dig into how to release to Zapstore, my shame.
Previous releases were available there, by detecting new release on Github but I am not familiar with the process.
Get a new 0.3.4-beta native release from Google Play or from github, link above.
New Minibits with Tap-to-pay is live on Android!
- Reads a cashu requests or lightning invoices via NFC and pays instantly
- Shares invoices or cashu tokens (emulating NFC host) so you can even tap two Minibits wallets
Prototype intended for testing w POS devices, that have their NFC antennas on front side but nevertheless very funny to play with 🚀 !
Very early, test with few sats only.
https://github.com/user-attachments/assets/d52700af-469b-42d7-a35b-1e11e043ef3f
Get an 0.3.4-beta update from Google Play or as an apk release from Github:
https://github.com/minibits-cash/minibits_wallet/releases
Ability to pay over NFC (without sharing option) should work on iOS as well, but will be released later.
New Minibits with Tap-to-pay is live on Android!
- Reads a cashu requests or lightning invoices via NFC and pays instantly
- Shares invoices or cashu tokens (emulating NFC host) so you can even tap two Minibits wallets
Prototype intended for testing w POS devices, that have their NFC antennas on front side but nevertheless very funny to play with 🚀 !
Very early, test with few sats only.
https://github.com/user-attachments/assets/d52700af-469b-42d7-a35b-1e11e043ef3f
When testing, sent hundred such zaps to myself. Here's a real one for you!
Checked the payment, it was paid and server says that it issued the ecash just after.
Either wallet might have missed the response, very rare but happens.
Or you might have an incoming transaction with error (if wallet failed to swap for fresh ecash for any reason).
In any case I set the ecash as unclaimed to force the wallet to claim it again. Restart and dm me any transaction details / error you'll get.
Wallet tries to heal that, but if there is more it could repeat.
NWC is not an ecash mint feature, so you can't switch unfortunately.
Pending means some of your balance is pending on the mint side, linked to some previous lightning payment that did not complete.
Try Recovery > Remove spent ecash.
Oh after the latest update making multiple zaps in quick sequence should be much faster!
Well in this case zaps are sort of meant to be public.
On the other side, direct ecash sends over nostr with Minibits use the newest nostr encryption for direct messages (nip-17), so they are pretty private even against the relay operator.
Yes as a fallback, but in that case, connections are interrupted by the OS if wallet goes background / killed. Not very practical
New Minibits native release is out! Various security improvements and an option to enter transaction amount in fiat currency, converted to the right amount of #Bitcoin SATS 🌽
Update to 0.3.0 now on Android, iOS Testflight got stuck in the approval process for now...
https://blossom.primal.net/2098bb96962385758919a4c55646f3d2ab9abb7ccbc4de0e1008dbfd2c012f45.mp4
And do not add more relays. NWC connection defines own relay and nostr clients support only a single one here.
Not now. Curious about what would be your use case? Complex but I might consider that.
You can get it from Testflight. For EU based users, Minibits is available to install from alternative store, the new Freedom store. Check minibits.cash for links.
Did you receive my dm with the instructions sent? Please check.
Will need to look at it. Thanks
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.
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.
Would it make sense to make a japanese wallet translation or something else?
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.
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.
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.
To start, put your minibits address to your nostr profile so that I can zap you!
Thank you! There is a lot of not-coding stuff missing. Will think of that during upcoming holidays and will come back to you!
Sounds like a great plan. However for operational reasons I intentionally keep min channel size quite high (10m sats) as well as not focusing to maximize routing traffic (I keep fixed and relatively high routing fees).
Have been operating a routing node from 2018 and learnt lessons on how this stuff can go wrong. Need to focus my efforts on the wallet dev so keeping the node operations low and secure.
Had to recall the release. Sorry for troubles.