His account is proxybanned which means that he is accessing the forum from an IP address that is considered evil (that IP address was used to do evil things before like DoS attacks, spamming, having banned accounts, etc.). Such IPs are usually Tor exit nodes or proxies.

The only way around it is to pay the fee.

No, that is the average block time that we want.

If by transaction speed you mean confirmation time, then changing that will effect confirmation time because it effects the block time. Note that changing that does not guarantee that blocks will be found every 6 seconds, it only says that the average time in between blocks is 6 seconds.

You will need to change the maximum proof of work target (which thus decreases the minimum difficulty). The proof of work target is what actually regulates block times.

Your genesis block is invalid; it probably does not have a valid proof of work. You will actually need to mine your genesis block which you can easily do by adding a while loop to the genesis block creation code (and a few other lines to check the PoW).

If the sender is asking you to send him money so that he can send you money, then you are being scammed.

If you has access to your blockchain.info wallet, then he can take all of your coins.

I think you are being scammed.

Yes, you can use Bitcoin Core (any version) without doing make install. Just using make is sufficient to build the binaries. The binaries themselves are src/bitcoind, src/bitcoin-cli, and src/qt/bitcoin-qt.

Install openssl and run this command:


You should get output that looks like this:

The hex under pub is what you put for pszMainKey. The hex under priv is the private key. Keep that somewhere safe. When you enter the hex, make sure you remove the colons ( and the line breaks.

---

Note that the alert system has a number of DoS vulnerabilities and was removed from Bitcoin.

We're pretty close. It will likely be in the next major release (0.17) but there is no guarantee. Basically it's just whenever this PR: https://github.com/bitcoin/bitcoin/pull/11383 gets merged.

It means that 1000 keys have been pre-generated and added to your wallet. If you restore a wallet backup, any keys that you had used that weren't marked as used in your backup are likely still in your backup's keypool. So when you restore it, the keys are already there and it knows to look for transactions related to those keys.

Even though Bitcoin Core uses BIP 32 HD wallets, it is not guaranteed that the software will be able to find all of your transactions if they keys are not in the keypool. Thus it is better to have a larger keypool to make sure that all transactions are caught during a restore.

The keypool also lets you get keys (specifically public keys and their associated address) without having to unlock your wallet. If there were no keypool, every time you wanted a new address, you would need to unlock your wallet in order for new keys to be added.

In theory yes since less data needs to be loaded.

The keypool automatically regenerates keys when it is able to.

If you use more than 20 keys and then you restore an old backup, Bitcoin Core may not catch all of your transactions during a rescan. It is advised to keep the keypool larger than what you expect to use between backups.

Using BIP 32 does not mean that they are using Bitcoin Core.

IIRC Bitfinex, Bitstamp, and Kraken use BitGo to store their Bitcoin. They interact with Bitgo via an API. Other exchanges may be doing the same. They may also be rolling their own wallet software. Some may also be using Bitcoin Core.

Some exchanges also use Armory to store their Bitcoin.

Presumably when you request an address, you send a request to the web server which then sends a request to some other server which has the addresses to get the address that it then serves to you.

---

How exchanges are actually setup is generally not known to people outside of the exchange. This sort of security critical infrastructure is not revealed to the public so that they can get some security through obscurity.

Most wallets are open source, and the ones that aren't are ones that you should not use.

So because they are open source, you can go and read through the code yourself and make sure that it is secure. Then you can compile the wallet from source (so that you don't have to trust any distributed binaries) so that you know that the source code that you read is exactly the code that went into the wallet program that you are running.

Hmm.

Try adding this line to DB_CONFIG

First of all, MAX_MONEY is not what controls the total money supply; that is governed by the block reward halvings which is in the function GetBlockSubsidy.

---

You can just create your genesis block to have a large amount of coins and then make sure that you insert that transaction into the UTXO set when the genesis block is loaded.

This topic has been moved to Trashcan.

Duplicate thread

You are connected to a lot of misbehaving peers.

Stop Bitcoin Core and go to your data directory. Delete the file named peers.dat. Start Bitcoin Core again.

---

It does look like you are currently syncing though, so that's good.

You can have all 3 different address types in each wallet.

Multiwallet is still in 0.16. It is still just an RPC only thing, no GUI support yet.

Older versions are not "simpler". They may actually be harder to understand as not everything is named logically or commented well. With newer versions of the code, most things are well commented and named appropriately. Things that aren't are typically shared with older versions so using an older version really won't help.

Also newer versions have documentation that makes it easier to build and do other common things with the software.

80 bits of security is not considered secure. It is within the realm of practical. In cryptography terms, taking 2500 years to brute force something is weak. There's a reason you don't see anything with less than 128 bits of security actually in use for applications that need serious security.

This error is because each wallet.dat file is opened in the same BDB environment. The entire environment has a limited number of database locks, and it seems like 333 wallets hits that number of database locks. Of course, if you are actually receiving transactions, I think you will run into more problems even with 332 wallets since database locks are required in order to write data to the wallets.

In the Bitcoin Core data directory, create a file named DB_CONFIG. Put the following lines in that file:
That will increase the number of available locks by tenfold (was 40000, no 400000) which will let you open 10 times more wallets (assuming you have enough memory), in theory. Once you run out of locks again, just keep increasing those two numbers.

Yes. That is normal.

Bitcoin Core requires the entire blockchain, which currently takes up ~170 GB of disk space. The entire blockchain must be downloaded and validated. This means that you need to have a fast internet connection and a fast processor in order to be able to download the blockchain and process blocks quickly. Furthermore, while validating blocks, Bitcoin Core will need to read many things from the hard drive, and write many things to the hard drive. So a slow hard drive is going to make the sync take even longer.

There are likely 3 things that are causing you to have a slow sync time. Firstly, your laptop has a mechanical hard drive (that's what HDD means). A mechanical hard rive has moving parts and because it has moving parts, it is slow. Thus this is a bottleneck that will slow down your sync time because it takes longer to read and write data to and from the mechanical hard drive.

Secondly, you are using a laptop, which means that you are likely using a WiFi connection. WiFi can be slow. It depends a lot on any interference, the materials between your laptop and the router, and the router that you are using. It's likely that your WiFi connection is not all that fast and thus syncing will take a longer time. Also, WiFi means that there can be more data loss and corruption, so it will take longer for the networking protocols to either resend the data or recover it.

Lastly, you are using a laptop, which means that you are likely using a slow processor. Generally Intel Core i5's are decent, but it depends on what kind of processor you have. Many laptop processors, even if they are Core i5 or Core i7, are very low powered because laptops need to have lower powered components in order to have a better battery life. This means that your laptop could be running a low powered processor which is slowing down the sync as it cannot process blocks quickly.

It does for everyone using Bitcoin Core. It really depends on the computer that you are using. For some people, they can be synced in 6 hours. For others, it takes weeks. But for everyone who uses Bitcoin Core, there is always a period of waiting for it to sync when you first get started.

No, don't do that. It absolutely is not recommended to do that. The USB protocol and the USB connection is not very fast and not very good for transferring large amounts of data without some corruption. Storing the Bitcoin Core data on an external drive is a good way to have it corrupted. There have been many more cases of people's Bitcoin Core data directories being corrupted routinely when using an external drive than when using an internal drive.

Don't use web wallets. If you want to use a wallet that does not have to do this kind of syncing, use a wallet like Electrum. Don't use web wallets.

Why did you use BItcoin Core 0.8? Everything that is in 0.8 is available in the most recent release of Bitcoin Core (and the master branch). You should use those instead. Those also include things such as better cross compilation, increased performance, and many security and bug fixes.