It's actually because the block at the difficulty adjustment only looks at the difficulty of the block before it since we assume (for mainnet) that all blocks in an interval are all the same difficulty. However on testnet the difficulty can be one, so if the last block in the previous interval has a difficulty of 1, then the next interval will do that too. I have edited my post to reflect this.

The difficulty will reset to 1 if the time since the last block is more than 20 minutes. There is no stipulation that after a difficulty reset block that the next block must be the normal difficulty; if the next block is more than 20 minutes after the current block, then it can also have a difficulty of 1.

For blocks that are found within 20 minutes of each other, the block's difficulty will be the same as the difficulty of the last block in the difficulty interval whose difficulty was not 1 OR the difficulty of the first block in the difficulty interval. This behavior is defined here: https://github.com/bitcoin/bitcoin/blob/master/src/pow.cpp#L32.

The way that the difficulty retarget works is that, at the beginning of the new difficulty interval, the difficulty of the first block in that interval takes the difficulty of the last block in that interval and multiplies that by the time it took to mine the 2016 blocks and then divides it by the target time. The result is then clamped to be at least 1. Since this is based upon the difficulty of the last block in the previous interval, if that block is difficulty 1, then the next interval will also have a difficulty of one.

So what we are seeing here is that the last block in the interval is found 20 minutes after the block before it so it has a difficulty of one. Because the next block adjust the difficulty and it only looks at the block before it (which is difficulty 1), the difficulty of the next interval is 1. So the next 2016 blocks are mined at difficulty 1, and the difficulty then slowly adjusts up again.

Edit:

I was slightly wrong. Fixed that.

If the wallet.dat file is fully or partially overwritten, no amount of salvagewallet, pywallet, or any other recovery tool is going to help. The BDB file format is probably corrupted so most tools won't be able to open it. The data is gone; you can't get it back. The only viable recovery strategy here is to find a backup of that wallet file and restore from the backup.

You should install the offline bundle which you can get from https://github.com/goatpig/BitcoinArmory/releases/tag/v0.93.3. The offline bundles contain all of the packages that Armory depends on so those will be installed as well.

Have you installed all of Armory's dependencies?

Please follow the build instructions at https://btcarmory.com/docs/building/. It will give you the commands to run and the dependencies that you need to install.

The encryption used in Bitcoin Core is not a wallet file encryption. It does not encrypt the whole file. Rather it encrypts individual keys and stores those encrypted keys. So only the keys are encrypted, and they have a record type of ckey. This individual key encryption is what allows you to get new addresses and see your transactions and wallet balance even when your wallet is not unlocked.

None. Wallets are not decrypted or encrypted during the salvage wallet process; there is no need to do that.

The .bak files are backup files that are produced before salvagewallet begins the actual salvage. The .bak files are a copy of the original wallet file.

So long as segwit2x uses the same transaction and block formats, Armory will be able to work with Segwit2x nodes. Note that if the signatures scheme is changed like Bitcoin Cash did, then Armory will not be able to send.

Did the transaction you just create spend from those funds? If so, that means that those funds are now unconfirmed because they are returned as change to you in the transaction you just made.

If you click on Send Bitcoins from the Wallet Properties dialog, you will only be spending from the Bitcoin in that specific wallet. If you have other wallets, then you will not be able to spend from those other wallets.

You can also enable Expert mode and use the Coin Control feature when in the Send Bitcoins dialog to choose the coins that you want to spend.

What do you mean by under reported? Do you not see transactions that you should? Or does the total balance not match what you think it should be? Or when you try to spend you can't spend all of your coins? Or something else?

This topic has been moved to Trashcan.

Duplicate

Just reinstall Bitcoin Core. If the software is still installed on your computer, then it will just overwrite those binaries. If it isn't then it will install new ones.

There is no "network provider". There are only 2 participants in a lightning channel. Only those two participants can fund the channel. So no, you cannot "invest" in a payment channel.

Deploying on your own servers is not going to help you at all. The problem isn't with the servers but rather the software itself. The software itself has many bugs and problems.

You cannot drag and drop files here. You can't upload files to this forum. Instead open the log files in a text editor and copy and paste the contents to a new paste on http://pastebin.com/ and post the link to that paste here.

The Bitcoin Core wallet is a Berkeley DB database. It consists of key-value pairs.

Salvage wallet calls BDB DB->verify() function with the DB_AGGRESSIVE flag which will result in it outputting any and all key-value pairs that it can find, even ones that were deleted or corrupted. This means that -salvagewallet can find key-value pairs that normally wouldn't be in your wallet.

These key value pairs are then scanned. Anything that has a key that begins with the strings key, ckey, wkey, or mkey will be pulled out and written to a new database file. It is important to note that those records are not checked for consistency. They are simply passed through. If the rest of the key (which usually contains a public key) or the value of the pair (which may contain the private key) is corrupted, salvagewallet will not detect it and will not be able to do anything to fix it. salvagewallet is only for recovering key type key-value pairs from a badly corrupted wallet. It cannot help you if the public or private keys themselves are corrupted. Lastly, using savagewallet on an non-corrupted wallet may result in that wallet becoming corrupted.

DB cleared and server rebooted. It should work now.

Are you using bitcore or Bitcoin Core? If the latter, please do not refer to it as bitcore as Bitcore is an entirely separate software that is based on Bitcoin Core.

Take the decrypted private key from your paper wallet. Import it using

That's not how Bitcoin or paper wallet work. You don't export Bitcoin and addresses are mapped to private keys (of which a paper wallet is just one private key) so you can't possible get a different address. You are importing private keys, not sending Bitcoin anywhere.

Yes, the wallet.dat contains all of your private keys. They are not in a human readable format as that would be pointless.

You should not see any private keys in that at all whatsoever.

Go to the Bitcoin Core data directory and delete all of the files in there. If you delete your wallet.dat file, you will be deleting your private keys and they are not recoverable unless you have a backup.

The wallet.dat contains the private key for that address, unless you had imported just the address. You don't need to import private keys for everything, Bitcoin Core will generate private keys and their corresponding addresses for you.

Yes,

It depends on your machine. It can take anywhere from several hours to several days.