I think this is what you are looking for: https://github.com/btcsuite/btcd/blob/ab0f30c00d17bb7766c06174d77661443df08973/chaincfg/chainhash/hashfuncs.go

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, we need to know what wallet software you are using.

For the fourth option, you can contact the users Quickseller and macbook-air.

The only part that depends on the fee is the first confirmation. Each confirmation after the first just means that that many blocks - 1 have been built on top of the block which includes your transaction. Those confirmations should come every 10 minutes or so as that is on average how long it takes for a block to be mined.

I am not familiar with go, I just looked at the logic.

It looks like you should be using btcutil.base58.Decode()

You don't have to do one transaction at a time or have to wait for previous transactions to confirm, but any transactions that depend on an unconfirmed transaction will not confirm until the ones it depends on confirm as well.

The issue with your transaction is the low fee. 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, you can do "Repair wallet" in MultiBit. That will clear all unconfirmed transactions from your wallet. Then you can respend the BItcoin in a transaction with a higher transaction fee.

For the fourth option, you can contact the users Quickseller and macbook-air.

Well any wallet that has Dynamic fees should be fine. Personally I use Bitcoin Core and Armory but that requires syncing the entire blockchain so that may not be very good for you. Otherwise, I recommend using Electrum. However, IIRC Electrum might have the same fee cap issue as blockchain.info, so you may have to set the fee rate manually. For setting the fee rate, you can use sites like http://bitcoinfees.21.co/ and https://bitcoinfees.github.io/ to see what the optimal fee rate is and set that for the fee rate in your wallet before each transaction. The best fee rate will constantly change as the network state changes, so you can't have a fixed fee that will always work.

Note that those sites use satoshis/byte but most wallets do BTC/kB. You need to convert the number you get from those site by dividing the amount by 100000 and that will get you the fee rate in BTC/kB.

What did you do for the other big events (100th ad round I assume)?

How about having more than the normal number of ad slots.

IIRC Blockchain.info sets a maximum fee rate of 65 satoshis/byte, even if the recommended dynamic fee rate is much higher than that.

Unfortunately Blockchain.info does not provide enough advanced utilities to do option 3. Your only options are to wait or ask a miner for help. I suggest that you contact the two users I linked above.

The issue was resolved over the IRC channel.

There are a few problems here.

Your third transaction depends on the first transaction, it cannot confirm until the first one does.

You have paid a low transaction fee on your transactions, ~65 satoshis/byte for the 2nd and third and ~55 satoshis/byte on the first. According to https://bitcoinfees.github.io/#30m the current recommended fee is ~140 satoshis/byte.

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, we need to know what wallet software you are using.

For the fourth option, you can contact the users Quickseller and macbook-air.

That command tells your wallet to forget about that transaction. However not everyone on the network has necessarily forgotten about it, so it is possible that a miner decides to include your transaction in a block, thus confirming it. The best way to prevent that from happening is to immediately spend the Bitcoin to invalidate the original transaction.

Before you to that command, run the following:
where <result of estimatefee> is the result of the first command. It should be a number like 0.00137237. This will get the BTC/Kb estimate for a transaction to confirm within 3 blocks. Then it will set that so that when you send that is the fee rate for your transaction.

That looks correct. What's not working about it?

Your wallet will ignore that that transaction ever happened and thus "return" the Bitcoin back to your wallet so that you can spend again. Of course, if the transaction does confirm, then the Bitcoin will be spent per that transaction.

BTW the terminal command is actually

That's a bad assumption to make. No software is perfect, no solution to scaling will be perfect.

A lot of the problems seem to stem from miscommunication and lack of communication between developers and miners. It seems that some miners have taken a grudge against the developers (all of them in general) for not consulting them when devising scaling solutions.

Your english is very hard to understand.

You have an error with your package manager. Something is broken about it, it cannot retrieve the necessary dependency packages of a package. This is not an issue with bitcoind or boost but rather an issue with your system. Google the error and you should be able to find a way to fix it.

Your question is hard to understand.

Running a full node is not the same thing has mining Bitcoin. Running a full node requires downloading the 100+ GB blockchain. Mining does not necessarily require that, you only need to do that if you are solo mining or operating a pool.

Running a full node will not earn you any money, you are not paid for the full node.

I can't find the transaction in any block explorer or on my own node. Given that it has been several weeks, it is safe to assume that the transaction has been dropped by the network and thus the Bitcoin has "returned" to your wallet. To actually be able to spend, you need to clear the unconfirmed transaction from your wallet. Right click the transaction in the transactions list and choose "Abandon transaction". If that option is not available, then you will have to start Bitcoin Core with the -zapwallettxes command line option.

A transaction can in fact have a parent transaction in the same block.

This may be helpful: https://bitcoincore.org/en/segwit_adoption/

Again, Bitcoin cannot be sent to email addresses. That is simply not how Bitcoin works. You should have gotten a ~30 character Bitcoin address beginning with a '1'. The transaction ID should be 64 characters. Both address and txid are safe to post publicly, no one can steal the Bitcoin just by knowing the transaction id or knowing the details of a transaction.

Bitcoin transactions are irreversible, you cannot cancel a transaction and send the Bitcoin back to the sender.