Topic: Will not accept my passphrase! any help please! (Read 444 times)

Glad to hear that you were able to finally access your coins. 

Do you know what the problem was (i.e. why you weren't able to import them at your first and second try) ? Just asking out of curiosity.

Hi Bob123 and all.

Firstly...  SUCCESS!!!   My BCC and BTG is now in my Exodus wallet.

I had 9 lines of PK's

only one line contained the coins.  It was line 2
The other showed error or "there are no coins associated with this address"

I understood that all my 9 keys contained coins. but in only 1 of them.  (I did put together my Bitcoin in 8 or 9 transactions)

Also I was incorrect. You can paste keys into Exodus. 

So now my world is alligned LOL.

Thank you so very much to you and everyone who helped and stuck with me on this.

Man, Armory is so much easier to understand and to navigate now.
There are great resources for everyone.

Thank you GoatPig.  You are legend!   There cannot be anything safer than Bitcoin Armory and I truly believe that if Armory was staffed and located,  It is a billion$ business as we enter a new phase of Bitcoin.  The world need security like this.  You guys are amazing and should be rewarded for this big time.  There are buyers and investors.  Rethink the brand and the product.  Armory has history and works!

Peace and Love! Peace and Love!

Hi Bob123 and all.

Firstly...  SUCCESS!!!   My BCC and BTG is now in my Exodus wallet.

I had 9 lines of PK's

only one line contained the coins.  It was line 2
The other showed error or "there are no coins associated with this address"

I understood that all my 9 keys contained coins. but in only 1 of them.  (I did put together my Bitcoin in 8 or 9 transactions)

Also I was incorrect. You can paste keys into Exodus. 

So now my world is alligned LOL.

Thank you so very much to you and everyone who helped and stuck with me on this.

Man, Armory is so much easier to understand and to navigate now.
There are great resources for everyone.

Thank you GoatPig.  You are legend!   There cannot be anything safer than Bitcoin Armory and I truly believe that if Armory was staffed and located,  It is a billion$ business as we enter a new phase of Bitcoin.  The world need security like this.  You guys are amazing and should be rewarded for this big time.  There are buyers and investors.  Rethink the brand and the product.  Armory has history and works!

Peace and Love! Peace and Love!

You don't have to panic at all. You don't need to move your coins prior to the fork.

You will always be able to access your coins. Whether they are now assigned to the current public key, or any other. Technically it doesn't matter at all.


Can you verify that your private keys do ONLY contain these characters:

Note, that there is no uppercase i (I), o (O) and no lowercase L (l) or zero (0).

May it be possible that you have somehow confused one of these chars ?

UPDATE:  still stuck but went to bitaddress.org and entered 1 line PK
It looks good!  Confirmed as it should will other key options.

waiting on Exodus to reply.

ok. here are top 3 PKs on my list

51 characters... I going to shorten it but show first and last as requested.

a) 5Js5skxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx7jt4c3F2R
b) 5KPS7wxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxs08XrmNjt
c) 5Ji55GxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxEjRuKwKpG

On Exodus you cannot copy/paste. Enter manually and painstaking triple checked.

That said I did contact Exodus.  (Great email commu)
They were struggling with it. 
Here are their notes. 

And this is where we are......

Exodus: Could you please tell me what version of Exodus are you using? Version 1.64.0 is our latest release
Me: Yes Version 1.64

Exodus: Can you please tell me which wallet are you trying to import into? Are you importing them into BCH & BTG wallets or are you trying to import them into BTC wallet?
Me: I did first try Bitcoin.  So I did try NCH & BTG wallets.  Same error.

Exodus: You'll need to import them on BCH and BTG wallets since those are the chains which hold your funds.
            Please go ahead and try with one PK, let me know how it goes.
Me: Tried. I entered one key into BCC
               "enter private key"
               I get error nonbase58 character

Exodus: Can you please ensure there is no space at the beginning or the end of the private key you paste? This is very often very easy not to notice.
Me:  No spaces ... triple checked all 51

Exodus: The non-base 58 error is thrown when there is a foreign character included in the private key, it is weird that there are no spaces and the wallet is showing this error.
             Is there a possibility to extract any other format of PK from Armory wallet? Or, are these private keys encrypted by a password by any chance?

Me:   I do not believe there is another option no. Encrypted by a password?  I believe so.   or understand it is.

Exodus: Thank you for writing back and letting me know.
             Do you mind downloading the bitaddress.org website and test the below in offline mode?

Visit bitaddress.org and download the website and run it locally
Click on the 'Wallet Details' tab
Enter your private key there and press View Details
If the PK is not encrypted, you should be able to view your public address etc. If the PK is encrypted, it will throw and encrypted PK error.

Let me know how it goes. I am only asking you to test this since we do have the ability to import password-encrypted PKs in Exodus.

Me: ok I will.  I starting to panic because of BCC fork is 1 week away.  I will try this.

Update:  I didnt go to bitaddress yet.  Life took over.   What do my Amory friends say about this first.  Good idea?

Are you manually typing the keys? Or are you using copy/paste?

Armory shouldn't be generating any non-base58 characters... unless it is doing something weird like copying a blank space or newline character when you copy/paste

Can you show us how your private key looks like (WITHOUT POSTING IT).

For example, don't change the first 3 and last 3 chars, but replace everything in-between with X's.


Your private key should look like this:

You might post it like this:


Or (if you don't want to post it, which isn't necessary), verify that there are no spaces and that all chars are base58.
The base58 charset is:

update.
 Yes I can confirm my private keys.

So on EXODUS when I import these keys to EXODUS Wallet (BTC) I get ERROR!  Non-base58 character
I retried 3 times. same error message   agh!

When I enter the same keys into AUTOMIC i get a red "service unavailable" message.

note: I took out the spaces in the keys.  It is a series of 6 X 8 +3 characters = 51
        so it has no spaces.  
I did not include Privbase58: (text)    just the key

I'm getting close but.  I sure appreciate your great input.  Should be a no brainer at this point

Because Armory is an "HD" wallet and actually has a "pool" of keys that are pre-generated... from memory, it is 1000.

If you followed my guide and ticked the "show un-used (address pool)" box, it will display ALL of these addresses/keys... the reason to do this, is that if Armory is not correctly synced, it may think some of your addresses/keys are "unused" so won't display them, even if they have in fact been used.



Did you actually change Atomic from ETH to BTC when you attempted to "import" your private? It defaults to ETH and will give "Invalid Private Key" unless you change to "Bitcoin (BTC)"

Also, Atomic doesn't actually "import" your private key... it uses "sweep", as you can see from the screenshot... it tells you it is going to send all spendable coins "minus transaction fee" to your Atomic wallet.






More correctly, I would assume all your BCH is contained on one (or more) key(s)... depending on how many addresses you had actually received BTC to, prior to the fork.

Oh, i have assumed you want to use exodus because you have said something about sweeping into exodus.

Usually it should work with every wallet.. Not sure why it doesn't work with the atomic wallet 




No, because you have received more than 1 transaction.
Most wallets do generate a new address (which also means a new private key) for each receiving transaction.

This is done for privacy reasons. Someone from outside can't link your two addresses together (if you don't use both of them in one transaction).




If you had all of your BTC 'on' one address prior to the fork, then yes.
If you had your BTC spread between 2 addresses, you need to import those 2 corresponding private keys to see all of your BCC.

Basically, each address which contained BTC at the forkdate results in one address containing BCC.
And each address needs one private key.

But it shouldn't say 'invalid key' at all.
Sorry I confused you./ 

I have an ATOMIC WALLET  When I tried to import the keys (only tried 2 on the lines)  it said "Not a valid Key" on ATOMIC.


Even if there are no funds there, importing shouldn't be a problem.
In fact, usually you can import all private keys and the wallet shows which address contains a balance.


Just to make sure.. your private keys start with 5.. and are 51 characters long, correct ?
Yes. all keys listed start with 5K and 5J

I do have an EXODUS wallet someplace here...  Let me try that.  I will post a follow up.

Question:  Because I restored my wallet a couple times... Is this why I have more than 1 key listed? 
Would I assume ALL BCC would be contained in one of the listed keys?

Back to Exodus.

Yes, these are your private keys.




The private key which belongs to the address which had BTC stored prior to the forkdate 'contains' your BCC.
But it shouldn't say 'invalid key' at all.

Even if there are no funds there, importing shouldn't be a problem.
In fact, usually you can import all private keys and the wallet shows which address contains a balance.


Just to make sure.. your private keys start with 5.. and are 51 characters long, correct ?

---

Edit:
How did you actually try to import the private key ?

Exodus seems to not support importing private keys, but sweeping them (which means that exodus will take your private key and generate a transaction to an address from your exodus wallet). Effectively this is the same (difference: costs transaction fee + can be recovered using exodus mnemonic code).

To sweep a private key in exodus: Select Developer > Assets > Bitcoin Cash > Move Funds

Is this what you have tried ?

Thanks,

So my wallet has 1 address .  It has been "restored" since the fork, but all BTC was in before fork.

Did you properly copy the private keys and did you tick 'Private Key (Plain Base 58)' ?
You don't need to include the address or unused addresses. Only the private keys.

Yes I did. select it to PB58

It will show a series of keys.  These are private keys right?  Not addresses...?

Are you suggesting that these in fact are keys. One of the keys will contain my BCC if it import that to a BCC wallet?
I say that because I imported the top 2 and the new wallet said invalid keys. Should I keep truing all of them until I hit a home run?

Sorry, if I sound confused.   I just want to determine my private key to import to another wallet.  I have removed all BTC successfully.

Because a wallet is a software which manages your private-/public- keypairs.
Each address has its own private key.

That's how bitcoin works. I'd suggest you read a bit into how BTC works. A lot of people assume wrong things and make mistakes which leads to a loss of funds.




All which contained a balance prior to the fork date.




Did you properly copy the private keys and did you tick 'Private Key (Plain Base 58)' ?
You don't need to include the address or unused addresses. Only the private keys.

HPC....
Thanks for that.
If you find this.

I was able to back up wallet and open to find keys as you show in your pic.

I got there.
There were about 6 or 8 rows of keys.

But why so many lines of keys?  I only had 1 wallet.
Also which one do I select to import to BCC wallet?

I have tried the top 3 keys (rows) but I get message on other end saying "invalid key"
I did take out the spaces too.

Or will only one of those work.

Thanks

Excellent that you followed through and posted an update (with details) on how you recovered your wallet!

As for getting your private keys to claim forks... you can follow the little mini guide (with pics! ) that I posted for another user who was also trying to export private keys so they could get BCH.

You can find it here: https://bitcointalksearch.org/topic/m.34442580

Good News!!!
I finished the process of resetting my passphrase.
Thanks for the help with this newbie.

Also here is a great video on the subject.
https://www.youtube.com/watch?v=5et2BfLzEHs

Take these steps.
1) Make sure you have latest version of Armory
2) Make sure you have latest version of Bitcoin Core
3) remove older versions from your computer.

4) Run Bitcoin Core first. Finish load blockchain complete.
5) Now open and run Armory with Bitcoin Core running in background (dont close it)

6) Let Armory load the blockchain and complete.
    If Armory kicks out... Click Rescan data / Data base.  Just start over again.  It would stop at 99% / 1 second left a few times for me.
But keep trying.
Tip: Make sure it is in offline mode.  When it is 100% complete it will go online by itself.  If it says offline no node... close Armory and wait a few minute and restart Armory.

7) So after everything is 100%  you will need to change your passphrase to do anything.

To Change Passphrase you must now restore your wallet.  You will need your long root key. That will be on your paper print out. 2 lines.
  Click restore wallet
9) enter your root key
10) Click restore
11) A window will pop up and now you will enter a NEW PASSWORD. Write it down!!!
12) Enter it a third time to be sure in new pop up window.

Now your wallet is synching to RESTORED WALLET
Now you have your passphrase that you will need to move coins out.


Thanks again guys.  Now I have to make a new post to find out exactly I find my private keys after I emtied my wall of Bitcoin.  I need the keys to claim my BITCOIN CASH.   I need to "sweep" the keys out to a BCC wallet or exchange to claim prefork coins/

Many thanks,
I will post a follow up .  Thank you so much!

Your BTC (and your forkcoins) are assigned to your public keys (which need the corresponding private keys to be spent).

No coins are stored directly 'in your wallet'. All coins are assigned to your public key in the blockchain. And your wallet does manage the private keys.


So, to answer your question: No, it will not affect anything. After restoring with the root key, your wallet will hold the same private keys again.