Bitcoin Forum
December 09, 2016, 03:58:46 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 [96] 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 ... 232 »
  Print  
Author Topic: Armory - Discussion Thread  (Read 482281 times)
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
March 09, 2013, 12:07:35 AM
 #1901

I've written the paper backup on notes by hand (I don't own a printer) and haven't noted the version of the wallet. It this a necessity?

So far, 1.35 is the only wallet version that has ever existed.  And 2.0 will be the next, and hopefully final one.  I expect that there will be a drop-down list to select the version -- given that paper backup information will look dramatically different for each version, it should be clear which version you used, just by the entry fields that show up when you select 1.35.


Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
1481299126
Hero Member
*
Offline Offline

Posts: 1481299126

View Profile Personal Message (Offline)

Ignore
1481299126
Reply with quote  #2

1481299126
Report to moderator
1481299126
Hero Member
*
Offline Offline

Posts: 1481299126

View Profile Personal Message (Offline)

Ignore
1481299126
Reply with quote  #2

1481299126
Report to moderator
1481299126
Hero Member
*
Offline Offline

Posts: 1481299126

View Profile Personal Message (Offline)

Ignore
1481299126
Reply with quote  #2

1481299126
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481299126
Hero Member
*
Offline Offline

Posts: 1481299126

View Profile Personal Message (Offline)

Ignore
1481299126
Reply with quote  #2

1481299126
Report to moderator
1481299126
Hero Member
*
Offline Offline

Posts: 1481299126

View Profile Personal Message (Offline)

Ignore
1481299126
Reply with quote  #2

1481299126
Report to moderator
cypherdoc
Legendary
*
Offline Offline

Activity: 1764



View Profile
March 09, 2013, 12:15:53 AM
 #1902

Okay I understand your intention Smiley

Two more question Smiley ->
- When my armory wallet is encrypted, is the paper wallet encrypted too?
- Do I have to worry that the wallet format of the paper wallet is no more supported in x years !?

I really love your client and hope you won't stop the development someday!

Paper backups are never encrypted.  Part of the reason is to guarantee that you have a useful backup in X years when you need it -- and most people would forget the encryption passphrase by then and it would be like not having a backup at all.

The paper backup displays the "Wallet Version", which is all you need to know.  Even though I'm making a new wallet version now, I will still support the old one.  Even in 10 years, any prior version of Armory that ever worked will let you recover the wallet and print off a list of all your private keys.   Either way, the code to create the private keys from your paper backup should be a permanent part of Armory, even if Armory doesn't produce those wallets anymore, but because I promised you it would still work 10 years from now Smiley

I've written the paper backup on notes by hand (I don't own a printer) and haven't noted the version of the wallet. It this a necessity?

that's a good thing.  ink rollers can't be stolen!

just make sure you can distinguish between 0OIl's.
wachtwoord
Legendary
*
Offline Offline

Activity: 1498



View Profile WWW
March 09, 2013, 12:16:01 AM
 #1903

that's a good thing.  ink rollers can't be stolen!

just make sure you can distinguish between 0OIl's.

etotheipi is smart and only used lowercase letters Smiley

Also, thanks for the answer, I already split my paper wallet in two to be able to have it on me at all times and not be recognizable as a wallet. (Don't want to lose my coins if my house burns down Wink)

cypherdoc
Legendary
*
Offline Offline

Activity: 1764



View Profile
March 09, 2013, 12:17:44 AM
 #1904

that's a good thing.  ink rollers can't be stolen!

just make sure you can distinguish between 0OIl's.

etotheipi is smart and only used lowercase letters Smiley

Also, thanks for the answer, I already split my paper wallet in two to be able to have it on me at all times and not be recognizable as a wallet. (Don't want to lose my coins if my house burns down Wink)

still, check it out to make sure you can restore wallet from handwritten letters.  i tried it a few times and i couldn't recognize my own printing for some letters!  given how many there are with overlaps its not easy to figure out which combination might be right.
wachtwoord
Legendary
*
Offline Offline

Activity: 1498



View Profile WWW
March 09, 2013, 12:22:28 AM
 #1905

I have deleted and restored my wallet from one of my two handwritten paper backups three times before sending anything more than 0.1 BTC to it. But you are right. Be careful.

I'm also thinking of memorizing or encoding the paper backup. It's just a little long Tongue

winnetou
Sr. Member
****
Offline Offline

Activity: 361


View Profile
March 09, 2013, 09:42:02 AM
 #1906

Bug report:
I just created my first paper wallet and tried to import it after printing it out on an offline machine (so I used the Armory Offline Client Wink). I clicked "Restore from paper wallet" and typed in all the letters, I checked it three times for mistakes. After I clicked the OK button it  happened nothing (Tried it with checked and unchecked "Encrypt wallet" checkbox.). I clicked one more time OK and the app gave me no feedback beside of the visual button click effect. Armory did not crash, I was able to click cancel and go back to the main window.

Can it be that this did not work because my wallet was already imported? If yes I would expect a msg like "This wallet is already imported". Then I would also know that the import has worked and would not have to remove the wallet first, import and encrypt it again to ensure the functioning of my paper wallet and the import function)

Armory version: 0.8.63
OS: Ubuntu 10.04 32bit
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
March 09, 2013, 02:07:55 PM
 #1907

Bug report:
I just created my first paper wallet and tried to import it after printing it out on an offline machine (so I used the Armory Offline Client Wink). I clicked "Restore from paper wallet" and typed in all the letters, I checked it three times for mistakes. After I clicked the OK button it  happened nothing (Tried it with checked and unchecked "Encrypt wallet" checkbox.). I clicked one more time OK and the app gave me no feedback beside of the visual button click effect. Armory did not crash, I was able to click cancel and go back to the main window.

Can it be that this did not work because my wallet was already imported? If yes I would expect a msg like "This wallet is already imported". Then I would also know that the import has worked and would not have to remove the wallet first, import and encrypt it again to ensure the functioning of my paper wallet and the import function)

Armory version: 0.8.63
OS: Ubuntu 10.04 32bit

You should've gotten a message like you suggested.  I have billions of catches like that...

Can you go check the /home/username/.armory/armorylog.txt file on that computer and look for some useful information.  I know you can't send it to me from the offline computer, but the error message would be fine.  Usually when a button is supposed to do something, but doesn't do anything, there's usually errors kicking around under the hood. 

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
ciore
Newbie
*
Offline Offline

Activity: 9


View Profile
March 09, 2013, 04:31:54 PM
 #1908

Hi,
I'm using bitcoin-Qt client with a datadir different from the system default; I've just installed Armory, It is connected but the block number count is stuck at the size of the blockchain in the system default Bitcoin-Qt data directory.
How cain I make Armory read from the updated blockchain?
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
March 09, 2013, 04:46:55 PM
 #1909

Hi,
I'm using bitcoin-Qt client with a datadir different from the system default; I've just installed Armory, It is connected but the block number count is stuck at the size of the blockchain in the system default Bitcoin-Qt data directory.
How cain I make Armory read from the updated blockchain?

You can start Armory using the "--satoshi-datadir=/path/to/it" when you start Armory.  If it's windows, just right-click the desktop icon for Armory and select properties, then add it to the end of the "Target:" line (with a space between the existing command and this one).

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
winnetou
Sr. Member
****
Offline Offline

Activity: 361


View Profile
March 09, 2013, 04:50:54 PM
 #1910

Bug report:
I just created my first paper wallet and tried to import it after printing it out on an offline machine (so I used the Armory Offline Client Wink). I clicked "Restore from paper wallet" and typed in all the letters, I checked it three times for mistakes. After I clicked the OK button it  happened nothing (Tried it with checked and unchecked "Encrypt wallet" checkbox.). I clicked one more time OK and the app gave me no feedback beside of the visual button click effect. Armory did not crash, I was able to click cancel and go back to the main window.

Can it be that this did not work because my wallet was already imported? If yes I would expect a msg like "This wallet is already imported". Then I would also know that the import has worked and would not have to remove the wallet first, import and encrypt it again to ensure the functioning of my paper wallet and the import function)

Armory version: 0.8.63
OS: Ubuntu 10.04 32bit

You should've gotten a message like you suggested.  I have billions of catches like that...

Can you go check the /home/username/.armory/armorylog.txt file on that computer and look for some useful information.  I know you can't send it to me from the offline computer, but the error message would be fine.  Usually when a button is supposed to do something, but doesn't do anything, there's usually errors kicking around under the hood.  

Here we go. This must it be:

2013-03-09 10:35 (ERROR) -- Traceback (most recent call last):
  File "/usr/share/armory/qtdialogs.py", line 3706, in verifyUserInput
    rawBin = easyType16_to_binary( str(self.lineEdits.text()).replace(' ','') )
  File "/usr/share/armory/qtdialogs.py", line 3872, in easyType16_to_binary
    return hex_to_binary(''.join([base16_to_hex_map[c] for c in b16str]))
  File "/usr/share/armory/armoryengine.py", line 897, in hex_to_binary
    return bout.decode('hex_codec')
  File "/usr/lib/python2.6/encodings/hex_codec.py", line 42, in hex_decode
    output = binascii.a2b_hex(input)
TypeError: Odd-length string
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
March 09, 2013, 04:53:43 PM
 #1911

Bug report:
I just created my first paper wallet and tried to import it after printing it out on an offline machine (so I used the Armory Offline Client Wink). I clicked "Restore from paper wallet" and typed in all the letters, I checked it three times for mistakes. After I clicked the OK button it  happened nothing (Tried it with checked and unchecked "Encrypt wallet" checkbox.). I clicked one more time OK and the app gave me no feedback beside of the visual button click effect. Armory did not crash, I was able to click cancel and go back to the main window.

Can it be that this did not work because my wallet was already imported? If yes I would expect a msg like "This wallet is already imported". Then I would also know that the import has worked and would not have to remove the wallet first, import and encrypt it again to ensure the functioning of my paper wallet and the import function)

Armory version: 0.8.63
OS: Ubuntu 10.04 32bit

You should've gotten a message like you suggested.  I have billions of catches like that...

Can you go check the /home/username/.armory/armorylog.txt file on that computer and look for some useful information.  I know you can't send it to me from the offline computer, but the error message would be fine.  Usually when a button is supposed to do something, but doesn't do anything, there's usually errors kicking around under the hood.  

Here we go. This must it be:

2013-03-09 10:35 (ERROR) -- Traceback (most recent call last):
  File "/usr/share/armory/qtdialogs.py", line 3706, in verifyUserInput
    rawBin = easyType16_to_binary( str(self.lineEdits.text()).replace(' ','') )
  File "/usr/share/armory/qtdialogs.py", line 3872, in easyType16_to_binary
    return hex_to_binary(''.join([base16_to_hex_map[c] for c in b16str]))
  File "/usr/share/armory/armoryengine.py", line 897, in hex_to_binary
    return bout.decode('hex_codec')
  File "/usr/lib/python2.6/encodings/hex_codec.py", line 42, in hex_decode
    output = binascii.a2b_hex(input)
TypeError: Odd-length string

It looks like you are missing some characters in the typed field.  I guess I only catch errors in the typed letters, not missing letters.  I'll add a condition to catch that...

When you have typed enough letters, it should automatically respace the chars for you into blocks of 4 letters.  There's a total of 9 blocks on each line, so 36 letters.  If you don't have that.... let me know!

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
winnetou
Sr. Member
****
Offline Offline

Activity: 361


View Profile
March 09, 2013, 05:04:23 PM
 #1912

Bug report:
I just created my first paper wallet and tried to import it after printing it out on an offline machine (so I used the Armory Offline Client Wink). I clicked "Restore from paper wallet" and typed in all the letters, I checked it three times for mistakes. After I clicked the OK button it  happened nothing (Tried it with checked and unchecked "Encrypt wallet" checkbox.). I clicked one more time OK and the app gave me no feedback beside of the visual button click effect. Armory did not crash, I was able to click cancel and go back to the main window.

Can it be that this did not work because my wallet was already imported? If yes I would expect a msg like "This wallet is already imported". Then I would also know that the import has worked and would not have to remove the wallet first, import and encrypt it again to ensure the functioning of my paper wallet and the import function)

Armory version: 0.8.63
OS: Ubuntu 10.04 32bit

You should've gotten a message like you suggested.  I have billions of catches like that...

Can you go check the /home/username/.armory/armorylog.txt file on that computer and look for some useful information.  I know you can't send it to me from the offline computer, but the error message would be fine.  Usually when a button is supposed to do something, but doesn't do anything, there's usually errors kicking around under the hood.  

Here we go. This must it be:

2013-03-09 10:35 (ERROR) -- Traceback (most recent call last):
  File "/usr/share/armory/qtdialogs.py", line 3706, in verifyUserInput
    rawBin = easyType16_to_binary( str(self.lineEdits.text()).replace(' ','') )
  File "/usr/share/armory/qtdialogs.py", line 3872, in easyType16_to_binary
    return hex_to_binary(''.join([base16_to_hex_map[c] for c in b16str]))
  File "/usr/share/armory/armoryengine.py", line 897, in hex_to_binary
    return bout.decode('hex_codec')
  File "/usr/lib/python2.6/encodings/hex_codec.py", line 42, in hex_decode
    output = binascii.a2b_hex(input)
TypeError: Odd-length string

It looks like you are missing some characters in the typed field.  I guess I only catch errors in the typed letters, not missing letters.  I'll add a condition to catch that...

When you have typed enough letters, it should automatically respace the chars for you into blocks of 4 letters.  There's a total of 9 blocks on each line, so 36 letters.  If you don't have that.... let me know!

MY FAULT! I really had a typo I guess. Now it worked fine and I got a nice msg that the wallet is already imported Smiley Thx!
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
March 09, 2013, 05:08:35 PM
 #1913

MY FAULT! I really had a typo I guess. Now it worked fine and I got a nice msg that the wallet is already imported Smiley Thx!

My fault, too:  that's not an unusual kind of user-error -- I should definitely catch that!  It's on my todo list for the next release!  Thanks!

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
ciore
Newbie
*
Offline Offline

Activity: 9


View Profile
March 09, 2013, 07:52:17 PM
 #1914

Hi,
I'm using bitcoin-Qt client with a datadir different from the system default; I've just installed Armory, It is connected but the block number count is stuck at the size of the blockchain in the system default Bitcoin-Qt data directory.
How cain I make Armory read from the updated blockchain?

You can start Armory using the "--satoshi-datadir=/path/to/it" when you start Armory.  If it's windows, just right-click the desktop icon for Armory and select properties, then add it to the end of the "Target:" line (with a space between the existing command and this one).


Thanks e^ip!!
Armory is very powerfull!!
gweedo
Legendary
*
Offline Offline

Activity: 1246


Java, PHP, HTML/CSS Programmer for Hire!


View Profile WWW
March 09, 2013, 11:39:08 PM
 #1915

So when I am sending coins from any one of my wallets, Sometimes I have to keep hitting the unlock password button until it will actually send the coins. Then I looked in the error log and saw this
Code:
2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (INFO) -- qtdialogs.py:5379 - Change address behavior: Feedback
2013-03-09 18:29 (INFO) -- qtdialogs.py:5379 - Change address behavior: Feedback
2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

My version
Code:
2013-03-09 18:15 (INFO) -- armoryengine.py:571 -    Armory Version        : 0.87
2013-03-09 18:15 (INFO) -- armoryengine.py:572 -    PyBtcWallet  Version  : 1.35
2013-03-09 18:15 (INFO) -- armoryengine.py:573 - Detected Operating system: Mac/OSX

Want to earn 2500 SATOSHIS per hour? Come Chat and Chill in https://goseemybits.com/lobby
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
March 09, 2013, 11:51:27 PM
 #1916

So when I am sending coins from any one of my wallets, Sometimes I have to keep hitting the unlock password button until it will actually send the coins. Then I looked in the error log and saw this
Code:
2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (INFO) -- qtdialogs.py:5379 - Change address behavior: Feedback
2013-03-09 18:29 (INFO) -- qtdialogs.py:5379 - Change address behavior: Feedback
2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

My version
Code:
2013-03-09 18:15 (INFO) -- armoryengine.py:571 -    Armory Version        : 0.87
2013-03-09 18:15 (INFO) -- armoryengine.py:572 -    PyBtcWallet  Version  : 1.35
2013-03-09 18:15 (INFO) -- armoryengine.py:573 - Detected Operating system: Mac/OSX

Ack!  That looks like a corrupted wallet!   The only time I remember seeing that is when I was messing with a wallet file and destroyed some data. 

Unfortunately, the error doesn't lead to a very agreeable way for me to investigate further (unless you want to send me your private keys and wallet file so I can check on it...).  Perhaps it got corrupted somehow on the way to being encrypted.  I have the app restore from the parallel backup when it detects an error in the wallet file, but that error cannot be detected until you try to unlock your wallet, which happens after the check Undecided

Do you have a paper or digital backup?  Can you try backing up the wallet manually (from your home directory), then remove it from Armory and restore from backup?   Then try again signing again.

Was there anything special about this wallet?  Was it originally restored from a paper backup?  From the new fragmented backup?  Do you know what version created it, or when you created it approximately?


Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
gweedo
Legendary
*
Offline Offline

Activity: 1246


Java, PHP, HTML/CSS Programmer for Hire!


View Profile WWW
March 10, 2013, 12:05:11 AM
 #1917

So when I am sending coins from any one of my wallets, Sometimes I have to keep hitting the unlock password button until it will actually send the coins. Then I looked in the error log and saw this
Code:
2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (INFO) -- qtdialogs.py:5379 - Change address behavior: Feedback
2013-03-09 18:29 (INFO) -- qtdialogs.py:5379 - Change address behavior: Feedback
2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

My version
Code:
2013-03-09 18:15 (INFO) -- armoryengine.py:571 -    Armory Version        : 0.87
2013-03-09 18:15 (INFO) -- armoryengine.py:572 -    PyBtcWallet  Version  : 1.35
2013-03-09 18:15 (INFO) -- armoryengine.py:573 - Detected Operating system: Mac/OSX

Ack!  That looks like a corrupted wallet!   The only time I remember seeing that is when I was messing with a wallet file and destroyed some data. 

Unfortunately, the error doesn't lead to a very agreeable way for me to investigate further (unless you want to send me your private keys and wallet file so I can check on it...).  Perhaps it got corrupted somehow on the way to being encrypted.  I have the app restore from the parallel backup when it detects an error in the wallet file, but that error cannot be detected until you try to unlock your wallet, which happens after the check Undecided

Do you have a paper or digital backup?  Can you try backing up the wallet manually (from your home directory), then remove it from Armory and restore from backup?   Then try again signing again.

Was there anything special about this wallet?  Was it originally restored from a paper backup?  From the new fragmented backup?  Do you know what version created it, or when you created it approximately?

It was created in 0.85 and I can send funds from the wallet, but I have keep click unlock until it takes sends the transaction, I do have a paper back, it all works fine. Should I do a digital back up, and try and restore from that? Should I create a new Wallet?

Want to earn 2500 SATOSHIS per hour? Come Chat and Chill in https://goseemybits.com/lobby
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
March 10, 2013, 01:56:36 AM
 #1918

So when I am sending coins from any one of my wallets, Sometimes I have to keep hitting the unlock password button until it will actually send the coins. Then I looked in the error log and saw this
Code:
2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (INFO) -- qtdialogs.py:5379 - Change address behavior: Feedback
2013-03-09 18:29 (INFO) -- qtdialogs.py:5379 - Change address behavior: Feedback
2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

My version
Code:
2013-03-09 18:15 (INFO) -- armoryengine.py:571 -    Armory Version        : 0.87
2013-03-09 18:15 (INFO) -- armoryengine.py:572 -    PyBtcWallet  Version  : 1.35
2013-03-09 18:15 (INFO) -- armoryengine.py:573 - Detected Operating system: Mac/OSX

Ack!  That looks like a corrupted wallet!   The only time I remember seeing that is when I was messing with a wallet file and destroyed some data. 

Unfortunately, the error doesn't lead to a very agreeable way for me to investigate further (unless you want to send me your private keys and wallet file so I can check on it...).  Perhaps it got corrupted somehow on the way to being encrypted.  I have the app restore from the parallel backup when it detects an error in the wallet file, but that error cannot be detected until you try to unlock your wallet, which happens after the check Undecided

Do you have a paper or digital backup?  Can you try backing up the wallet manually (from your home directory), then remove it from Armory and restore from backup?   Then try again signing again.

Was there anything special about this wallet?  Was it originally restored from a paper backup?  From the new fragmented backup?  Do you know what version created it, or when you created it approximately?

It was created in 0.85 and I can send funds from the wallet, but I have keep click unlock until it takes sends the transaction, I do have a paper back, it all works fine. Should I do a digital back up, and try and restore from that? Should I create a new Wallet?

Wait... so it's not deterministic whether it accepts the passphrase?  How many attempts does it take?  I'm not sure why it would work ever, if it doesn't work the first time.  Perhaps only some of the keys are corrupted and it needs to be clicked once for each of them.

I recommend upgrading to the latest version (probably 0.87.3) and then restore from paper backup.  You can restore it directly to an encrypted file in the latest version.  After it rescans with the restored backup, try sending again.

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
gweedo
Legendary
*
Offline Offline

Activity: 1246


Java, PHP, HTML/CSS Programmer for Hire!


View Profile WWW
March 10, 2013, 02:06:51 AM
 #1919

So when I am sending coins from any one of my wallets, Sometimes I have to keep hitting the unlock password button until it will actually send the coins. Then I looked in the error log and saw this
Code:
2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:28 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2060, in unlock
    self.unlock(secureKdfOutput)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (INFO) -- qtdialogs.py:5379 - Change address behavior: Feedback
2013-03-09 18:29 (INFO) -- qtdialogs.py:5379 - Change address behavior: Feedback
2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

2013-03-09 18:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/qtdialogs.py", line 62, in acceptPassphrase
    self.wlt.unlock(securePassphrase=securePwd)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 8335, in unlock
    addrObj.unlock(self.kdfKey)
  File "/usr/local/Cellar/armory-qt/0.87-beta/share/armory/armoryengine.py", line 2091, in unlock
    raise KeyDataError, "Stored public key does not match priv key!"
KeyDataError: Stored public key does not match priv key!

My version
Code:
2013-03-09 18:15 (INFO) -- armoryengine.py:571 -    Armory Version        : 0.87
2013-03-09 18:15 (INFO) -- armoryengine.py:572 -    PyBtcWallet  Version  : 1.35
2013-03-09 18:15 (INFO) -- armoryengine.py:573 - Detected Operating system: Mac/OSX

Ack!  That looks like a corrupted wallet!   The only time I remember seeing that is when I was messing with a wallet file and destroyed some data. 

Unfortunately, the error doesn't lead to a very agreeable way for me to investigate further (unless you want to send me your private keys and wallet file so I can check on it...).  Perhaps it got corrupted somehow on the way to being encrypted.  I have the app restore from the parallel backup when it detects an error in the wallet file, but that error cannot be detected until you try to unlock your wallet, which happens after the check Undecided

Do you have a paper or digital backup?  Can you try backing up the wallet manually (from your home directory), then remove it from Armory and restore from backup?   Then try again signing again.

Was there anything special about this wallet?  Was it originally restored from a paper backup?  From the new fragmented backup?  Do you know what version created it, or when you created it approximately?

It was created in 0.85 and I can send funds from the wallet, but I have keep click unlock until it takes sends the transaction, I do have a paper back, it all works fine. Should I do a digital back up, and try and restore from that? Should I create a new Wallet?

Wait... so it's not deterministic whether it accepts the passphrase?  How many attempts does it take?  I'm not sure why it would work ever, if it doesn't work the first time.  Perhaps only some of the keys are corrupted and it needs to be clicked once for each of them.

I recommend upgrading to the latest version (probably 0.87.3) and then restore from paper backup.  You can restore it directly to an encrypted file in the latest version.  After it rescans with the restored backup, try sending again.

Ok I will just restore it and it took like 5 or 6 clicks to unlock it. I am on a mac with https://github.com/WyseNynja/homebrew-bitcoin/blob/master/armory-qt.rb so I have to wait until that updates to 0.87.3

Want to earn 2500 SATOSHIS per hour? Come Chat and Chill in https://goseemybits.com/lobby
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
March 10, 2013, 02:57:58 AM
 #1920

Ok I will just restore it and it took like 5 or 6 clicks to unlock it. I am on a mac with https://github.com/WyseNynja/homebrew-bitcoin/blob/master/armory-qt.rb so I have to wait until that updates to 0.87.3

0.87.3 shouldn't behave any different in this regard, compared to 0.87.

So wait, you did restore it?  Your wording was awkward...

If you restored from paper backup and it still has unlocking problems... I'll have to think about that one...

You could also try going to Help-->Revert All Settings.  I doubt that would do it, but who knows.  Also, make sure the wallet is removed from your .armory directory before you restore from paper backup. 

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
Pages: « 1 ... 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 [96] 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 ... 232 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!