-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wallet recovery not working #350
Comments
Hello @umk0m1qk, Thank you for the report! There are a few important things to know and to check for a successful recovery.
In your case, it is.
In simple terms, if you had a balance in the mint prior to generating the seed, you will have to create a Cashu token from the total balance of the mint and claim it yourself. Only the funds that were generated after the seed can be recovered.
The wallet is currently unable to restore funds from multiple keyset-IDs. Meanwhile, until I fix this, you can restore using a better implementation with more restore options from this web wallet: https://v2alpha.nutstash.app
I am working on a fully functional implementation and a much clearer UI for the restore process where these things are handled in a much more user-friendly way to avoid such situations. I apologize for the inconvenience and for any issues that might have occurred. |
Thanks for the guidance. I moved the balance with a token.
On 6/20/2024 7:52 PM, First-Terraner wrote:
Hello @umk0m1qk, Thank you for the report! There are a few important
things to know and to check for a successful recovery. Is the mint
still online? In your case, it is. Was there a balance in the wa
*DuckDuckGo* removed one tracker. More
<https://duckduckgo.com/-6JnO_og0NFZ_-VNEQxnIelf9fxtgWi4XGxJawpQ1U7JUK1oIVEKtOR2ETFASfVufSpPPTb4DsQIsRnhwlB8NKzUwWdQTDPkHIPGfgDSMHQAL1viOlQWRPUmk2-Z-FkzgHYD-lxQlqMBYcyjsZxFRZ7C4aqMrNzfv96Zh9xXyqf7pBi_tF19GwWIgUWISSp3aFwHNLUSS_e16_RPSOzFWsTUoAxJraZkv3a9z050RvxOxy64TG3hZwAudiy4AX1tYs5OK2pZlcyL7vSNMAQD2SDIQn-QZkUYc23ETJSV1INjHUUKvjHpSAPNCjTkLJEwFO8Occ88qazt4_DsdPXSRkG-UsZW0qDVVVrEW07hS2m83fAhtEkvyTS3dr8xnSs4BJJu87W5VSrJtudEpuK1Tj4Rkj8EpQKd222rjx-AXpho277Sg2sWFpJ5tA0w98ja4SiTTSX-24l4Obtif26V_OePC4v7EB6d-_giSF5fuO8AsOFquBFl8rcRWmkET8QQc>
Deactivate
<https://duckduckgo.com/>
Hello @umk0m1qk <https://github.com/umk0m1qk>,
Thank you for the report!
There are a few important things to know and to check for a successful
recovery.
1. *Is the mint still online?*
In your case, it is.
2. *Was there a balance in the wallet prior to generating the seed
phrase?*
In simple terms, if you had a balance in the mint prior to generating
the seed, you will have to create a Cashu token from the total balance
of the mint and claim it yourself. Only the funds that were generated
after the seed can be recovered.
3. *Did the mint rotate its keyset-ID?*
The wallet is currently unable to restore funds from multiple
keyset-IDs. Meanwhile, until I fix this, you can restore using a
better implementation with more restore options from this web wallet:
https://v2alpha.nutstash.app
* /You can check if the mint has rotated its keyset in the
mint-details screen under "proofs". There is a list of amounts
with a corresponding keyset-ID, and if the amounts have different
keyset-IDs, it means that the mint has rotated its keyset-ID./
I am working on a fully functional implementation and a much clearer
UI for the restore process where these things are handled in a much
more user-friendly way to avoid such situations.
I apologize for the inconvenience and for any issues that might have
occurred.
—
Reply to this email directly, view it on GitHub
<#350 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BF3WR7ZAYTS4MUVGSEMUVCDZILUB3AVCNFSM6AAAAABI6BZOFOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBQHEYDMMBRGE>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--=_/KfBF0kYzxiqql8C/kbac0_=
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Thanks for the guidance. I moved the balance with a token.<br>
</p>
<div class="moz-cite-prefix">On 6/20/2024 7:52 PM, First-Terraner
wrote:<br>
</div>
<blockquote type="cite" ***@***.***">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div>
<div style="display:none;font-size:1px;background:#ffffff;background-color:#ffffff;color:#000000;line-height:1px;max-height:0px;max-width:0px;opacity:0;overflow:hidden;">
Hello @umk0m1qk, Thank you for the report! There are a few
important things to know and to check for a successful
recovery. Is the mint still online? In your case, it is. Was
there a balance in the wa </div>
</div>
<p dir="auto">Hello <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/umk0m1qk/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/umk0m1qk" ***@***.***</a>,</p>
<p dir="auto">Thank you for the report!</p>
<p dir="auto">There are a few important things to know and to
check for a successful recovery.</p>
<ol dir="auto">
<li><strong>Is the mint still online?</strong></li>
</ol>
<p dir="auto">In your case, it is.</p>
<ol dir="auto" start="2">
<li><strong>Was there a balance in the wallet prior to
generating the seed phrase?</strong></li>
</ol>
<p dir="auto">In simple terms, if you had a balance in the mint
prior to generating the seed, you will have to create a Cashu
token from the total balance of the mint and claim it yourself.
Only the funds that were generated after the seed can be
recovered.</p>
<ol dir="auto" start="3">
<li><strong>Did the mint rotate its keyset-ID?</strong></li>
</ol>
<p dir="auto">The wallet is currently unable to restore funds from
multiple keyset-IDs. Meanwhile, until I fix this, you can
restore using a better implementation with more restore options
from this web wallet: <a href="https://v2alpha.nutstash.app" rel="nofollow" moz-do-not-send="true" class="moz-txt-link-freetext">https://v2alpha.nutstash.app</a></p>
<ul dir="auto">
<li><em>You can check if the mint has rotated its keyset in the
mint-details screen under "proofs". There is a list of
amounts with a corresponding keyset-ID, and if the amounts
have different keyset-IDs, it means that the mint has
rotated its keyset-ID.</em></li>
</ul>
<p dir="auto">I am working on a fully functional implementation
and a much clearer UI for the restore process where these things
are handled in a much more user-friendly way to avoid such
situations.</p>
<p dir="auto">I apologize for the inconvenience and for any issues
that might have occurred.</p>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>
Reply to this email directly, <a href="#350 (comment)" moz-do-not-send="true">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/BF3WR7ZAYTS4MUVGSEMUVCDZILUB3AVCNFSM6AAAAABI6BZOFOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBQHEYDMMBRGE" moz-do-not-send="true">unsubscribe</a>.<br>
You are receiving this because you were mentioned.<span style="color: transparent; font-size: 0; display: none; visibility: hidden; overflow: hidden; opacity: 0; width: 0; height: 0; max-width: 0; max-height: 0; mso-hide: all">Message
ID: <span><cashubtc/eNuts/issues/350/2180906011</span><span>@</span><span>github</span><span>.</span><span>com></span></span></p>
<script type="application/ld+json">[
{
***@***.***": "http://schema.org",
***@***.***": "EmailMessage",
"potentialAction": {
***@***.***": "ViewAction",
"target": "#350 (comment)",
"url": "#350 (comment)",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
***@***.***": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
</blockquote>
</body></html>
--=_/KfBF0kYzxiqql8C/kbac0_=--
|
Describe the bug
wallet recovery not working
To Reproduce
Steps to reproduce the behavior:
Expected behavior
a successful wallet recovery
Smartphone (please complete the following information):
-old phone: stock One Ui 6.0 (android 14) on galaxy a23
-new phone: GrapheneOs on pixel 8a build 2024051600
Additional context
all ecash balance is on a single mint: mint.minibits.cash/Bitcoin
The text was updated successfully, but these errors were encountered: