You should run Bitcoin Core manually and then start Armory. Don't let Armory run bitcoind because that is known to cause many issues.

You probably have a corrupted block in blk00377.dat in the blocks folder in Bitcoin Core's data directory. You probably need to redownload a large part of the blockchain to fix the issue.

When you want to send Bitcoin, pay a high enough transaction fee and you won't have any issues. Use a wallet that has dynamic fees so it will always calculate the best transaction fee for your transaction to confirm quickly based upon the state of the network.

As for a block size increase, there is a lot of technical nuances that have to go into making one happen. There are currently two proposals out there that have been implemented: Segwit and Bitcoin Unlimited. Nearly all people who can be considered "Bitcoin experts" (aka developers) agree that Segwit is the way to go and that BU is flawed and has issues. Unfortunately activation of segwit depends on enough miners signalling support, and right now that is not happening. Miners right now are tending to not signal any support for any of the proposals.

When the transaction "drops" and "disappears" from your wallet, it does not necessarily drop or disappear from the mempools of all nodes. Some nodes and block explorers will still remember the transaction. When you go to send again, those nodes and block explorers remember the first transaction, and because you sent again, you technically have created a double spend transaction so block explorers will mark the transaction as such.

BIP 70 has something similar to what you are trying to do. It has the option to allow merchants to sign the payment request with a X.509 certificate to prove that the request and thus the address to pay is actually theirs.

However, I still don't see how this solves your problem. If someone injects an address into your database, then you probably won't know that that happened and still end up signing the address and giving it out anyways.

Your transaction has a low transaction fee, so it will take longer to confirm.

You have a few options here. You can wait and hope it confirms, wait for the transaction to be "forgotten" by the network, or ask a miner to confirm it for you.

For the third option, you can contact the users Quickseller and macbook-air. You can also try using https://www.viabtc.com/tools/txaccelerator/ to "accelerate" your transaction.

Unfortunately because you do not control the private keys for the addresses being sent from in that transaction (they are bitbargain's keys), you can't do anything else like attempt a RBF transaction.

If you have access to the private keys on the receiving end, you can try a Child Pays For Parent transaction where you spend from your stuck transaction and pay a transaction fee which covers both the stuck transaction and the spending one.

First of all, transactions are not "canceled" nor "returned". When your wallet forgets about a transaction, nothing is sent back, it simply acts as if the transaction never happened.

The previous expiry time was 3 days. However, often times transactions will either expire out of the mempool and be rebroadcast and subsequently put back into the mempool, so the expiry time did not matter at all. If your transaction is unconfirmed for more than 2 or 3 days, it will probably get evicted from the mempool anyways because the fee is too low. The minrelay fee has been changed to be dynamic for a couple of releases already. If a transaction remains unconfirmed for several days, its fee is likely too low and the minrelay fee will have moved to be greater than that transaction's fee rate so it is evicted anyways. Transactions that pay a sufficient fee will probably confirm within two or three days so this does not really affect that.

No. You cannot change a transaction once it has been created and broadcast. Setting the fee can only be done at the time of creation.

What are you confused about? You can move the fee slider forward to get a better fee.

If you pay a sufficient transaction fee, then this is not a problem at all. I rarely run into any issues with sending because I use a wallet which has dynamic fees so it sets a sufficient transaction fee to be confirmed within 3 blocks.

Follow these instructions very carefully. I am going to give you specific instructions for using Electrum to import the private keys from blockchain.info to Electrum and then have you sign a transaction to broadcast it.

First, go to your bc.i wallet and go to Settings > Security. Then click on the "Backup Phrase" button. This will have you go through a process to get your twelve word seed phrase. Copy those 12 words somewhere safe.

Then go to https://electrum.org/#download and download and install Electrum. Once it is installed, when you first run it, it should have a dialog for creating a new wallet. Choose the "Standard wallet" option and click Next. Choose the "I already have a seed" option and click Next. In the box, enter your 12 word seed phrase. Click the "Options" button and check the box for "BIP 39 Seed". Click Next and set a password. Then click Next. You should now have an Electrum wallet which should exactly mirror your blockchain.info wallet. You should see any confirmed transactions in the History tab. To double check this is your wallet, click on Wallet > Addresses. You should get a list of addresses. Double check that they match the ones in your blockchain.info wallet (you will probably get more addresses than you have in your bc.i wallet).

If that is all correct, then now you can create a double spending transaction. Your unconfirmed transaction shouldn't appear in the history list, and if it doesn't, then you can use the send tab to send your Bitcoin to an another address in your wallet. Once the transaction is signed and broadcast, the broadcast may actually fail. In the dialog where you see the transaction details before broadcast, click the "Copy" button and then paste that into a post here. That will post your raw signed transaction for others to broadcast for you should Electrum fail to do so (because its a double spend).

If it does appear in the history list, report back here.

You have a few options here. You can wait and hope it confirms, wait for the transaction to be "forgotten" by the network, attempt a double spending transaction that pays a higher fee, or ask a miner to confirm it for you.

For the third option, there should be something in Multibit that is like "reset wallet" or "repair wallet" which would clear all of the unconfirmed transaction from your wallet and allow you to resend the transaction but with a higher transaction fee.

For the fourth option, you can contact the users Quickseller and macbook-air. You can also try using https://www.viabtc.com/tools/txaccelerator/ to "accelerate" your transaction.

Did you know that it's possible to ask a question without writing an entire paragraph with a whole tangent in the middle? You should do that because your post is almost off topic and signature spam. In fact, it probably is signature spam but it is a legitimate question so I won't delete it.

There is no risk to using services like ViaBTC's. They only ask for a transaction id, and anyone can submit a transaction to be "accelerated". Transaction ids are already public, as are the details of everyone's transactions, so it doesn't matter. Revealing your transaction id or its details does not reduce your security as everyone running a full node already knows the details of your transaction, and anyone can easily lookup your transaction in any block explorer. Their service "accelerates" transactions by increasing the priority of the transaction in the mempool of their mining pool. That means that if ViaBTC's mining pool finds a block, it has a higher probability of being included in the block.

Also, transactions are not "stuck in the blockchain". They are not in the blockchain, thus they cannot be stuck in it. The whole point of mining and confirmations is to be included in the blockchain. "Stuck" transactions are just transactions that have remained unconfirmed for longer than the sender or receiver wants it to be.

Because you are not the sender (you don't have any control over the parameters of the transaction except the amount), there is nothing you can do. Bitcoin transactions cannot be canceled nor can they be modified. You can either just wait or ask a miner to confirm it.

For the second option, you can try using https://www.viabtc.com/tools/txaccelerator/, and contacting the users Quickseller an macbook-air. Those two users have access to a mining pool and are known to have helped people with similar issues before.

The transaction is not in the blockchain. There is no "progress" or a set time limit for the transaction to confirm. It is impossible to say when a transaction will confirm as that is attempting to predict the future.

Use a wallet that supports dynamic fees. This means that the wallet will choose a fee rate based upon the state of the network at the time you make the transaction. This will ensure that an optimal fee is set. You can also use a site like http://bitcoinfees.21.co/ to get the optimal fee rate and manually set that before making a transaction.

I can create a double spending transaction for you, but you would have to sign it. However, because blockchain.info no longer supports exporting private keys and does not allow signing of raw transactions, this process will be extremely difficult as it requires using the wallet seed in another wallet and hoping that it derives the same addresses as blockchain.info.

Bitcoin transactions are irreversible. You cannot "cancel" a transaction. The best you can do is to create a double spending transaction which invalidates the original if it confirms. However that entirely depends on the double spending transaction confirming instead of the original transaction.

Since your transaction is currently unconfirmed, you can attempt to make a double spending transaction, but this may be very difficult for you as you are using blockchain.info. You will somehow have to get the private keys off for your addresses off of blockchain.info and use another wallet in order to create, sign, and send the transaction.

While the transaction is unconfirmed, you should not spend from it to pay someone else. That spending transaction cannot confirm until your receiving one does, so whatever you spend it on may not accept the transaction and credit you with having paid them.

Your transaction is taking a long time to confirm probably because the transaction fee is too low. As the receiver of that transaction, there isn't much that you can do to make it confirm faster. You can try asking miners to confirm it for you.

The problem is that you are using a fixed fee rate and thinking that there is a standard fee rate that will always work. Unfortunately this is most definitely not the case. You cannot just set a fixed fee rate and expect it to work every time. The state of the network constantly changes and thus the recommended fee will as well.

In order to avoid this problem, you should use a wallet that supports dynamic fees. This means that the wallet will calculate the optimal fee rate based upon the fees of transactions that are confirmed. If you cannot do that or do not want to do that, then you should always change the fee rate that you are using. You can use a site like http://bitcoinfees.21.co/ to find out what the current optimal fee rate is and set that as your transaction's fee rate prior to sending the transaction.

The number of peers seen has nothing to do with how soon your transaction will confirm.

What is the txid of your transaction? It is extremely likely that your transaction fee is too low and thus it has not confirmed yet.

Yes.