0.96.4 RC1

[goatpig]

everything worked like a charm.  thx goatpig!

how do i make the ccDlgGeometry line deletion persistent? 

Idk, it's some weird shit where the dialog appears minimized or out frame for whatever reason. I may just get rid of the damn geometry saving for this dialog if I can figure out what's going on.

[Mike Belg]

Dawm, struckelling all around at Christmasday..lol..


Situation: New Mac Air with Sierra 10.13.2, Bitcoin core V0.15.1 and Armory 0.96.3.99.

Bitcoin core went well bulding upend connecting, is now done with connecting.

Starting up Armory is the big issue....

package Armory will install, that aint the problem. but after that...

First start up Bitcoine core, then after that started Armory. No result. Just a few seconds the image of Armory blinking. Then its disappears, it won't start up.

I ve removed the program to another folder, didn't work.

Disabled Gatekeeper in terminal, didn't work.

dump:
Process:               Python [1151]
Path:                  /Applications/Armory 2.app/Contents/MacOS/Armory
Identifier:            com.armory.armory
Version:               Huh
Code Type:             X86-64 (Native)
Parent Process:        Huh [1]
Responsible:           Python [1151]
User ID:               501

Date/Time:             2017-12-25 22:24:44.333 +0100
OS Version:            Mac OS X 10.13.2 (17C88)
Report Version:        12
Anonymous UUID:        09F2F47F-BC4C-4A7D-387C-4C91029BC4AA

Sleep/Wake UUID:       E364B7A2-23AD-463F-88A5-48E12B87C69D

Time Awake Since Boot: 9700 seconds
Time Since Wake:       500 seconds

System Integrity Protection: enabled

Crashed Thread:        0

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    DYLD, [0x1] Library missing

Application Specific Information:
dyld: launch, loading dependent libraries
DYLD_FRAMEWORK_PATH=/Applications/Armory 2.app/Contents/MacOS/../Dependencies:/Applications/Armory 2.app/Contents/MacOS/../Frameworks
DYLD_LIBRARY_PATH=/Applications/Armory 2.app/Contents/MacOS/../Dependencies:/Applications/Armory 2.app/Contents/MacOS/../Frameworks

Dyld Error Message:
  Library not loaded: /usr/local/opt/openssl/lib/libssl.1.0.0.dylib
  Referenced from: /Applications/Armory 2.app/Contents/MacOS/Python
  Reason: image not found

Binary Images:
       0x100000000 -        0x100000fff +Python (Huh) <DE9F445E-AF87-3A6F-B171-EF96DCC5B5D1> /Applications/Armory 2.app/Contents/MacOS/Python
       0x10a62d000 -        0x10a67798f  dyld (519.2.2) <6695F30B-4E88-3C0B-9867-7D738C44A3E6> /usr/lib/dyld

Model: MacBookAir7,2, BootROM MBA71.0171.B00, 2 processors, Intel Core i5, 1,8 GHz, 8 GB, SMC 2.27f2
Graphics: Intel HD Graphics 6000, Intel HD Graphics 6000, Built-In
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x02FE, -
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x02FE, -
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x117), Broadcom BCM43xx 1.0 (7.77.37.5.1a3)
Bluetooth: Version 6.0.2f2, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM0512G, 500,28 GB
USB Device: USB 3.0 Bus
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Air, Apple Inc., 27.2

I did read all the treats so far I could find, but no solutions for. Are there more members with this problem?


Happy Christmas to all for you from Belgium!

[droark]

Dawm, struckelling all around at Christmasday..lol..

Read me.

[Mike Belg]

Ok, thanks showing me the way. The instructions didn't work for me, after searching  https://brew.sh/index_nl.html  worked well. I had also to replace armory to another map, then it worked! Pjieuw!

Many txs!

[droark]

Ok, thanks showing me the way. The instructions didn't work for me, after searching  https://brew.sh/index_nl.html  worked well. I had also to replace armory to another map, then it worked! Pjieuw!

Many txs!

What do you mean they didn't work? I'd like to know what exactly you did in case I need to update the directions.

[ConnyH]

So I installed this version of Armory in order to get the BCH signer so I could claim my BCH, but when I start Armory it just sits at "Preparing Databases" and nothing happens. I can't see my BTC balance and it says that Armory is offline in the bottom right corner.

The CPU is idling and no disk or wifi is being used, so I'm fairly confident it doesn't actually do anything. What can be the problem and what can I do to solve it?

EDIT: I first tried to install 0.96.3 but had the exact same problem.

EDIT2: I'm also using bitcoin core 0.13.1, should I update?

EDIT3: Looking at the logs, this is what is says:
"Log file opened at 23:30:55.000: C:\Users\Bla\AppData\Roaming/Armory/dbLog.txt
-INFO  - 23:30:55.000: (..\main.cpp:32) Running on 8 threads
-INFO  - 23:30:55.000: (..\main.cpp:33) Ram usage level: 50
-INFO  - 23:30:55.000: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:263) Listening on port 9001
-ERROR - 23:30:55.016: (..\BDM_Server.cpp:1270) There is already a process listening on 127.0.0.1:9001
-ERROR - 23:30:55.016: (..\BDM_Server.cpp:1272) ArmoryDB cannot start under these conditions. Shutting down!
-ERROR - 23:30:55.016: (..\BDM_Server.cpp:1273) Make sure to shutdown the conflicting processbefore trying again (most likely another ArmoryDB instance)."

[hornby]

EDIT2: I'm also using bitcoin core 0.13.1, should I update?

Hello ConnyH,

Bitcoin Core will never ever follow the BCH chain (no matter which version). Replace Bitcoin Core temporarily with Bitcoin ABC and let that work as backend to Armory. Then you will be getting there.

EDIT1: And then move your BCH funds to a new wallet you create in a wallet that intends to support the future hard forks of BCH (e.g. Bitcoin ABC). Goatpig has made it clear, that he will not support Altcoins in Armory other than moving your hard-fork funds out of Armory wallets.

[PhoenixFire]

EDIT3: Looking at the logs, this is what is says:
"Log file opened at 23:30:55.000: C:\Users\Bla\AppData\Roaming/Armory/dbLog.txt
-INFO  - 23:30:55.000: (..\main.cpp:32) Running on 8 threads
-INFO  - 23:30:55.000: (..\main.cpp:33) Ram usage level: 50
-INFO  - 23:30:55.000: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:263) Listening on port 9001
-ERROR - 23:30:55.016: (..\BDM_Server.cpp:1270) There is already a process listening on 127.0.0.1:9001
-ERROR - 23:30:55.016: (..\BDM_Server.cpp:1272) ArmoryDB cannot start under these conditions. Shutting down!
-ERROR - 23:30:55.016: (..\BDM_Server.cpp:1273) Make sure to shutdown the conflicting processbefore trying again (most likely another ArmoryDB instance)."

Have you set Armory to specifically use port 9001? Mine uses a random-ish high port each launch and I'm fairly sure that is the default.
Either way, something is listening on port 9001, and ArmoryDB is trying to use that port too. As it says, it could be another ArmoryDB process that you would need to kill, or another program entirely.
If it is ArmoryDB, it is possible that it is choking on a bad DB, depending on which version you upgraded from, which is usually resolved with a rebuild and rescan.

EDIT2: I'm also using bitcoin core 0.13.1, should I update?

Probably, yeah. I think Core will need to update the DB format so be prepared for that to take a little while.

Hello ConnyH,

Bitcoin Core will never ever follow the BCH chain (no matter which version). Replace Bitcoin Core temporarily with Bitcoin ABC and let that work as backend to Armory. Then you will be getting there.

EDIT1: And then move your BCH funds to a new wallet you create in a wallet that intends to support the future hard forks of BCH (e.g. Bitcoin ABC). Goatpig has made it clear, that he will not support Altcoins in Armory other than moving your hard-fork funds out of Armory wallets.

Depends on how they intend to split the BCH and the situation with UTXOs, but ABC isn't always required. All covered in the BCH thread, though.

[droark]

Bitcoin Core will never ever follow the BCH chain (no matter which version). Replace Bitcoin Core temporarily with Bitcoin ABC and let that work as backend to Armory. Then you will be getting there.

The user should read the guide to moving funds before proceeding. If nothing else, it'll tell them about pathing, which they'll need to worry about it they don't want Armory to be deeply confused whenever people switch between chains.

[ConnyH]

Hello ConnyH,

Bitcoin Core will never ever follow the BCH chain (no matter which version). Replace Bitcoin Core temporarily with Bitcoin ABC and let that work as backend to Armory. Then you will be getting there.

EDIT1: And then move your BCH funds to a new wallet you create in a wallet that intends to support the future hard forks of BCH (e.g. Bitcoin ABC). Goatpig has made it clear, that he will not support Altcoins in Armory other than moving your hard-fork funds out of Armory wallets.

Hi,
I’ve read the guide about claiming your BCH and if I understand it correctly I don’t need Bitcoin ABC, have I missunderstood the guide?
Thanks for your reply!
   

Have you set Armory to specifically use port 9001? Mine uses a random-ish high port each launch and I'm fairly sure that is the default.
Either way, something is listening on port 9001, and ArmoryDB is trying to use that port too. As it says, it could be another ArmoryDB process that you would need to kill, or another program entirely.
If it is ArmoryDB, it is possible that it is choking on a bad DB, depending on which version you upgraded from, which is usually resolved with a rebuild and rescan.
 

Nope, I haven’t set Armory to specifically use that port. I don’t even know how to set Armory to use a specific port. How do I set Armory to use another port?
I will try with a rebuild and rescan! I will also try to update Core.
Thanks for your reply!

The user should read the guide to moving funds before proceeding. If nothing else, it'll tell them about pathing, which they'll need to worry about it they don't want Armory to be deeply confused whenever people switch between chains.

I’ve read the thread, but the problem is that I’m very new to this (I've had bitcoins in an Armory wallet for a couple of years, but never really did anything with them), so I barely understood anything.
If I understood it correctly this is what I have to do:
1. Update Armory to a version that has the BCH signer
2. Delete some blocks to somehow see the BCH balance I had at the time at the fork.
3. Send all those funds to a ”real” BCH wallet using the BCH signer.
Have I understood it correctly or am I completely lost?
Thanks for your reply!

[droark]

I’ve read the guide about claiming your BCH and if I understand it correctly I don’t need Bitcoin ABC, have I missunderstood the guide?

Yes. You need Bitcoin ABC (or Bitcoin Unlimited, although it crashes a lot last I checked) in order to access your Bcash coins.

If I understood it correctly this is what I have to do:
1. Update Armory to a version that has the BCH signer
2. Delete some blocks to somehow see the BCH balance I had at the time at the fork.
3. Send all those funds to a ”real” BCH wallet using the BCH signer.

1)Yes.
2)Yes, by using ABC or Unlimited. You'll want to follow the guide and use alternate paths in order to not wreck your regular Bitcoin Core setup. I believe this is covered in the guide.
3)Yes, or to an exchange so that you can sell them.

[ConnyH]

I’ve read the guide about claiming your BCH and if I understand it correctly I don’t need Bitcoin ABC, have I missunderstood the guide?

Yes. You need Bitcoin ABC (or Bitcoin Unlimited, although it crashes a lot last I checked) in order to access your Bcash coins.

If I understood it correctly this is what I have to do:
1. Update Armory to a version that has the BCH signer
2. Delete some blocks to somehow see the BCH balance I had at the time at the fork.
3. Send all those funds to a ”real” BCH wallet using the BCH signer.

1)Yes.
2)Yes, by using ABC or Unlimited. You'll want to follow the guide and use alternate paths in order to not wreck your regular Bitcoin Core setup. I believe this is covered in the guide.
3)Yes, or to an exchange so that you can sell them.

Thanks for your fast reply!
I think I might understand a little bit more what I need to do now.
I'll install Bitcoin ABC on an external HDD and let that sync until it's done. Then I'll set my Armory path to that external harddrive. Do I still need to delete some blocks then? According to the BCH network (or whatever it's called) I have not spent any BCH since the fork (even though I've spent BTC since the fork)?
I still can't see my current BTC balance, but when I've solved that (I updated bitcoin core to the newest version, and it looks like it doesn't say anything about another process listening on that port, but it still won't let me see my current balance), would it be wise to first send my current BTC balance to another wallet so I don't fuck up, or is it literally completely impossible to fuck up? (I'm sorry if I'm being paranoid, but since I'm a student with very little money I would rather not accidentally lose my BTC)

I have one question about a line in the log file:
 "-INFO  - 09:44:27.000: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:263) Listening on port 9001"
I know goat is one of the developers of Armory, but is it trying to access his user or something? Because I of course don't have a user called goat on my computer.

And again, thanks for your reply!

[droark]

Thanks for your fast reply!
I think I might understand a little bit more what I need to do now.
I'll install Bitcoin ABC on an external HDD and let that sync until it's done. Then I'll set my Armory path to that external harddrive. Do I still need to delete some blocks then? According to the BCH network (or whatever it's called) I have not spent any BCH since the fork (even though I've spent BTC since the fork)?

You're welcome, and you're close. You should be able to copy your Core data and Armory data over to the external drive. (Make sure they're copies!) Cash should do a large reorg and reset the blockchain, downloading only the data starting from the split. The Armory wallets will work as-is but you'll want to use copies since the wallets themselves (and the Armory DB) will split once you use the coins.

I still can't see my current BTC balance,

Are you running Armory and Core at the same time? What exactly is happening?

would it be wise to first send my current BTC balance to another wallet so I don't fuck up, or is it literally completely impossible to fuck up?

Send the Bcash coins first. Cheaper fees, and they're the ones you want to move anyway.

I have one question about a line in the log file:
 "-INFO  - 09:44:27.000: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:263) Listening on port 9001"
I know goat is one of the developers of Armory, but is it trying to access his user or something? Because I of course don't have a user called goat on my computer.

No clue. Presumably a bug in the logging code somewhere. Don't worry, goatpig isn't after your coins. I can take a peek around the coins and see if I can figure out what's going on.

[ConnyH]

You're welcome, and you're close. You should be able to copy your Core data and Armory data over to the external drive. (Make sure they're copies!) Cash should do a large reorg and reset the blockchain, downloading only the data starting from the split. The Armory wallets will work as-is but you'll want to use copies since the wallets themselves (and the Armory DB) will split once you use the coins.

Are you running Armory and Core at the same time? What exactly is happening?

This is what I was running up until yesterday.
I have 2 SSD:s, one 500GB with Windows etc. installed and one 250 GB with both Armory and Bitcoin Core installed.
The bitcoin core folder is about 160 GB and the Armory folder is not even 100 MB. I don't know how this works because if I've understood it correctly the Armory folder should be about as large as the bitcoin core folder (and it would not fit in my 250 GB SSD if that were the case). But somehow this was how it was installed before (I followed a thread here on Bitcointalk to make it work).
What I had to do before to access my bitcoins and send them:
1. Start bitcoin core and let it sync.
2. Without closing bitcoin core, start Armory and let that finish. Then I would see my BTC balance in Armory and could send my bitcoins wherever I wanted.
If I did it in any other way (i.e. starting Armory without first having Bitcoin Core opened) I would not see my BTC balance in Armory and could not do anything.


Yesterday I installed the newest version of Armory and when I do the exact same thing Armory gets stuck at "Preparing Databases" and nothing seems to happen. In the right corner it says offline and I can't see my current balance.


So I don't really have alot of Armory data, should I have it somewhere? Should it be about the same size as the bitcoin data (i.e. approx 160 GB)? If then, should I maybe uninstall both Bitcoin core and Armory and then maybe install Bitcoin core on my 500 GB drive and only Armory on my 250 GB drive and let them sync? (I have a fairly fast computer, i7 quad core) and 1 Gbit/s internet, so it should not take more than a day or two, right? I also have a armory paper wallet, so I should be able to retrieve my BTC, right?
I have an external HDD with 320 GB (is that enough or do I need more space?), should I install Bitcoin ABC on that one and copy the bitcoin core blockchain files into that folder and then let it sync?
If I start Armory and path it to the bitcoin core, then I would see my BTC balance, right?
And if I start Armory and path it to Bitcoin ABC then I would see my BCH balance, right? (or am I completely lost now?)
(Since the fork I have sold approx half of my BTC, but none of my BCH, so I should have different amount of them).

Send the Bcash coins first. Cheaper fees, and they're the ones you want to move anyway.

Yes, will do when I get it to work

No clue. Presumably a bug in the logging code somewhere. Don't worry, goatpig isn't after your coins. I can take a peek around the coins and see if I can figure out what's going on.

Okay thanks!

And thank you so much for your help! As you've probably understood by now, I'm quite the newbie and need very specific instructions

[Holliday]

Send the Bcash coins first. Cheaper fees, and they're the ones you want to move anyway.

I strongly disagree. Get the bitcoins disassociated and secure before messing around with the bcash (or any other altjunkairdropcoins).

[droark]

Send the Bcash coins first. Cheaper fees, and they're the ones you want to move anyway.

I strongly disagree. Get the bitcoins disassociated and secure before messing around with the bcash (or any other altjunkairdropcoins).

Bcash does have some replay protection, and as long as you send the coins back to addresses you control, you can always import the private keys on the Core side if that somehow becomes necessary. Besides, if something goes wrong on the Core side and the coins can't be recovered (wrong address entered by accident or something), that's a tragedy. If Ver's crappy altcoins get burned, that would be a resaon to celebrate were usable fiat not involved.

[ConnyH]

I uninstalled both Bitcoin Core and Armory and then reinstalled Bitcoin core in its default path. I let them sync and now I can see my current BTC balance!

If I understand it correctly, my next step is to install Bitcoin ABC on an external harddrive and let it sync. I can then set the path of Armory to where those blocks are and I will se my current BCH balance? Or do I need to install and run another instance of Armory?

EDIT: And it looks like I remembered it completely wrong about the HDD space needed. I believe when I first got Armory (2014) the total space needed was 2 times the blockchain size, since armory took up the same amount of space. Now it looks like this is not the case (or maybe it wasn't ever like that, and I just remember it wrong)

[droark]

I uninstalled both Bitcoin Core and Armory and then reinstalled Bitcoin core in its default path. I let them sync and now I can see my current BTC balance!

If I understand it correctly, my next step is to install Bitcoin ABC on an external harddrive and let it sync. I can then set the path of Armory to where those blocks are and I will se my current BCH balance? Or do I need to install and run another instance of Armory?

EDIT: And it looks like I remembered it completely wrong about the HDD space needed. I believe when I first got Armory (2014) the total space needed was 2 times the blockchain size, since armory took up the same amount of space. Now it looks like this is not the case (or maybe it wasn't ever like that, and I just remember it wrong)

1)Glad you can see your balance.

2)Basically. As mentioned before, copy the Core data and Armory data to the external drive, use command line pathing to get ABC to update the blockchain, and then use pathing on Armory (with ABC running) to access your coins under Armory.

3)You're right. My understanding of the progress of Armory was managing the blockchain directly in memory (all versions before 0.9), then using LevelDB to manage the blockchain (0.9-0.93.3), and then LMDB to manage the blockchain (0.94-present). You're probably thinking of LevelDB, where Armory basically replicated the blockchain, which would now be ~370 GB of data when combined with the blockchain. LMDB is much smarter and only uses ~1 GB on my setup (+ ~185 GB for the blockchain).

[JBowie]

Hi guys. I am a newb to bitcoin armory. I hope you could please help me. I haven't used Armory since 2015 and I was using Bitcoin core 0.10 with Armory. I first tried rebuilding the Armory data base and block chain but that didn't work. After that i updated Armory to 0.96 and couldn't get it to work correctly so i update Bitcoin core to 0.15.1 After that it would crash on startup with a ArmoryDB.exe stopped error. I have tried updating Armory to 0.96.4 RC1 to work with Bitcoin core 0.15.1 and it crashes before Armory completely opens with a ArmoryQt.exe has stopped error. 

[RoadStress]

Hey goatpig I found a strange bug in 0.96.1. Not sure if it's present in this version too. Here it is: I tried setting the fee to 218 sat/byte, but Armory would just set it to 21. It's not important, but just saying.

Thank you for your effort as always!