What are the addresses 3ATq4854DnkFoAMhKP5FTUCeJeHXgvWjYK and 3DhDTgW6G5CFaqbtK2UFGBJFkQk6sGkC63 for? Whatever they are, your coins are associated with those addresses. If those are addresses from an exchange, then go to their respective exchanges and your coins will be there.

The wiki is outdated (it is always outdated).

Use the help command to get help. If you do help importmulti, it will show you the help for importmulti.

There are no such things as sending addresses. What Bitcoin Core calls sending addresses should really be called "Address book". You do not want to import those.

Your command should look something like this:

Brainwallets are really not that secure, especially if you thought of the password yourself (versus letting a computer generate one for you).

There is no standard for generating brainwallets, so it entirely depends upon how you created the brainwallet in the first place. What website or software did you use? How much of the password do you remember? Do you know potential candidates for the password? Was the brainwallet salted? If so, what was the salt?

There are a lot of things that you need to know that you may not know before you can even start trying to guess the password, and if you don't know or don't remember those things, then you probably will not be able to get your coins.

It is, and so is making an ICO.

It makes no difference because it will just be another ICO token among millions of other ICO tokens that no one has ever heard of or cares about.

The time it would take to mine X number of coins of a yet to be created altcoin is entirely dependent on the parameters you set for that altcoin. It will depend on the difficulty (the Proof of Work target parameter that you begin with), the target block rate, the hash algorithm, etc.

What exchanges have dinosaur names?

They are probably named whatever they are named because the creators thought it sounded cool.

Electrum has a mobile wallet but it may not have the same features as the desktop version.

If you are making a lot of large recipient transactions, I suggest that you do so on a computer and not on mobile as it will be easier to not make mistakes.

Yes.

If you are using the latest Bitcoin Core, then you should make a new backup every 1000 addresses. That is the default keypool size and you should make a new backup whenever the keypool runs out. This should be done regardless of HD or non-HD wallet, and even more so because you are using addwitnessaddress.

Also, you will need to unlock your wallet every 1000 addresses so that the keypool can be refreshed.

You should keep making backups regularly. What HD wallets do is that you can still use old backups and still generate the private keys that are not in the keypool at the time of backup.

The wallet contains a field which has the latest block height that the wallet is synced up to (as in it has the transactions for the wallet up to that block height). So when restoring, Bitcoin Core will know where it should begin rescanning the blockchain to get any new transactions.

Because OP is also using addwitnessaddress, older backups will not know about those witness addresses (the scripts themselves must be added to the wallet) and addwitnessaddress will need to be called again on every single address generated.

Use the importmulti command. It lets you import multiple addresses or private keys in the same command. Just craft the command in a text editor and copy and paste it when entering.

The name "Bitcoin Pay" is incredibly generic. From a quick google search, it seems like just another payment processor, not any particular approach to making Bitcoin transactions faster through layer 2 solutions or consensus rule changes. Can you perhaps provide a link to what you were looking at?

It certainly is possible. You would do that by reading through the block files byte by byte. Each block is preceded by the network magic bytes and then a compact size unsigned integer representing the number of bytes of the block. Then the block itself in the network serialization format.

Yes.

No. We have not moved to BIP 32 yet. Once we do, it will still be a few versions before the legacy wallets are phased out entirely.

0.15.x is greater than 0.14, so it is supported. However you should use the latest version of Armory anyways, 0.96.3 or 0.96.4 RC1.

0.96.3 has OSX binaries that I forgot to list on the website. You can get them from here: https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.3. You could also use 0.96.4 RC 1 which has a few bug fixes, available from here: https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.3.99

It should be fine, but the older versions have a variety of bugs and performance issues that were fixed in the new versions.

What are the addresses and txids of the top two transactions in that screenshot? Are those transactions confirmed or unconfirmed?

There are hundreds of open source libraries that you can use for doing Bitcoin things on websites and in other software. Just use Google and you will find them. There is no need to pay any money to use a library.

This thread is just becoming a place for people to spam. AFAICT, little to no meaningful discussion is happening here, so it is being locked.

A lot of the hate stems from either a fundamental misunderstanding of how segwit works (or misrepresentation of how it works) or from hatred towards the Bitcoin Core developers.

Segwit does multiple things. It essentially defines a new type of address which, when spent from, does not have its signatures in the txid calculation. It also redefines the block size limit as a thing called block weight. A lot of opposition is from this block weight re-definition. The block weight makes spending from segwit addresses cheaper (less block weight) than non-segwit addresses, and a lot of people did not like that for some reason. This re-definition also means that if more segwit addresses are being spent from, then transactions will take up less block weight and thus more transactions can fit in a block.

Segwit allows for second layer solutions like the Lightning network to exist more easily. The Lightning Network is what would allow for atomic swaps, not segwit itself.

Don't do that, you will get a different address. Compressed and uncompressed public keys result in different addresses. The private key has a flag that indicates whether it should use a compressed or uncompressed public key, so doing this will change the addresses that you get.

Instead of importing your private keys, you should sweep them. Create a new Electrum wallet and use the Wallet > Private Keys > Sweep function instead.

It could happen. I have seen it rewind a few hundred blocks before due to unclean shutdown.

That assumption is wrong. Core does not have an Android app and never has had one. Your wallet is written by different developers and uses different technology. The wallet file is completely incompatible with Bitcoin Core.

Bitcoin Wallet for Android uses Bitcoinj. If you are comfortable using the command line and installing JDK and maven packages, then you can use the bitcoinj wallet-tool to extract the data from your wallet file. The wallet-tool is part of the Bitcoinj repository here: https://github.com/bitcoinj/bitcoinj

You probably made the transaction without any fees so it was dropped by the network.

You can either update Bitcoin Core and allow it to sync and then send the Bitcoin. Or you can export the private key(s) and import them into Exodus.

To export the private keys, go to Help > Debug Window > Console and use the dumpprivkey <address> command where <address> is the address that you want the private key of. Do this for every address that has Bitcoin associated with it. Then import those private keys into Exodus.