Those addresses are P2SH nested addresses. Armory will make those in the next version which will have those enabled.

You can't. Such addresses don't exist yet.

No, that is disabled because segwit is hardcoded to be disabled on mainnet for now. We will be releasing another version with segwit enabled soon.

Yes. That uses compressed keys and that is pretty much the only reason you would want to use it.

Many wallets already have segwit support built in but disabled by default (like Armory). You should expect most wallets to release new versions with segwit enabled in the next few weeks. Bitcoin Core will be adding support for bech32 addresses and the P2SH nested addresses soon in a minor version after we release 0.15.0.

The CPU has to do all of the work to verify the blocks as they are downloaded. It must hash the blocks and check the proof of work, hash the transactions in the block and compare that with the merkle root, lookup in a database to make sure that transactions are not spending previously spent inputs, etc. A lot of it is calculating hashes, which, given a large number of hashes, can be fairly computationally intensive.

It depends on the block. Bitcoin Core has checkpoints which mean that the block at a certain height must have a certain hash. Blocks prior to that will not have signatures validated. The recent checkpoint was block 250000 which means that for older nodes, they will begin checking signatures after block 250000. However for newer nodes, we introduced a thing called assumevalid which supersedes checkpoints (although checkpoints still exist). Assumevalid has a block hash specified. It is similar to checkpoints; any block in the chain prior to the assumevalid block (we have a best headers chain which has the assumevalid block in it) will have signature validation skipped. Blocks after the assumevalid block will have all signatures verified. The assumevalid block can be set with the -assumevalid=<hash> startup option. The default assumevalid block is updated every release.

Yes. There are more transactions in newer blocks which requires more hashing, and after the assumevalid block, all signature validation is done.

One of the bottlenecks is database flushing. To make syncing faster, you can increase the -dbcache=>n> parameter so more of the database is held in memory and does not need to be flushed to disk as often. You can also check the current block hash, and if you trust the block explorer you used, you can set the -assumevalid=<hash> option so that you will skip all signature validation up to the most recent block.

The paper backup that you made when you first made the Vault should contain your public keys. Retrieve them from there. If you don't have those, then you can generate them from the seeds that you have.

This topic has been moved to Trashcan.

Duplicate. Your other thread is here: https://bitcointalk.org/index.php?topic=2128207.0;topicseen#msg21260292

Bitcoin Core currently has no functionality to create Segwit addresses (either P2SH nested ones or bech32 ones) in the GUI. Thus all addresses you get from the GUI are non-segwit and anyone who sends to those will be making non-segwit outputs. The legacy Bitcoin addresses did not have their definitions change.

Server rebooted, database cleared. Should be working now.

Nothing prevents governments, ISPs, your school or work, etc. from blocking Bitcoin network connections. However Bitcoin is decentralized, there are no servers or clients, only nodes. So in order to "kill" Bitcoin, you would have to prevent every single node from connecting to any other node in the network. This would have to be a worldwide effort since Bitcoin nodes can be found all over the world.

Furthermore, Bitcoin does not necessarily have to rely on the internet. There are projects that are working on providing non-internet means of communication for nodes, such as Blockstream Satellite.

Are you hashing the number as a string? Is it in decimal or hex?

You must be hashing your number as bytes. Otherwise it will not be correct as you would be hashing a string.

No. There is only one blockchain.

Yes. They are also non-standard, and given that the majority of nodes and miners are enforcing segwit, those transactions are not actually anyone-can-spend.

Yes. Both BIP 148 and BIP 91 are irrelevant now.

Yes. It will check all transactions and blocks it knows of. If a transaction is in a block that has a specific descendant block (the assumevalid block), then signatures are not checked. Everything else is still checked. Note that using the bootstrap.dat torrent will be slower than syncing from p2p.

The transactions don't matter; what matters are the private keys. The transactions can always be recovered as they are in the blockchain, but your private keys cannot be recovered if you lose them. If you check block explorers for all of the addresses in your wallet and don't see any suspicious transactions, then you are fine and your coins are not stolen.

If you have a backup of your wallet file, then use that with your new install of Bitcoin Core and see if it works. If it does not, then please post the debug.log file. Don't use salvagewallet since it may actually make the problem worse (salvagewallet has been known to corrupt uncorrupted wallets. It is a last resort thing).

Every single full node (not just miners) fully verifies every single transaction it receives. It does the same for every block. Since blocks and transactions can be mostly validated in parallel, it really isn't all that slow. Furthermore, the entire blockchain is not rechecked for every block, nor does it need to be rescanned for every block. Node software has more efficient ways of checking up transaction by storing various data separately, e.g. maintaining a separate database for the UTXO set which is used for checking transaction validity. Furthermore transactions in new blocks don't need to be revalidated if you have already seen them in your mempool. So that saves validation time as well.

No, it does not.

When more people start using segwit and more segwit transactions have been made.

Yes. There were 6 segwit transactions in the first block after segwit's activation.

As more people begin using segwit, it will. We have also already seen at least one block larger than 1 MB.

In your wallet, go to whatever tab or page for "Receive Bitcoin" (usually named something like that). There you should be able to get a Bitcoin address.

Make a new paste on https://pastebin.com/ and post the link here.

Is Bitcoin Core fully synced? Is Armory fully synced? If not, you won't see the transaction until both are fully synced.

There are two main protocols used for getting block information, stratum and getblocktemplate. For either one, you have to connect to the url for a pool's stratum or getblocktemplate server. Then from there you follow the respective protocol to request data from the server.

Information on how to use the stratum protocol is found here: https://slushpool.com/help/manual/stratum-protocol
Basically you just open up a tcp connection and send it specific JSON data and you will get a reply. You can do this manually by using netcat.

Information on how to use getblocktemplate can be found here: https://github.com/bitcoin/bips/blob/master/bip-0022.mediawiki and https://github.com/bitcoin/bips/blob/master/bip-0023.mediawiki
Basically you just connect to the server and send it HTTP POST requests.

This topic has been moved to Trashcan.

Duplicate