The transaction pays a fairly low transaction fee. There is not much you can do as the receiver. You can try asking miners for help. The users Quickseller and macbook-air have access to a mining pool and are known to have helped people with this type of issue before.

Run
where <blocks> is the number of blocks that you want your transaction to be confirmed within. Note that you cannot choose 1 because that is too soon and not enough data can be gathered for 1 block. I recommend using 3.

Take the result of the estimatefee command above and run
where <fee> is the output of the estimatefee command.

Then whenever you send using the wallet RPCs in the same session, it will use the fees set by settxfee.

RBF is, by definition, a double spend attempt, regardless of Opt-in or not. You are creating a transaction which spends inputs already spent by an unconfirmed transaction.

This method is Full RBF, not Opt-in or First-Seen-Safe RBF. It is still RBF and is as Peter Todd originally proposed RBF.

Download and install Electrum from https://electrum.org/#download. Once it is installed, start it up. It should ask you to make a new wallet. Choose the Standard wallet option and follow the instructions in the dialog to secure your wallet.

Make sure that Bitcoin Core is shut down. Start Armory. If you did not change it so that you have to manually start Bitcoin Core, go to File > Settings, and uncheck the box "Let Armory run Bitcoin Core in the background". Then restart Armory. Armory should be in offline mode.

In Armory, double click your wallet in the table at the top right of the window. This should open up a "Wallet Properties" dialog box. Click on "Backup This Wallet" and another window should appear. Choose the option "Export key lists" and then click the big "Export key lists" button. You should now see a window titled "All wallet keys". You will see a bunch of checkboxes at the top right. Uncheck all of them except for "Private key (Plain base 58)". At the bottom of the window, check the box "Omit spaces in data". In the middle of the window you should now see some lines that start with "PrivBase58:" and are followed by a string that begin with a '5'. The strings beginning with '5' are your private keys. Copy all of the lines that are of that format (ignore the stuff at the beginning, which should be Created, Wallet Name, and Wallet ID, you don't need those).

Now back to Electrum. Go to Wallet > Private keys > Sweep. In the big box, paste all of the private keys that you copied. Remove the "PrivBase58:" in front of each line. At the bottom of the dialog is a field for an address. This is because you are sweeping the Bitcoin so Electrum will send all of the Bitcoin associated with the private keys you entered to an address in the Electrum wallet. It should choose an address in your wallet for you. Then click "Sweep" and follow whatever other instructions Electrum gives you. Wait for the transaction to confirm, and Voila, you have migrated all of your Bitcoin to Electrum.

Once the transaction confirms, it should be safe for you to uninstall Armory, uninstall Bitcoin Core, and delete their data directories.

It could be when there are spikes in transactions that need verification. Could also be new blocks coming in that need to be checked.

That is a transaction, not a block.

The r and s values look right to me.

The message that is signed is the sha256 of the sha256 of the transaction with the signing serialization (which is your second hash). Note that this is different from the transaction id which is the sha256 of the sha256 of the entire transaction.

Take a look at localbitcoins.com. There may be people selling Bitcoin near you for cash. Or you can do an online trade with another person with something like a direct bank wire. Just always use Local Bitcoin's escrow system, if the seller asks you to not use it, don't trade with them.

What is an "receive email number"? Do you mean a Bitcoin address? If it is not a Bitcoin address, then such a thing is not recognized by the Bitcoin network or any other wallet.

You can just use Trezor and create an address. Then send all of your Bitcoin from your blockchain.info account to an address from your Trezor.

Your Bitcoin addresses are meant to be published and shared. Note that the wallet ID is a blockchain.info only thing, it is not related to anything else with Bitcoin.

Unless the Bitcoin was sent to an online or exchange wallet (depends on the service whether they credit your account), then you still have the Bitcoin. Addresses do not expire and wallets will keep track of all addresses, they do not just delete an address after it has been used.

Are you using the latest dev? If so, I think it is currently unstable. Goatpig was working on some fixes to the socket (related to that dblog error you posted) and I don't think they are completely done yet (something about edge cases).

Did you run
before attempting to build? If not, do that first.

This is incorrect. The payment protocol does exactly that, it sends the exact amount of Bitcoin to their address. There is no need to use the payment protocol, you can just send the exact amount of Bitcoin to their address. I have done this many times with sending from Armory to a merchant that uses BitPay.

Armory does not support the payment protocol yet. However you can just send the exact amount of Bitcoin directly to their address, as that is what the payment protocol tells your wallet to do. The only other thing it does is verifies that the address actually came from BitPay and not some malicious third party.

Nope. Just send the exact amount to BitPay's address.

I asked someone to try this and it did not work for them.

Opt-in RBF is indeed a great feature. Unfortunately it is not used by most people so it is not really applicable here as most transactions will not enable RBF.

The transaction fee is the difference between the amount spent by the inputs, and the amount sent to the outputs. In order to increase the transaction fee, you either need to add a new input or reduce an output. What this software does it reduces one of the outputs, which you can choose. By default it chooses the last output.

Open the start menu and search for "regedit". Open the program, it should ask to be run as an administrator. On the left sidebar, click the arrow next to "HKEY_CURRENT_USER". Then the arrow for "Software" and then the arrow for "Bitcoin". Click Bitcoin-Qt. The main window should show a bunch of stuff. Find the one labeled "fUseProxy" and double click it. The value data box in the dialog that shows up should say "true". Change it to "false". Close regedit and start Bitcoin Core. It should no longer be using the proxy.

I use an Amazon EC2 t2.micro instance to host the site and do all of the calculations.

Make what faster? The wait time for the stats to be generated? Unfortunately nothing can be done about that as that is actually dictated by bitcointalk. Bitcointalk restricts requests to 1 request per second, and because the site has to request all of a user's show posts pages, there are a lot of requests that need to be done, but only once per second. That is why there is a queue and a wait time, to keep under the rate limit.

You can only send from an address if it still has Bitcoin. Bitcoin is not actually stored in an address, and you can't just magically send from any address in your wallet. If you don't have any Bitcoin associated with an old address, you can't spend from it.

You should not need to send Bitcoin from an old address as you may not necessarily have money in an old address. You can however sign a message from an old address. Ask their support if they will accept a signed message (and they should, it still indicates that you control the private key to that address) and use that instead to prove ownership. Make sure your message also includes the current date and time when you sign it.

Make your desktop into portrait mode (basically turns the desktop sideways to take advantage of the wider monitor) and look at it sideways for a bit to see the button. Otherwise there isn't much else that you can do. I should make it scrollable, but I don't really have time to maintain the software.

Bitcoin Core has a pruning feature which deletes most of the blockchain, but unfortunately Armory will not work if you enable that.

You can export the private keys for your address(es) from Armory and import them into another wallet. You can import them into Bitcoin Core and enable pruning, or use a different lightweight wallet like Electrum.

That's quite a large transaction that you have there. You have to make the window as large as possible as JavaFX does not automatically scroll the window apparently when there are too many things on it.

Yes, Bitcoin Core must be fully up to date. If it says that it is behind by some number of days, weeks, or years, then it is not synced. Note that the time listed there is not the amount of time that is required for it to actually be up to date but rather that the most recent block it has is that long ago. It can take anywhere from a few hours to a few days depending on your hardware and internet connection.