You can just send the Bitcoin from your online wallet to the offline wallet. There is no other way to transfer the Bitcoin from one wallet to another.

Probably not. Setting up a node on low memory systems is quite difficult and can be very annoying to do. I would recommend that you have at least 4 GB RAM so that it sets up without any issues.

Pruned mode takes up ~5 GB IIRC. However you should probably allocate more disk space anyways just in case.

Directory.io is not a rainbow table nor is it an exploit or anything malicious. Their FAQ: http://directory.io/faq pretty much explains what the website is. TL;DR it's satire and a joke. The private keys are real but you can't actually lookup the private key for an address and you can't actually search through all of the private keys in the lifetime of the universe.

Every single Bitcoin private key is just an integer from 1 to 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140 (1.1579209 * 10^77 in decimal) inclusive. This means that technically, all private keys are known by everyone. However, there are so many private keys that finding one that has Bitcoin to spend is basically impossible, especially since private keys are generated randomly. With good random number generators, two people will never be able to generate the same private key simply because the keyspace is so unfathomably massive.

What directory.io does is they just figure out what number private keys the page you are looking at should be showing (as in which integers since a fixed number of keys fit per page) and displays those. They physically cannot have a database which stores all of the private keys and their respective addresses, it would be too computationally intensive to generate (and take way too long to do that) and the hard drive space for such a database is not available, it is too large. Furthermore, the odds of you stumbling upon a private key which has Bitcoin on it is extremely small too.

I have not been experiencing that problem. Are you sure it happens consistently?

If your machine can support 64-bit OSes, always get the 64-bit OS. There is no reason not to. Everything that can run on the 32-bit can run on the 64-bit OS, but not the other way around. There are also some things that are 64-bit only or run better on 64-bit OSes so by having a 64-bit OS, you can run those too.

Could you post the debug.log file?

You can also try using pywallet: https://github.com/jackjack-jj/pywallet. There are instructions at that link to get pywallet running, but it does require you to use the command line. You can run it with the web interface --web option and should be able to export the private keys from there.

There is no answer to these questions as that is not how Bitcoin works.

Bitcoin works by spending transaction outputs and creating transaction outputs. Each transaction output contains script, a partial mini program (i.e. you can't actually run it). When you spend Bitcoin, you are spending from a previous transaction output and creating another script as the input script. Both the output script and input scripts are combined to create a full mini program (i.e. one that actually runs). When a node receives the transaction, it runs that program and it must output true (well the symbols representing true, not the string itself) for the script to be valid. If the script is valid, then that input is validly spending the output.

One part of the standard script operations is a digital signature check. The output script of most outputs specifies that the input script must contain a public key and digital signature which is valid, and that the public key must hash to the hash specified in the output script. That hash is also encoded as your Bitcoin address. So when you spend, you create a digital signature using your private key which verifies to your corresponding public key and put those in the input script.

As you can see, there is nothing that your private key does except for creating the digital signature. There is no "key goes into effect" thing nor is any part of it sent anywhere when you spend or receive. The only thing that has to be sent that is related to your private key is the address as that is the hash of the public key that corresponds to your private key. There are no such objects as a Bitcoin; they are just values assigned to the output scripts.

Since everyone on the network uses the same digital signature algorithm that has a predefined private key range and public key range, there is no need for any keys to be registered anywhere or sent anywhere; everyone already knows them. As such, anyone can easily check all transactions in the blockchain to see if any public keys in input scripts hash to the hash specified by a Bitcoin address or if any hashes in the output scripts match the hash specified by a Bitcoin address.

The issue likely lies with the block data already on disk. Since you are not deleting any of it, the error will keep appearing as it hits the corrupted data repeatedly. Again, try deleting the blocks folder too in order to resync the entire blockchain. If you get the same error after doing that, then you likely have a hardware error.

You have ranked up. It seems that the time calculation on the site is off. The token is old and from before the activity update. The site data is not regenerated every time a token is used. It is only generated once. So since you generated the data before the activity period ended, you are served the data collected at that time.

You likely won't be able to set it up yourself to run locally. The site is a major pain to set up and have it work. I'm looking into why it is currently down.

Edit: It's back up now. You may need to use the www URL (www.bctalkaccountpricer.info) as the redirect does not seem to be working.

How are you using an ethereum wallet and are making Bitcoin transactions? Ethereum is a completely different cryptocurrency.

Did you mean to say Electrum?

You should make a new thread instead of hijacking this one. In that new thread, you should also post the armory log files, armorylog.txt and dbLog.txt. Lastly you need to make sure that Armory is looking for the blockchain in the right folder.

Can you post some of what comes before that? There should be lines saying which numbered file it is currently indexing. Otherwise your best bet would be to just delete the blocks and chainstate folders and resync the blockchain from scratch.

Yes.

Can you post the debug.log file?

The latest blk*.dat and rev*.dat files may not be enough. You will need to check the debug.log file to see which files it is actually failing at. You should also delete the chainstate folder so that you fully rebuild the databases.

You may need to resync the entire blockchain from scratch in which case you should just delete the blocks folder.

It's this one: https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.0.3-testing

You should upgrade to Armory 0.96 and Bitcoin Core 0.14.2. I recommend that you upgrade to the 0.96.1 testing build 3 as it fixes several bugs in 0.96 and is, IMO, more stable that 0.96.

No. The only way to do that is to create a transaction which spends all of your small transactions into one large output. If you aren't going to spend your Bitcoin in the near future, you can make such a transaction and just pay a very low transaction fee (and enable RBF just in case so that you can bump the fee if you have to). It will take a while to confirm, but you won't be paying as much in transaction fees.

Bitcoin transactions work by spending previous transaction outputs as inputs in a transaction, and creates transaction outputs. When you create a transaction, there is an option to preview the transaction. This will tell you how many inputs are being spent and how many outputs are being created. Since the transaction fee is based upon the size of the transaction in bytes (not the value being transacted), the more inputs you have, the larger the transaction will be and thus the greater your fee will be.

Staking a new address: 17kKQppUsngUiByDsce4JXoZEjjpvX9bpR

Signed message with previous staked address

Signed message with PGP key:

Signed message with new address