# Wallet Passphrase has a bug!?

**URL:** <https://forum.pokt.network/t/wallet-passphrase-has-a-bug/1829>\
**Category:** Help\
**Tags:** app-support\
**Created:** [January 18, 2022, 1:46pm UTC](https://forum.pokt.network/t/wallet-passphrase-has-a-bug/1829 "2022-01-18T13:46:49Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![samwithacoin](https://forum.pokt.network/user_avatar/forum.pokt.network/samwithacoin/32/543_2.png) [@samwithacoin](https://forum.pokt.network/u/samwithacoin)\
**Post date:** [January 18, 2022, 1:46pm UTC](https://forum.pokt.network/t/wallet-passphrase-has-a-bug/1829/1 "2022-01-18T13:46:50Z")

</div>

I could not open import my wallet with the json file and my passphrase, the app doesen’t recognise my passphrase anymore.  
 → First I thought I accidentally modified my passphrase, but now I encountered another similar problem: I tried to create a new wallet and followed the passphrase instruction, I entered this: _Ghee46M?_ which technically fulfils the requirements and it doesen’t work as well.

Is there a bug/problem with the wallet? and can someone of the team help me with this issue?

Tried on Safari/chrome on a macbook.

 ![Screenshot 2022-01-18 at 14.45.49](https://forum.pokt.network/uploads/default/original/1X/65e1bf2bcd4485c9f5f154324828b9e5410c070c.jpeg)

---

<div class="post-metadata">

**Author:** ![JackALaing](https://forum.pokt.network/user_avatar/forum.pokt.network/jackalaing/32/39_2.png) [@JackALaing](https://forum.pokt.network/u/JackALaing)\
**Post date:** [January 18, 2022, 3:50pm UTC](https://forum.pokt.network/t/wallet-passphrase-has-a-bug/1829/2 "2022-01-18T15:50:58Z")

</div>

? is not a valid character, the copy is wrong. This was supposed to be updated before release but must have slipped through the cracks.

Use a different password and you will be able to create the wallet without issues. Besides, this password is now doxxed 😉

---

<div class="post-metadata">

**Author:** ![samwithacoin](https://forum.pokt.network/user_avatar/forum.pokt.network/samwithacoin/32/543_2.png) [@samwithacoin](https://forum.pokt.network/u/samwithacoin)\
**Post date:** [January 18, 2022, 4:24pm UTC](https://forum.pokt.network/t/wallet-passphrase-has-a-bug/1829/3 "2022-01-18T16:24:51Z")

</div>

Ok great, but my original Passphrase of my existing wallet also contains a “?” - that’s probably why I can’t access my wallet anymore?

How can I get my wallet back?

---

<div class="post-metadata">

**Author:** ![Rocket](https://forum.pokt.network/letter_avatar_proxy/v4/letter/r/e79b87/32.png) [@Rocket](https://forum.pokt.network/u/Rocket)\
**Post date:** [January 19, 2022, 6:01am UTC](https://forum.pokt.network/t/wallet-passphrase-has-a-bug/1829/4 "2022-01-19T06:01:33Z")

</div>

Looking forward to further progress.

---

<div class="post-metadata">

**Author:** ![samwithacoin](https://forum.pokt.network/user_avatar/forum.pokt.network/samwithacoin/32/543_2.png) [@samwithacoin](https://forum.pokt.network/u/samwithacoin)\
**Post date:** [January 19, 2022, 3:52pm UTC](https://forum.pokt.network/t/wallet-passphrase-has-a-bug/1829/5 "2022-01-19T15:52:47Z")

</div>

Is there any update on this? I am still locked out of my wallet.

---

<div class="post-metadata">

**Author:** ![steve](https://forum.pokt.network/user_avatar/forum.pokt.network/steve/32/512_2.png) [@steve](https://forum.pokt.network/u/steve)\
**Post date:** [January 19, 2022, 5:19pm UTC](https://forum.pokt.network/t/wallet-passphrase-has-a-bug/1829/6 "2022-01-19T17:19:44Z")

</div>

Hey @samwithacoin I ran into the same issue. I ended up chaning my passphrase. If you have access to a Pocket Node you can use the CLI and the `pocket accounts update-passphrase <address>` to change the passphrase for an account. Details are here [Accounts Namespace - Pocket Core](https://docs.pokt.network/core/specs/cli/accounts#update-an-accounts-passphrase) - if you can’t wait for the wallet to be fixed. Hope that helps.

---

<div class="post-metadata">

**Author:** ![samwithacoin](https://forum.pokt.network/user_avatar/forum.pokt.network/samwithacoin/32/543_2.png) [@samwithacoin](https://forum.pokt.network/u/samwithacoin)\
**Post date:** [January 19, 2022, 8:45pm UTC](https://forum.pokt.network/t/wallet-passphrase-has-a-bug/1829/7 "2022-01-19T20:45:36Z")

</div>

Thank you very much for the input Steve, good to know access can be restored.

However I’m not technically capable to do this - can the wallet be fixed by the tech team?

---

<div class="post-metadata">

**Author:** ![EZ\_Rock](https://forum.pokt.network/user_avatar/forum.pokt.network/ez_rock/32/583_2.png) [@EZ\_Rock](https://forum.pokt.network/u/EZ_Rock)\
**Post date:** [January 20, 2022, 2:05am UTC](https://forum.pokt.network/t/wallet-passphrase-has-a-bug/1829/8 "2022-01-20T02:05:01Z")

</div>

From what I understand the private key can be used in this case. It will ask you for a temp passphrase on a session by session basis.

---

<div class="post-metadata">

**Author:** ![EZ\_Rock](https://forum.pokt.network/user_avatar/forum.pokt.network/ez_rock/32/583_2.png) [@EZ\_Rock](https://forum.pokt.network/u/EZ_Rock)\
**Post date:** [January 20, 2022, 2:06am UTC](https://forum.pokt.network/t/wallet-passphrase-has-a-bug/1829/9 "2022-01-20T02:06:46Z")

</div>

While we are on the topic, can anyone tell me what the public key is used for?

The string under the public address is what I am referring to.

And also, why does this key include the second half of the private key?

---

<div class="post-metadata">

**Author:** ![blockjoe](https://forum.pokt.network/user_avatar/forum.pokt.network/blockjoe/32/462_2.png) [@blockjoe](https://forum.pokt.network/u/blockjoe)\
**Post date:** [January 20, 2022, 3:23am UTC](https://forum.pokt.network/t/wallet-passphrase-has-a-bug/1829/10 "2022-01-20T03:23:27Z")

</div>

The second half of your private key is your public key because of how Pocket generates it’s wallets.  
See:

> **[PBKDF2](https://en.wikipedia.org/wiki/PBKDF2)**
>
> In cryptography, PBKDF1 and PBKDF2 (Password-Based Key Derivation Function 1 and 2) are key derivation functions with a sliding computational cost, used to reduce vulnerability to brute-force attacks.
> PBKDF2 is part of RSA Laboratories' Public-Key Cryptography Standards (PKCS) series, specifically PKCS #5 v2.0, also published as Internet Engineering Task Force's RFC 2898. It supersedes PBKDF1, which could only produce derived keys up to 160 bits long. RFC 8018 (PKCS #5 v2.1), published in 2017...

The public key is used for actually signing and verifying transactions.

---

<div class="post-metadata">

**Author:** ![samwithacoin](https://forum.pokt.network/user_avatar/forum.pokt.network/samwithacoin/32/543_2.png) [@samwithacoin](https://forum.pokt.network/u/samwithacoin)\
**Post date:** [January 20, 2022, 11:31am UTC](https://forum.pokt.network/t/wallet-passphrase-has-a-bug/1829/11 "2022-01-20T11:31:02Z")

</div>

Correct, but for some odd reason I did not extract the private key for this wallet because I thought Passphrase + JSON file is enough for the moment. So still sitting in the dark on how to resolve this.

Or is it possible to extract the private key from my JSON with the passphrase?

---

<div class="post-metadata">

**Author:** ![blockjoe](https://forum.pokt.network/user_avatar/forum.pokt.network/blockjoe/32/462_2.png) [@blockjoe](https://forum.pokt.network/u/blockjoe)\
**Post date:** [January 20, 2022, 3:43pm UTC](https://forum.pokt.network/t/wallet-passphrase-has-a-bug/1829/12 "2022-01-20T15:43:50Z")

</div>

We’re working on a fix for this as we speak. Would you mind reaching out to me directly so I can collect some more details about your system/what problem you’ve experienced.

---

<div class="post-metadata">

**Author:** ![blockjoe](https://forum.pokt.network/user_avatar/forum.pokt.network/blockjoe/32/462_2.png) [@blockjoe](https://forum.pokt.network/u/blockjoe)\
**Post date:** [January 20, 2022, 6:38pm UTC](https://forum.pokt.network/t/wallet-passphrase-has-a-bug/1829/14 "2022-01-20T18:38:16Z")

</div>

If anyone is experiencing issues where they cannot import their key file, try to import the key file through Incognito/Private browsing mode.
