Yes. Use a computer that is capable of syncing the blockchain and use that to download and verify the entire blockchain. Then copy and paste the datadir (without the wallet.dat) to an external drive and use that external drive on your low power hardware.

Please post the armorylog.txt and dbLog.txt files (copy and paste their contents into pastebin and post the link to the paste here).

Yes. That transaction is now invalid and will be subsequently rejected from mempools now.

You need the raw transaction, not just the txid. I never got around to actually adding support txids or transaction signing.

Decode the raw unsigned transaction and make sure that the details of it are what you expect it to be.

There is no universal time for a transaction to be considered invalid or rejected. Once a valid transaction is created, it is always valid until a double spending transaction is confirmed. Anyone can rebroadcast a transaction, so what probably happened was that someone has a node which just constantly rebroadcasts transactions, and your original low fee one was thus rebroadcasted.

The reason that your second transaction has poor propagation is likely due to the first transaction having been rebroadcast and thus causing nodes to reject your second transaction as a double spend.

What do you mean by "processing"? Do you mean checking the validity of transactions and then relaying them? If so, that is called operating a full node. Full node operators are not paid for operating a full node. The only people who receive any payments from doing any sort of processing with Bitcoin are the miners.

That is not how ASICs work. You don't build an ASIC computer. ASICs are highly specialized machines. They usually cost somewhere in the range of thousands of dollars. Furthermore Bitcoin mining equipment in general consumes a lot of electricity. Unless you have very cheap electricity, mining will not be profitable.

---

If your post was just deleted, it was because it repeated something that was already said and added no new useful or on topic information to the thread.

This is your first problem. 0.93.3 is out dated, and because Armory and Bitcoin Core (a very important dependency) are both very hardware intensive software, you should not be using a 32bit install. In fact, Armory no longer provides 32bit packages. You should use the latest Armory from https://btcarmory.com/0.95.1-release/

You should be able to run
That should install the package and Armory should be able to use it. There shouldn't be anything else that you need to do.

It's back.

I cleared the database, so any old tokens will no longer work. If you need to lookup the details related to a token, please pm me.

Was your address from your blockchain.info wallet or from elsewhere? Were you trying to import its private key to blockchain.info?

Watch only means that the wallet does not have the private key for it (or it doesn't think it does, blockchain.info has many bugs and often does stupid things). There is no way to get the private key for a watch-only address in a wallet because the wallet doesn't have the key.

The way that the soft forks work is that it makes something previously valid invalid. This means that it is backwards compatible, old nodes won't reject stuff made with the new rules. However, that also means that something invalid under the new rules can still be valid under the old rules. If miners and nodes are still running nodes with the old rules, then they will accept those transactions and blocks as valid, but not the new nodes. This can cause a split in the network and potentially a blockchain fork, and just be a major pain to resolve.

The point of the 95% signalling is so that everyone knows that it is safe to use the new rules because the miners are promising that they will use the new rules when creating blocks. It ensures that nearly all miners will enforce the new rules which means that the likelihood for a chain split is much much lower.

There is no one singular way that allows you to compile all altcoins ever. Each one is a separate project with its own way of building it. There is no unified build system that every coin uses which somehow magically allows you to compile every single coin with the exact same set of commands.

It all depends on the project you are building, whether they forked off of Bitcoin Core or some other altcoin, and when that happened. Usually they have documentation in a doc/ folder which will tell you how to compile the software, but that documentation may be out of date because a lot of people don't know how to write documentation or know that they need to update it as things change.

If you want specific instructions as to how to compile the source code for a specific coin, then you need to tell us what that coin is and allow us to look at the source code because something that works on one altcoin may not necessarily work on the next.

Bitcoin Core does allow you to rebroadcast transactions. You use the debug console and use the sendrawtransaction command to send the transaction. Even if the transaction is in the mempool, it will be broadcast again.

As for transaction fees, again, Bitcoin Core supports dynamic transaction fees and allows you to choose your fee. When you send, there is a button labeled Choose next to the Transaction Fee label. Just click that and you get advanced options for transaction fees.

You should use any wallet that is listed here: https://bitcoin.org/en/choose-your-wallet. The website gives decent descriptions of the security and privacy of the wallet along with a brief description. The wallets listed here have to meet certain requirements in order to be listed. I highly recommend that you do not use blockchain.info (it isn't listed on that website for a reason). I highly recommend that you use Bitcoin Core if you are ok with running a full node (requires syncing the entire blockchain, which can take a while) or use Electrum if you don't want to deal with running a full node.

That is an issue with your wallet software, not with Bitcoin or anything else. Your wallet software is being confused by the double spends. Users here cannot help you with that, you will have to contact blockchain.info's support to have them fix it for you.

That it continuously fails is usually indicative of hardware issues. Bitcoin Core is very hardware intensive and can cause issues with RAM or the hard drive to become noticeable. Try running some hardware diagnostics on your computer to see if it finds any issues with your computer.

The way that getbalance works currently cannot check the balance of an individual address. However the whole accounts system in Bitcoin Core has been deprecated and is being removed, so you will probably be able to do that in a major release or two (after 0.14).

The accounts are the same as the Labels that you see in the Receiving Addresses list. By default, the account is blank, so you would type
in order to get the balance of all of your wallets.

For one address, you could assign it its own account by changing the label and callling
where <account> is the label you gave the address.

Because he can't. Almost no wallet allows you do make a CPFP transaction because that involves spending from an unconfirmed transaction. Given that he is using either Blockchain.info or Coinbase, he basically has no access to the private keys in order to even attempt an advanced method of making a CPFP transaction.

Secondly, I'm not sure how well a CPFP transaction would work for covering three ancestor transactions. Also, the fee for that would cost around 0.002 BTC because it has to cover 4 transactions of unconfirmed transactions.

The times that the block explorers report do not matter and are typically not reflective of the time that the transaction was actually made. Ignore that, all that matters here is the transaction id.

There are multiple problems with your transaction. First and foremost, your transaction spends from an unconfirmed transaction (I will call this Tx 1): https://blockchain.info/tx/0cca850d39a87be0c6e958049ede276cca19bebc8c68a809e3e3b5bd31b03a1f which spends from another unconfirmed transaction (I will call this Tx 2): https://blockchain.info/tx/3ffbe09b0967b52dbda5ef46995a420dae5c227a92bd3baecb2041842cf99b6e

Your transaction cannot confirm until Tx 1 confirms, and that cannot confirm until Tx 2 confirms. This is what is primarily preventing your transaction from confirming.

Tx 2 pays a very low transaction fee, only 35 satoshis/byte. The current recommended transaction fee is 160 satoshis/byte according to http://bitcoinfees.21.co/. Tx 1 and your transaction also pay fairly low transaction fees, only ~65 satoshis/byte.

Unfortunately all you can do is wait or ask a miner for help. For asking miners for help, you can contact the users Quickseller and macbook-air. You can also try using https://www.viabtc.com/tools/txaccelerator/ to "accelerate" your transaction.

With waiting, since you are the recipient, you want to constantly remind the Bitcoin network that those three transactions exist so that the sender does not scam you by double spending the Bitcoin so you should constantly rebroadcast the transactions (although rebroadcasting does not prevent double spending, it can make it harder to do so). To rebroadcast the transactions, get the raw transaction by appending ?format=hex to the blockchain.info URL's for each transaction. Then copy and paste everything you see in that page (should just be a blank page with a bunch of random looking letters and numbers, that's the hex code of the transaction) into https://blockchain.info/pushtx and push the transaction. Do that periodically (maybe once a day). Other people can and probably will also rebroadcast the transactions for you.

You can attempt the RBF transaction that I described in the post I linked to above. Note that this actually creates a second transaction which is considered a double spend, so the recipient may not like that, especially if it is an online service. Otherwise you can wait or ask miners for help.

There is no way to modify a transaction once it has been signed and sent. Any modification makes the transaction a new transaction entirely.