Closed stevenwelsh565 closed 5 months ago
Together with fee reserve the payment hit the mint limit. Please copy me the errored transaction audit trail to support@minibits.cash email, or using nostr to dev@minibits.cash. Do not post it publicly here.
As a quick try you can restart the wallet under normal behavior it should try to sweep ecash from pending state back to spendable after failed lightning tx.
I tried emailing support@minibits.cash
from gmail and got this error:
The recipient server did not accept our requests to connect. For more information, go to https://support.google.com/mail/answer/7720 [minibits.cash 2a01:4f8:c2c:bb96::2: timed out] [minibits.cash [195.201.20.134](http://195.201.20.134/): timed out]
Sorry I'll need to solve some unintended DNS related issues. In the meantime, please send it to bitango.app@gmail.com
Done
Thank you. Retested your scenario and found a bug where ecash returning after failed lightning payment from pending state back to spendable balance missed unit param, thus was not included into balances. Hotfix is on the way as an over the air update.
I think the easiest way to recover should be to go to Settings > Backup and recovery > Local recovery tool and reload the wallet from the local backup that sets the unit if missing in the process.
Will the hotfix also handle my case? I'm not in a rush to get the funds back so I'm happy to wait until it is available on google play.
On Fri, Jun 14, 2024 at 8:28 AM minibits-cash @.***> wrote:
Thank you. Retested your scenario and found a bug where ecash returning after failed lightning payment from pending state back to spendable balance missed unit param, thus was not included into balances. Hotfix is on the way as an over the air update.
I think the easiest way to recover should be to go to Settings > Backup and recovery > Local recovery tool and reload the wallet from the local backup that sets the unit if missing in the process.
— Reply to this email directly, view it on GitHub https://github.com/minibits-cash/minibits_wallet/issues/81#issuecomment-2167523141, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJDMDSBXTEWYIRLSMFLFSL3ZHKSSNAVCNFSM6AAAAABJERAENKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRXGUZDGMJUGE . You are receiving this because you authored the thread.Message ID: @.***>
Hotfix prevents future cases to happen. To fix your existing ecash, follow the steps above.
Thanks for reporting the issue.
Thanks. I tried using the "Local recovery tool", and clicked on "Recover to wallet" While that screen showed 1038965 SATS as being present, the sats still didn't show up in my wallet, even after reloading the app.
On Fri, Jun 14, 2024 at 12:22 PM minibits-cash @.***> wrote:
Hotfix prevents future cases to happen. To fix your existing ecash, follow the steps above.
Thanks for reporting the issue.
— Reply to this email directly, view it on GitHub https://github.com/minibits-cash/minibits_wallet/issues/81#issuecomment-2167911045, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJDMDSDLVSKLDNI5TA2FTQTZHLOCDAVCNFSM6AAAAABJERAENKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRXHEYTCMBUGU . You are receiving this because you authored the thread.Message ID: @.***>
Will require yet one small fix of too restrictive validation of backed up proofs, sorry.
I'll write here when I'd release it. After update, you'd run local recovery again and it should pass.
Sounds good! Let me know.
On Fri, Jun 14, 2024 at 6:49 PM minibits-cash @.***> wrote:
Will require yet one small fix of too restrictive validation of backed up proofs, sorry.
I'll write here when I'd release it. After update, you'd run local recovery again and it should pass.
— Reply to this email directly, view it on GitHub https://github.com/minibits-cash/minibits_wallet/issues/81#issuecomment-2168578971, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJDMDSAERRI5BWLN7EA2YSDZHM3KBAVCNFSM6AAAAABJERAENKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRYGU3TQOJXGE . You are receiving this because you authored the thread.Message ID: @.***>
Releasing fix in local recovery process as beta.28. On travel, so had not space to simulate whole process, please turn on debug level logging in developer options and retry to recover from local backup.
Thanks! That fixed it.
With the https://mint.minibits.cash/Bitcoin mint I attempted a 999999 sat payment. This lead to a MINT_ERROR, saying "Maximum melt amount is 1000000 sat." But my coins never were returned to my wallet.
How can I recover them?