Seriously, who puts that much money on finex... Just asking for a goxxing.

Wee... infinity wall.

https://i.imgur.com/hfLeDb0.jpg

I don't care (beyond the fact that it gives Joe Q. Public the impression that the entire cryptocurrency space is a joke) if people continue to make forked shitcoins until the sun supernovas and consumes the earth. What I care about, in the context of the location of this thread in the Armory subforum, is the limited resource known as "goatpig's time" and how he spends that time while coding features and improvements for Armory - A Bitcoin wallet.

If you want to petition goatpig on the importance of implementing every forked shitcoin from here until Ragnarök, however, don't let me dissuade you!

I would certainly prefer goatpig work on Bitcoin features and keeping the wallet up to date with the Bitcoin ecosystem, along with bug fixes and general improvements, as opposed to wasting time adding support for every forked shitcoin that someone dreams up. Armory is a Bitcoin wallet, after all.

Besides, one is able to access their forked shitcoins with other methods if so desired.

Did you happen to delete the armory/databases folder after updating and try the new version from scratch?

Try the latest version: https://bitcointalk.org/index.php?topic=2754632.0

Delete your Armory databases folder, update to the latest release (https://bitcointalk.org/index.php?topic=2754632.0) and try again. If that doesn't help, post your log files here.

If you are feeling frisky enough, you can use a config file to place (access) the block chain (either of them) in a non-default location.

You need to path correctly. https://btcarmory.com/docs/pathing

You should also use the latest release candidate. https://bitcointalk.org/index.php?topic=2754632.0

Well, it shouldn't take your computer all that long to sync Armory from scratch unless there is an underlying problem somewhere.

People who are better at this than me are probably going to need to see your log files in order to attempt to address your issue.

Is Bitcoin Core fully synced before starting Armory?

Are you using an external HDD for the block chain or anything like that?

Yes, log files will show folders names for where the block chain is located.

Is Bitcoin Core fully synced before starting Armory?

What are the specs of your computer? CPU? RAM? HDD or SSD?

Post your log files please.

Is Bitcoin Core synced with the network?

What does it say after "Current number of blocks" on Bitcoin Core?

You can always start Armory offline and obtain your private keys in order to import them into another wallet software.

I've never suggested as much. A used 4c/8t CPU running around 4GHz with a SATA SSD, is not "top notch" hardware (it can be had for around $200). My desktop syncs Armory from scratch in under 3 minutes and that's not even top notch hardware! 32c/64t processors and 4x M.2 NVMe PCIe 3.0 x16 raid cards are a thing.


I never commented on the quality of Dell's workmanship, rather the low IPC, core count, and clock rate of your processor (which was on the low end of Intel's product line at the time), along with the fact that HDDs are huge bottlenecks when it comes to software involving block chain data.


Well, I'm a lumberjack and I can get Armory to run, every single time with ease.


Healthy criticism is great, but that won't stop me from pointing out that your hardware is older than Moses and will struggle when it comes to dealing with large amount of data. There are requirements here, the block chain itself, which no amount of coding skill is going surmount. At some point, you either suffer or run the software on better hardware. Or, you can do what most people do and sacrifice security and use a lite wallet. That's fine, we all make trade-offs every day to suit our needs.


You are referring to Core start up. What does that have to do with anything? Do you know what Core does during start up? It isn't "load the local blockchain below 30 seconds" as you've mentioned up thread. Suggesting that Core's startup process is the benchmark for whether or not your computer can parse the block chain with ease is silly.


And all I can do is explain, apparently to deaf ears, that aging hardware is going to make the process far more painful than it needs to be. It can certainly work, but it is obvious from this thread and many threads in the past, it's going to take some additional effort on the part of the user. I'm simply pointing out that one may want to add some grease to the gears here...


Armory's security model is that your private keys are created and forever remain on an air-gapped PC (which does not have to deal with the block chain itself) while the block chain is maintained locally on the internet connected PC. Anything less (private keys online / remote block chain data) is a trade off and ultimately far, far less security.

Your hardware was average over a decade ago. Today you can buy 6c/12t CPUs that boost to 3.6GHz for less than $200. That's average! They make your CPU look like something from the dark ages. Today's high end CPUs have 12c/24t or more!

The block chain is a large amount of data, you can't just hand wave that away. You are going to need semi-decent hardware if you want to parse that data without difficulty. That is simply a fact.

Armory is wallet software which doesn't rely on outside sources for the block chain. In order to take advantage of that kind of security, there are certain trade-offs that need to be made. One of them is having a relatively decent computer.

Armory is also not for the "average user". It's for the advanced user who is comfortable with these programs and willing to run them on appropriate hardware, and willing to do some troubleshooting to get things to work. When operations takes ten times longer to complete due to ancient hardware, it's going to make troubleshooting settings that much more painful.

Basically, if you want a smooth experience with Bitcoin Core/Armory, you will want at the very least a 4c/8t CPU that boosts somewhere in the 4Ghz range and at least a SATA SSD (along with 4-8GB of RAM). SSD really can't be understated here. Many computers now use a m.2 drive which makes SATA SSD look silly. I haven't touched a HDD in 10 years. These systems aren't expensive. You can have a used system that will breeze through this for a couple hundred bucks.

I am no developer. I'm basically software illiterate. Linux is like a foreign language to me. I know hardware because I've custom built my PCs for years. I have no issues what-so-ever running Armory. In seven years I've never had it fail on me. As long as you have some semi-decent hardware, and you aren't using some crazy configuration, Bitcoin Core and Armory will simply work.

Armory needs to build its database against a fully synced block chain.

286806 isnt even close.

Your transaction won't appear until you've synced (at the very least) to the block which holds your transaction.

I didn't say delete armoyqt.conf...

Armory needs to know where the block chain is.

I said that you don't need to point to default locations in the config. You do, however, need to point to the custom locations (such as your block chain) in the conifig....

You "left bitcoin.conf on it's defaults"? What is that? By default there is no bitcoin.conf afaik. If you have your block chain in a custom location, it not default.

It seems to me that you have pathing issues, but I can't explain it any clearer than my previous attempt.

Armory does not need to be running to receive bitcoins. Once you have a receive address, coins can be sent to it at any point in time. You really should learn how Bitcoin works before using Armory. These are very basic block chain concepts.

Armory's main feature is offline transaction signing. This allows you to create transactions with an online wallet (contains no private keys) and sign it with your offline wallet (air gapped PC with private keys). Again, these are things you should be very comfortable with before proceeding.

There are many places you can go to learn about Bitcoin and Armory. This forum itself can be a useful resource. Use the search function.

https://en.bitcoin.it/wiki/Main_Page
https://bitcoin.org/en/
https://btcarmory.com/

Alan's autobitcoind is the devil.

If Armory isn't controlling Bitcoin Core, ignore "bitcoin install directory". Pretend you've never heard that term.

You certainly do not need to use custom directories with the portable versions of either Bitcoin Core or Armory. Where did you get this idea?

Unless absolutely necessary, leave everything in it's default location.

You don't need to point to default locations in a config file (as you've done above). The amount of data Armory requires should fit in the default location, there really isn't any reason to use a custom path.

If you use a custom path for the block chain, make sure that path matches in both Bitcoin Core and Armory.

Keep paths simple. "Blockchain Core" is the name of the folder where you keep the block chain? Just call it "Bitcoin" for the love of all things holy. Why are you using quotes, they aren't necessary (if you don't use spaces in your folder name, which you shouldn't).

Here is an example of my exact config files.

bitcoin.conf


As you can see, I've relocated the block chain data to my D drive. Now, I have to tell Armory where that data is located.

armoryqt.conf


The D drive on my computer has one folder in it called "Bitcoin".

This setup works every time, without fail, on a clean Windows 10. I start Bitcoin Core (from a folder on my desktop, never installed). I wait for it to finish syncing, then I start Armory (from a folder on my desktop, never installed). If I want to use an existing wallet, I copy that to the Armory folder before the initial start up.

If I were you, I would:

1. Delete the contents of the Armory folder in C:\Users\username\AppData\Roaming except for the wallet files.

1. Copy my config files into the appropriate folders.
            
            bitcoin.conf goes into C:\Users\username\AppData\Roaming\Bitcoin

            armoryqt.conf goes into C:\Users\username\AppData\Roaming\Armory

2. Modify the config files with your specific locations. Keep it as simple as you can (like mine).

Hopefully this shines some light on pathing. Either do as suggested or modify your current setup with the above in mind. If this doesn't work, I would delete your block chain and start from scratch.

The config file is placed in the default Armory folder. When Armory starts, it reads the config file and uses any custom directories you've included there. This is also how Bitcoin Core works.