I can't see the issue on /info. I can investigate more after tommorow, on travel without pc until then.

Hey, I've set it up for mint.minibits.cash on proxy 2 days ago, including for preflight requests. For which exact request do you get the error?

Hey, I've configured the cors support for pre-flight requests on the proxy. Please retry.

In the recent update, there is new option to retry to receive in case the transaction failed (and remained both in DRAFT or selected ERROR statuses - e.g. in case mint was offline at the receive time).

Thanks for testing Minibits and making it better!

Good to hear it worked for you and I appreciate your zap!

Do you mean draft status of a transaction?

Good question. Seed as such backs up only ecash - it allows, with cooperating mint, to regenerate lost ecash into new wallet.

In new wallet, new Nostr keys are always created, as the private key never leave the device.

However, as a last part of recovery process, newly installed Minibits wallet passes hash of the seed and new nostr public key to Minibits nostr address server. If match is found, corresponding nostr and lightning address is re-linked to new keys.

That way, your minibits nostr and lightning address re-appears in the new wallet. Update is finally published to default nostr relays.

Have not thought about that yet. I'd like to finish the cashu protocol in terms of other balances than sats and offline payments.

In terms of what's next: I keep the direction open. More inclined to add other protocol if it would provide rather different than similar trust options, but open for discussion and demand.

Zapped back instinctively. Enjoy!

Paid zaps on the way to #Minibits do not expire as they are converted to ecash at the moment of settled lightning payment. Then they wait on nostr relay to be received.

However due to major mint upgrade, mint's keys rotated to new ones and wallet required to update as well.

For failed tx before wallet managed to update, it is enough to retry, no need to go tgrough full recovery from seed.

Thanks to all trying to help to Gzuuus

Thank you for the report. The issue relates to recent mint upgrade and should not repeat anytime soon. Glad the prepared reclaim path worked for you.

nostr:nevent1qqsfae8x2drhagf8fntr67jh2shwql9ja7seh65c4mwc5umwlkzwh9gppamhxue69uhkummnw3ezumt0d5pzpveml85hk78n2622qtnthmuwwuzexuly9v9gtf3lykjsa076magdqvzqqqqqqy87pk8q

Thanks for feedback, will make UX more precise.

Pass your feedback to me, thanks

Minibits dev here. Did you try to go through multiple recovery intervals ahead still without finding any ecash?

You can dm me the details, might be mint upgrade related but we will sort it out.

Minibits dev here. Did you try to go through multiple recovery intervals ahead still without finding any ecash?

You can dm me the details, might be mint upgrade related but we will sort it out.

I meant LNbits <> LND comm.

Using GRPC

Put it to your nostr profile as your lightning address so I can zap you in ecash.

Own LNBits instance is still part of the stack as it helps to keep mint's funds segregated from funds needed to have liquidity reserve on the lightning node.

But now mint is no more LNBits extension but runs pure Nutshell in it's own container.

First major #Minibits mint upgrade completed today. Huge thanks to nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg to help me to play with fire.

Now ready for really cool stuff to come.

IMPORTANT: Please accept latest Minibits wallet update immediately before usage, it includes important fix to support smooth mint keys rotation.

IMPORTANT: Keep in mind Minibits is still in research and wild development of best ecash ever. Do not use with money you'd regret to break up with.