Armory - Discussion Thread

[wachtwoord]

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

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 )

[1714136869]

1714136869

[1714136869]

1714136869

[1714136869]

1714136869

[1714136869]

1714136869

[1714136869]

1714136869

[cypherdoc]

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

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 )

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.

[winnetou]

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 ). 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]

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 ). 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. 

[ciore]

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]

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).

[winnetou]

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 ). 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]

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 ). 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!

[winnetou]

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 ). 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 Thx!

[etotheipi]

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 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!

[ciore]

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!!

[etotheipi]

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

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?

[etotheipi]

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

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.

[etotheipi]

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. 

[etotheipi]

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.  

So I put a tail on the log and the only issue that it took like 2 hours after importing the paper wallet to read the blockchain and I just sent 1 btc to your bounty for the Mac OSX with no issues, guess the wallet was corrupted.

Ugh!  Have you used a lot of addresses in that wallet?  I forgot that I recently added an "extended" search for restored wallets, to guarantee that it searches out far enough in your address list.  If you have used a lot of addresses, I could see it doing quite a few scans....

Glad it works now, though...

[coqui33]

Is this the right place to post suggested future features? Could Armory someday be made to access the bitcoin-d node running on a different machine? As it turns out, my 24/7 bitcoin-d node runs on a computer with insufficient ram to run Armory (along with everything else). So I would like to run Armory on a different machine on the LAN. FYI, Andreas Schildbach's latest Android wallet does this.

[K1773R]

Is this the right place to post suggested future features? Could Armory someday be made to access the bitcoin-d node running on a different machine? As it turns out, my 24/7 bitcoin-d node runs on a computer with insufficient ram to run Armory (along with everything else). So I would like to run Armory on a different machine on the LAN. FYI, Andreas Schildbach's latest Android wallet does this.

this already works (i do it myself), atleast the network thingy.
i mount the .armory directory with NFS onto the local machine and forward the local bitcoind ports to the others machine with socat (nc works too).

[coqui33]

Thank you. My fault. I should have been clearer. I use Windows, not linux.

[etotheipi]

Sorry coqui33,

This is not currently possible, because Armory depends on having access to the blk*.dat files in the Bitcoin-Qt/bitcoind home directory.  In the future (hopefully near future), this will be possible, as I start maintaining my own database of blockchain data.  However, bear in mind that Armory is very dumb when it comes to networking... it can compute the longest chain, but that's its only defense.  So you will have to select a trusted node.  I recognize you are planning to do that, it's just a warning.

However, before then, the RAM usage will probably come down considerably, so it may not be needed in your case.


Good news!  24 hours and 24 BTC, and it looks like we may have an OSX installer for Armory soon!  It turns out, all it took was some advertising on reddit -- someone had basically already packaged it up for his own use.   I wish I'd known it was that easy, I wouldn't have been dreading it for months!

[bit365]

Another feature request: ability to enter/edit comment on the View Details/Transaction Info popup.