Bitcoin Forum
May 23, 2024, 11:43:41 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 [6] 7 8 »  All
  Print  
Author Topic: Armory 0.96.3 released  (Read 15550 times)
alomar
Member
**
Offline Offline

Activity: 178
Merit: 10


View Profile
March 07, 2018, 04:59:29 PM
Last edit: March 07, 2018, 05:12:53 PM by alomar
 #101


there must be a bug somewhere.  

as you can see in the same section in my wallet, there is no Imported Addresses category nor the Remove Import Address command over on the right (which is expected if Armory isn't detecting an imported address, i guess):  

https://i.imgur.com/C9mNWEs.png

yet, when i open Coin Control, i plainly see the imported address with it's balance.

using 0.96.3.992 in expert mode
goatpig (OP)
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1347

Armory Developer


View Profile
March 07, 2018, 05:15:52 PM
 #102

How did you restore this wallet?

alomar
Member
**
Offline Offline

Activity: 178
Merit: 10


View Profile
March 07, 2018, 05:43:57 PM
 #103

How did you restore this wallet?

i described it above
goatpig (OP)
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1347

Armory Developer


View Profile
March 08, 2018, 09:34:44 AM
 #104

I need more detail. What was the state of your offline instance when you restored? Was this particular wallet there?

EDIT: did you cycle the .lmdb mirror wallet file?

PhoenixFire
Member
**
Offline Offline

Activity: 270
Merit: 36


View Profile
March 08, 2018, 03:46:17 PM
Last edit: March 08, 2018, 05:47:57 PM by PhoenixFire
 #105


there must be a bug somewhere.  

as you can see in the same section in my wallet, there is no Imported Addresses category nor the Remove Import Address command over on the right (which is expected if Armory isn't detecting an imported address, i guess):  

https://i.imgur.com/C9mNWEs.png

yet, when i open Coin Control, i plainly see the imported address with it's balance.

using 0.96.3.992 in expert mode
As far as I know, the option doesn't appear for a watch only wallet. Is that the case here?
Scratch that, missed some info. Strange issue!
alomar
Member
**
Offline Offline

Activity: 178
Merit: 10


View Profile
March 10, 2018, 05:12:10 PM
 #106

I need more detail. What was the state of your offline instance when you restored? Was this particular wallet there?

EDIT: did you cycle the .lmdb mirror wallet file?

no, Armory offline was devoid of any and all wallets prior to the restore. 

after signing, i always delete/remove the wallet in the GUI, nothing more.
goatpig (OP)
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1347

Armory Developer


View Profile
March 10, 2018, 09:36:01 PM
 #107

after signing, i always delete/remove the wallet in the GUI, nothing more.

On the online side?

alomar
Member
**
Offline Offline

Activity: 178
Merit: 10


View Profile
March 11, 2018, 05:07:56 PM
Last edit: March 11, 2018, 05:21:35 PM by alomar
 #108

after signing, i always delete/remove the wallet in the GUI, nothing more.

On the online side?

same thing.  deleted online wallet first before importing new restored WO wallet.  Armory even labels it as a "Restored" wallet in the description.  again, the bizarre thing is that when i open Wallet Properties, the imported key is NOT listed nor is the "Imported Key" key category even displayed, as i showed in that screenshot above.  but i still see it in Coin Control with a balance.  i can even construct a tx with it.  but it won't sign on the offline wallet b/c the imported private key has been successfully deleted on that pc.
goatpig (OP)
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1347

Armory Developer


View Profile
March 11, 2018, 06:51:00 PM
 #109

What I am asking is whether you delete the .lmdb mirror wallet files in the Armory datadir at all.

alomar
Member
**
Offline Offline

Activity: 178
Merit: 10


View Profile
March 12, 2018, 02:05:33 AM
 #110

What I am asking is whether you delete the .lmdb mirror wallet files in the Armory datadir at all.

no, why?  what does that do?
goatpig (OP)
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1347

Armory Developer


View Profile
March 12, 2018, 02:26:08 AM
 #111

What I am asking is whether you delete the .lmdb mirror wallet files in the Armory datadir at all.

no, why?  what does that do?

It's a watching only copy of your wallet used to interface with the DB. This most likely still has the imported public key in it, which is why the DB returns those UTXO in coin control.

alomar
Member
**
Offline Offline

Activity: 178
Merit: 10


View Profile
March 12, 2018, 06:35:01 PM
 #112

What I am asking is whether you delete the .lmdb mirror wallet files in the Armory datadir at all.

no, why?  what does that do?

It's a watching only copy of your wallet used to interface with the DB. This most likely still has the imported public key in it, which is why the DB returns those UTXO in coin control.

looking inside user@Ubuntu:~/.armory$ , i see these wallets:

armory_IekLiRmn_wallet.lmdb
armory_IekLiRmn_wallet.lmdb-lock

but those ID's numbers don't match the imported WO wallet ID number that has the imported private key.
goatpig (OP)
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1347

Armory Developer


View Profile
March 12, 2018, 09:45:40 PM
 #113

These are the one. The .lmdb wallets do not carry the same file ID cause the ID is built differently. You can nuke any .lmdb (and lock files) file with anything prior to 0.97 (this is to future proof this comment) as they are built on the fly WO copies of the python wallets.

alomar
Member
**
Offline Offline

Activity: 178
Merit: 10


View Profile
March 12, 2018, 10:22:43 PM
 #114

These are the one. The .lmdb wallets do not carry the same file ID cause the ID is built differently. You can nuke any .lmdb (and lock files) file with anything prior to 0.97 (this is to future proof this comment) as they are built on the fly WO copies of the python wallets.

ok, that killed it.  thanks.
Ente
Legendary
*
Offline Offline

Activity: 2126
Merit: 1001



View Profile
April 12, 2018, 10:23:37 PM
 #115

I imported a new address in 0.96.3, scanning hangs close to finished:

ArmoryDB:
Quote
(BlockchainScanner.cpp:852) scanned from block #514744 to #515526

ArmoryQt:
Quote
-ERROR - �Q��o: (BinaryData.h:563) odd hexit count
-ERROR - �Q��o: (SwigClient.cpp:61) odd hexit count

I restarted both a few times, always the same. Around half an hour scanning, then it hangs in Qt, and wouldn't show a time estimate any more after restarting Qt.

Well, first time I have a computer problem where I literally find noone with the same problem before, yay! :-)

Ente
goatpig (OP)
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1347

Armory Developer


View Profile
April 13, 2018, 06:58:21 AM
 #116

I imported a new address in 0.96.3, scanning hangs close to finished:

Have you tried with 0.96.4?

Ente
Legendary
*
Offline Offline

Activity: 2126
Merit: 1001



View Profile
April 13, 2018, 08:43:09 AM
 #117

I imported a new address in 0.96.3, scanning hangs close to finished:

Have you tried with 0.96.4?

Not yet, as it's an RC.
If you have no other suggestions, I'll upgrade and recheck.

Ente
goatpig (OP)
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1347

Armory Developer


View Profile
April 13, 2018, 08:49:30 AM
 #118

I've tagged 0.96.4, there just aren't builds for it yet.

Ente
Legendary
*
Offline Offline

Activity: 2126
Merit: 1001



View Profile
April 13, 2018, 11:54:13 PM
 #119

Ah, neat!
I upgraded both ArmoryDB and ArmoryQt to 0.96.4, still the exact same messages and scanning never finishes..

Ente
alomar
Member
**
Offline Offline

Activity: 178
Merit: 10


View Profile
April 14, 2018, 01:09:09 AM
 #120

i also tried building from the 0.96.4 source but run into this error upon "make":

Code:
user@user-VirtualBox:~/Downloads/BitcoinArmory-0.96.4$ make
Making all in cppForSwig
make[1]: Entering directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig'
Making all in lmdb
make[2]: Entering directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig/lmdb'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig/lmdb'
Making all in fcgi
make[2]: Entering directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig/fcgi'
make[2]: *** No rule to make target 'all'.  Stop.
make[2]: Leaving directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig/fcgi'
Makefile:1538: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig'
Makefile:413: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
Pages: « 1 2 3 4 5 [6] 7 8 »  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!