Yes, please post your log files.

Bitcoin Core is the name of a software, not the name of the coin. The name of the coin should not be based on the name of the software that most nodes are running. There can and are multiple node software that enforce the exact same consensus rules and all have different names.

There is no voting. No one votes on anything. Bitcoin is not a democracy. Even after all coins are mined, mining will still continue. No one has the power to unilaterally change Bitcoin's consensus rules. The consensus rules change when the supermajority of users, nodes, and miners all agree to change the consensus rules. Typically the consensus rules are activated when miners signal that they will be enforcing the new consensus rules. That is not a vote, it is a signal of readines.

There will still be mining and there will still be nodes. Mining is not just the process of generating new coins, it is the process of including transactions in blocks and that can, must, and will continue even after all Bitcoin has been mined.

There is no need to make a second Bitcoin Core wallet, or to even do anything to split your coins. Since they now have two way replay protection, your coins will be split the moment the chain forks.

What you need to do to spend your ABC coins is to just make a copy of your Core wallet.dat file. Then install the Bitcoin ABC client and put your copied wallet.dat file in the place where you want the ABC datadir to be (do this before starting ABC). Then start ABC and let it sync. When you want to spend your ABC coins, just use the ABC wallet. When you want to spend your Core coins, use the Bitcoin Core wallet.

Upgrade to our latest testing build: https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.0.4

Have you installed Bitcoin Core? If not, install it from https://bitcoin.org/en/download and let it sync with the network.

The company doesn't exist anymore. There are no company emails or twitter as the company originally behind Armory dissolved. It is maintained by the community now.

There may be a hard fork on august 1st, but that does not mean that Bitcoin is changing. What will happen is that there will be two coins, one will remain Bitcoin (the chain using the current rules) and the other one will become an altcoin, Bitcoin Cash (the chain with the different rules). Whatever happens to Bitcoin Cash will not effect Bitcoin and vice versa. You can continue to use Bitcoin as you would normally. The way that fees are calculated will be the same for both chains and the RPC commands and command line options for both chains will remain the same.

In what way do you think emotions would be something that can be put in the blockchain? The blockchain is just a data structure. If you have data that is "emotion" or whatever, you can put it in the blockchain, otherwise, no you cannot.

Yes. The replay protection is opt in, so if you naively send the coins, then you are not opting in to their replay protection. You can split your coins to avoid transaction replay though and that can also be done without using Bitcoin ABC's replay protection.

Yes.

There are three methods that I know of that you can use. The first two are Bitcoin ABC's opt-in replay protection, and the last one would work with any chain split.

The first method is to make a transaction on the Bitcoin ABC chain that sends all of your coins on that chain to another address in your wallet. This transaction would use their newly-defined sighash type which is invalid and unknown to the non-ABC chain. Once that transaction has confirmed, send the coins on the non-ABC chain to yourself as you would normally.

The second method is to make a transaction on the non-ABC chain which includes an OP_RETURN output with the string
The ABC chain will reject transactions with such outputs until they reach block 530,000. Once that transaction has confirmed on the non-ABC chain, send your coins to yourself on the ABC chain as you would normally.

The third method is to use transaction lock times. On the chain that is longer, create a transaction which has a sufficient fee to be confirmed in the next block or two and has a locktime of the current block height. Once that transaction confirms, on the shorter chain send your Bitcoin to yourself as you would normally. Note that this method requires on chain to be several blocks longer than the other chain.

There is actually a fourth method that uses RBF, but I don't know how well that would work since Bitcoin ABC removed all RBF logic.

Note that all of these transactions must be transactions back to yourself. That way if you made a mistake and a transaction is replayed, you won't lose any coins.

Running a node with the default settings will consume 3-400 GB of data.

Your node is the machine that is running the Bitcoin Core software. Your node is up if the Bitcoin Core software is currently running. It is down if the software is not running. It is up for a long time if the Bitcoin Core software has been running on that machine for a long time.

The entire bitcoin network is designed without any consideration for data usage in mind. Many optimizations are currently being made to reduce data usage, but some things cannot be changed because they are part of the consensus rules.

Do you have any antivirus software running, including windows defender? If so, either disable it or set it to ignore everything in C:\Users\Andrzej\AppData\Roaming\Bitcoin. Sometimes antivirus software will mess with the blockchain data since someone has embedded virus signatures into the blockchain.

No, there is risk of a replay attack. Currently Bitcoin ABC's replay protection is entirely opt-in, so if you don't try to replay protect your transactions, they can be replayed on both chains.

Because Bitcoin ABC was the original name and the name of the client. Then ViaBTC went ahead and started calling it Bitcoin Cash.

I wouldn't be surprised if they were.

Yes. You can even just copy Bitcoin Core's datadir entirely instead of syncing a Bitcoin ABC node from scratch.

There are instructions for cross compiling here: https://github.com/bitcoin/bitcoin/blob/master/doc/build-windows.md

Assuming that they don't change the transaction format or make it impossible to make legacy transactions (i.e. transactions that you make now), then Armory should work just fine. It would be very stupid of them to not accept legacy transactions since it would mean breaking all unconfirmed and timelocked transactions at the time of activation.

Considering that they are still trying to figure out what they want to do, I suggest that you wait until after they fork off before figuring out what you can do to avoid transaction replay.

Either way, Armory does have some replay protection built in, in the form of the transaction lock time. Armory will set the transaction's locktime to be that of the block height at the time the transaction is created. This means that the transaction can only be included in blocks which have a height greater than or equal to the specified locktime. When Bitcoin ABC forks, they will almost definitely have a minority hashrate so their blockchain will grow more slowly (although they do have a difficulty adjustment thing), so their blockchain will be at a lower height for a while. So while their blockchain is at a lower height, you can make a transaction on the main chain and it will have a locktime block height greater than that of the ABC's chain height. Once that transaction confirms, you just move to the ABC chain and make the same transaction there, but without the locktime. The second transaction would be a double spend on the main chain, and it should confirm before the first transaction is able to on the ABC chain. Once both transactions are confirmed, your coins are split.

No, please don't call Bitcoin Core that. There is a software called Bitcoin Classic which is based on Core. If there is a fork, don't call the fork that runs Bitcoin Core "Bitcoin Classic". You will confuse the hell out of most people.

There is no guarantee that there will be a fork. There currently is no fork. If there were a fork, Bitcoin Core would likely still be "Bitcoin". Right now, that analogy is completely wrong and you should stop thinking of it. Bitcoin Core is just a software, not the name of a coin.

Their transaction replay protection is all opt-in. Transactions on Bitcoin ABC are still in the current transaction format.

Have you redownloaded the entire blockchain from scratch (i.e. deleted the blocks folder in the datadir or used a completely new datadir)? If not, try doing that.

Otherwise, you may have a hardware issue, not necessarily disk. More likely you have a problem with your RAM. Just run system diagnostics and see if it finds anything wrong with your system.

Should be back now

Yes, see my update

474294 is missing the parent entirely.

Both blocks are invalid because they included a transaction without including its unconfirmed parent.

I checked block 474294 and it contained transaction a6655ca47c62ffcbf6d3dcba34bc1af24a1eb0bcea54d3099d36201a66aec2a0 but not its parent transaction b11a78c6c61af1cb37586f639050d74b95c2b0fd525623b6cb6a4bb4fba46a0e.

I'm still checking block 477115 for which transaction it is missing, but it triggered the same error message as 474294, so I believe it is caused by the same problem.

Update: Block 477115 is actually more interesting than 474294. It contains the transaction 7a122ef22468e4af16b010d7acf7aa81e5af3636423c613fd98246c179d79800 which is missing its parent 9639dd073e67efc879abb1075fafa4fa23d5fa427c129b2b1dd4f5a5520b408d. But the interesting part is that the parent transaction is actually lower down in the block. So the problem here is that the transactions are in the wrong order, which means that they are probably permuting the order of their transactions.

One thing to notice is that 477115 contains 256 transactions and 474294 contains 255 transactions, both of which are good numbers of transactions to have for asicboost. Furthermore, this problem could be caused by permuting transactions as would need to be done for asicboost.

Edit: corrected transaction counts

Bitcoin ABC and "Bitcoin Cash" are the same thing.

Lets call it Bitcoin ABC.

Yes.

You won't be receiving any coins on the other chain. What you will have is a wallet which has exactly the same state (same transactions) as your wallet on the other chain.

You can't. Bitcoin Core cannot understand the consensus rules that Bitcoin ABC will be deploying. It is a hard fork, so whoever wants to use that fork needs to upgrade their software. The only way you can spend Bitcoin ABC coins is to use the Bitcoin ABC client.

Because the Bitcoin ABC client is based off of Bitcoin Core, you can simply copy the wallet.dat file into a data directory you are using for Bitcoin ABC and be able to use your wallet from there. They are not incompatible.

Just copy your wallet.dat file into a data directory that you are using for Bitcoin ABC. Then you will need to split your coins. You can read about how to split your coins here: https://bitcoin.stackexchange.com/questions/56867/bitcoin-cash-replay-protection/56874#56874