Your transaction fee rate is not high at all. You are paying a fee rates of 109 sat/byte, 120 sat/byte, and 132 sat/byte, which are much lower than the current recommended fee rate of 270 sat/byte according to https://bitcoinfees.21.co/.

Your third tx depends on the second, so it cannot confirm until the second does. The second depends on the first, so that cannot confirm until the first does.

Read https://bitcointalk.org/index.php?topic=1802212.0 for what you can do about your transactions.

Yes. Using the same address will result in less privacy and potentially less security. People who send you money will know how much money you actually have. People can then also see who you are paying and how much you are paying them. It is highly recommended that you do not use the same address but instead generate a new address for each payment you want to receive.

All you can do is ask miners for help and wait. Read https://bitcointalk.org/index.php?topic=1914800.0

Blockchain.info's web wallet is considered a poorly written wallet and is seemingly incapable of sending proper transactions with correct transaction fees and confirmed inputs. If you are using blockchain.info's web wallet and your transaction is stuck, it is almost definitely because the transaction fee is too low (at 120 sat/byte which seems to be blockchain.info's default fee rate even though it is much too low) or because you are spending from other unconfirmed transactions.

If you are using blockchain.info's web wallet, unfortunately you won't be able to attempt RBF or CPFP transactions as blockchain.info does not provide the advanced functionality to make those transactions. All you can do is ask miners for help and wait. For asking miners for help:

To avoid this problem in the future, stop using blockchain.info. Instead switch to any wallet listed on Bitcoin.org and has one of the following texts regarding how the wallet handles transaction fees:
Any wallet which has one of these texts for in their descriptions (with the color and bolding) will support dynamic fees and allow you to make transactions with proper fee rates.

Firstly, DO NOT POST ISSUES RELATED TO BLOCKCHAIN.INFO (including "stuck" transactions made with their wallet) HERE! If you do, your thread will be moved to the Web Wallets section.

Blockchain.info's web wallet is considered a poorly written wallet and is seemingly incapable of sending proper transactions with correct transaction fees and confirmed inputs. If you are using blockchain.info's web wallet and your transaction is stuck, it is almost definitely because the transaction fee is too low (at 120 sat/byte which seems to be blockchain.info's default fee rate even though it is much too low) or because you are spending from other unconfirmed transactions.

If you are using blockchain.info's web wallet, unfortunately you won't be able to attempt RBF or CPFP transactions as blockchain.info does not provide the advanced functionality to make those transactions. All you can do is ask miners for help and wait. For asking miners for help:

To avoid this problem in the future, stop using blockchain.info. Instead switch to any wallet listed on Bitcoin.org and has one of the following texts regarding how the wallet handles transaction fees:
Any wallet which has one of these texts for in their descriptions (with the color and bolding) will support dynamic fees and allow you to make transactions with proper fee rates.

blockchain.info's wallet and fee estimation (if they even have any, it doesn't seem they actually do) is complete garbage. I highly suggest that you stop using their wallet and use a desktop wallet like Electrum instead. With properly written wallet software like Electrum or Bitcoin Core (and not blockchain.info's wallet) you won't have many issues with transaction fee, and if you do, the wallet has sufficient advanced functionality to properly deal with it. You don't need to be an "expert" to use these software and they do everything for you in the background like blockchain.info, but they do it better and properly.

With blockchain.info, all you can do is wait and ask miners for help.

The transaction fee rate has been above 200 sat/byte for the past several months.

Your transaction pays a fairly low transaction fee rate, only 120 sat/byte. According to https://bitcoinfees.21.co/, the current recommended transaction fee is 270 sat/byte, more than twice the fee rate you paid. Read https://bitcointalk.org/index.php?topic=1802212.0 for what you can do about your transaction.

Bitcoin Core is developed on github here: https://github.com/bitcoin/bitcoin. If you want to contribute, you make a fork of the repository (which goes to your account), make your changes, and then open a Pull Request on Bitcoin Core's repo. Then other Core contributors review your code and indicate whether they support the change or not. If a lot of the reviewers think the change is something that they want in Core, the maintainers of the repo will merge the change and it will be a part of Bitcoin Core.

Yes, but it requires a hard fork. It would require every single person running a Bitcoin node to update their software to accept that new rule.

Because the block subsidy will go to 0 over time (and it decreases very quickly). Transaction fees are to pay miners so that they keep mining in the future as the block subsidy goes to 0. Otherwise there would be no incentive to mine blocks.

There is no voting, there is only signalling. Signalling is not the same as voting.

Segwit uses BIP 9 for deployment. After the starting date (Nov 15th 2016 for segwit), miners can signal that they are ready to enforce the segwit rules by setting a specific bit in the version numbers of their blocks. This state is known as "Started". Once at least 1916 blocks in a 2016 block difficulty retarget period have signalled for segwit, the next retarget period will be in a state called "locked in". Locked in means that it will activate once that retarget period ends. The point of this time is to let everyone know that segwit will activate and give them time to update their nodes and wallets to support segwit if they want to use its features as soon as possible. Once the locked in retarget period ends, the state changes to "Active" and the segwit rules will be active.

This is a known issue, but I'm not sure how to fix it. I have been experiencing the same problem for a long time. It happens because ArmoryQt is unable to connect to ArmoryDB, so when it shuts down, it is unable to shut down ArmoryDB too since there is no connection. ArmoryDB is what handles the bitcoind so that doesn't shut down either.

Edit: goatpig figured it out a few days ago and this issue has been fixed for 0.96.1

Your transaction pays a fairly low transaction fee, only 116 sat/byte whereas the current recommended transaction fee is 270 sat/byte according to https://bitcoinfees.21.co/. That is why it is taking so long.

Unfortunately, because you use blockchain.info's web wallet, there is not much that you can do. I highly recommend that you stop using their wallet and instead get a desktop wallet like Electrum in order to avoid this issue in the future. blockchain.info's fee estimation is basically nonexistent and seems to have a maximum of 120 sat/byte even though the recommneded is over twice that fee rate.

addrlocal is just what that peer thought your IP address was when it first connected to you. It doesn't actually matter as that field isn't used for anything.

Can you post the Armory log files? Go to File > Export Log Files and copy the contents of the exported log file into a post here.

It is possible that something is erroring and preventing the wallet from being unlocked even if you entered the right password. Those errors will appear in the log files.

I have just been using Ctrl+C (when ArmoryDB is in the terminal) or sudo kill -9 to kill it and I have not experienced any issues. I think that is the only way to actually stop ArmoryDB when you run it yourself.

That's interesting. It looks like some blocks are corrupted and that is what is causing the crash. I suggest that you redownload the blockchain entirely so it actually starts from scratch. Just delete the entire blocks folder in the datadir and it will redownload and resync the entire blockchain.

If the error still comes up after you do this, I think it is likely that you have a hardware error. If the error does come up again, run hardware diagnostics, especially for the hard drive and for the RAM and see if that comes up with any errors.

The value of the fee itself (especially in fiat) is completely meaningless. What matters is the fee rate in satoshis per byte.

Your transaction pays 112 sat/byte, which is much lower than the current recommended fee of 270 sat/byte according to https://bitcoinfees.21.co/. Furthermore, you transaction spends from this unconfirmed transaction: https://blockchain.info/tx/acef4181af12098dd8b29e1fff0f171dfefc7d4dd58435149b1554583d6006ac. Your transaction cannot confirm until this unconfirmed transaction confirms as well. That transaction pays a fee of 105 sat/byte.

The transaction fees on your transaction are not "reasonable". According to https://bitcoinfees.21.co/, the current recommended fee rate is 270 satoshis/byte, you only paid 120 satoshis/byte. That is not your only problem though. Your transaction spends from this: https://blockchain.info/tx/1745ed7850a2fec54af82f5ee35906622a93ba1f51b110431be67428a6b38c87 unconfirmed transaction which has a fee of only 53 sat/byte. Your transaction cannot confirm until this unconfirmed transaction confirms as well.

You will need to have access to the computer that originally had the wallet. Without it or a backup, you cannot access your Bitcoin.

From your original computer, make a digital backup of the wallet. Then copy the file it makes onto a USB drive and bring the file over to your new computer where you have installed Armory. Choose the "Import or Restore wallet" button and then choose your backup file. That will then import the wallet into Armory.

Electrum is not a company, they do not have a "customer service department".

I have moved your thread to the Electrum sub forum.

Please post the transaction ids for the transactions in question. There is likely no issue related to Electrum itself, especially if your are the recipient of a transaction.

With a transaction of 2437 bytes and paying a fee rate of 280 satoshis/byte, you would need a fee of 682,360 satoshis, which is 0.00682360 BTC. You should either set your wallet's fee rate to 280 satoshis/byte or set the fee for the transaction itself to 0.00682360 BTC.