Bitcoin Core version 0.9.0 is now available from: This is a new major version release, bringing both new features and bug fixes.Please report bugs using the issue tracker at github: If you are running an older version, shut it down.Wait until it has completely shut down (which might take a few minutes for older versions), uninstall all earlier versions of Bitcoin, then run the installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux).If you are upgrading from version 0.7.2 or earlier, the first time you run 0.9.0 your blockchain files will be re-indexed, which will take anywhere from 30 minutes to several hours, depending on the speed of your machine.On Windows, do not forget to uninstall all earlier versions of the Bitcoin client first, especially if you are switching to the 64-bit version.New in 0.9.0 is the Windows 64-bit version of the client.There have been frequent reports of users running out of virtual memory on 32-bit systems during the initial sync.

Because of this it is recommended to install the 64-bit version if your system supports it.NOTE: Release candidate 2 Windows binaries are not code-signed; use PGP and the SHA256SUMS.asc file to make sure your binaries are correct.bitcoin inr live chartIn the final 0.9.0 release, Windows setup.exe binaries will be code-signed.bitcoin miner software comparison0.9.0 drops support for older Macs.dogecoin value todayThe minimum requirements are now: The 'chainstate' for this release is not always compatible with previous releases, so if you run 0.9 and then decide to switch back to a 0.8.x release you might get a blockchain validation error when starting the old release (due to 'pruned outputs' being omitted from the index of unspent transaction outputs).bitcoin kaufen per kreditkarte

Running the old release with the -reindex option will rebuild the chainstate data structures and correct the problem.Also, the first time you run a 0.8.x release on a 0.9 wallet it will rescan the blockchain for missing spent coins, which will take a long time (tens of minutes on a typical machine).bitcoin memory poolTo reduce confusion between Bitcoin-the-network and Bitcoin-the-software we have renamed the reference client to Bitcoin Core.armory bitcoin open sourceOn OP_RETURN: There was been some confusion and misunderstanding in the community, regarding the OP_RETURN feature in 0.9 and data in the blockchain.This change is not an endorsement of storing data in the blockchain.The OP_RETURN change creates a provably-prunable output, to avoid data storage schemes -- some of which were already deployed -- that were storing arbitrary data such as images as forever-unspendable TX outputs, bloating bitcoin's UTXO database.

Storing arbitrary data in the blockchain is still a bad idea; it is less costly and far more efficient to store non-currency data elsewhere.For 0.9.0 we switched to an autotools-based build system instead of individual (q)makefiles.Using the standard "./autogen.sh; ./configure; make" to build Bitcoin-Qt and bitcoind makes it easier for experienced open source developers to contribute to the project.Be sure to check doc/build-*.md for your platform before building from source.Another change in the 0.9 release is moving away from the bitcoind executable functioning both as a server and as a RPC client.The RPC client functionality ("tell the running bitcoin daemon to do THIS") was split into a separate executable, 'bitcoin-cli'.The RPC client code will eventually be removed from bitcoind, but will be kept for backwards compatibility for a release or two.The behavior of the walletpassphrase RPC when the wallet is already unlocked has changed between 0.8 and 0.9.

The 0.8 behavior of walletpassphrase is to fail when the wallet is already unlocked: The new behavior of walletpassphrase is to set a new unlock time overriding the old one: This release contains a few fixes for transaction ID (TXID) malleability issues: This release drops the default fee required to relay transactions across the network and for miners to consider the transaction in their blocks to 0.01mBTC per kilobyte.Note that getting a transaction relayed across the network does NOT guarantee that the transaction will be accepted by a miner; by default, miners fill their blocks with 50 kilobytes of high-priority transactions, and then with 700 kilobytes of the highest-fee-per-kilobyte transactions.The minimum relay/mining fee-per-kilobyte may be changed with the minrelaytxfee option.Note that previous releases incorrectly used the mintxfee setting to determine which low-priority transactions should be considered for inclusion in blocks.

The wallet code still uses a default fee for low-priority transactions of 0.1mBTC per kilobyte.During periods of heavy transaction volume, even this fee may not be enough to get transactions confirmed quickly; the mintxfee option may be used to override the default.Thanks to everyone who contributed to this release:By the end of this tutorial, you'll see the first block on the Bitcoin blockchain, created by Satoshi Nakamoto.You'll also see how Bitcoin Core stores blocks on your disk.The first block on the Bitcoin blockchain—block 0—is called the Genesis Block.According to the timestamp in the block header, it was mined on 3 Jan 2009 at 18:15:05 UTC, although (as you'll learn) it contains more proof of work than we'd expect and the mining was only started on January 3rd.Let's take a look at it on the disk of your computer by running the following commands: The cd command changes your directory into the Bitcoin Core block data directory.

The hexdump command above displays the first 255 bytes of the file.It should look like this: The output has three columns: The left side is the byte count; it starts at zero and increases by 16 bytes on each line except the last.The middle part is each byte with a space between it and the next byte.Bytes are represented here in hexadecimal which takes two characters to represent a single byte.When we refer to byte sequences below, we'll use the common prefix of 0x.For example, the first byte in the output is 0xf9.On the right is the ASCII text representation of the hexadecimal data.Bytes that don't map to displayable ASCII are shown as periods.Almost none of the data in the blockchain is ASCII, but Nakamoto left us a surprise here (see below for details).Note the first four bytes, 0xf9beb4d9.This is called "Bitcoin's magic number", although it isn't really magical.It's just four arbitrary bytes chosen by Nakamoto as a byte sequence otherwise unlikely to appear in a Bitcoin datastream.

In the block data files, these bytes identify the start of a new block but they aren't part of the block themselves.These bytes also start each message in the Bitcoin peer-to-peer network protocol to help clients tell when one message ends and another begins.You'll note that the early part of the block contains many zero bytes (0x00).That's because the Genesis Block, unlike every other Bitcoin block, doesn't reference a previous block—it just references a long string of zeroes.This is truly the beginning of the Bitcoin blockchain.Finally, in the ASCII text section, you'll see the message Nakamoto left us: This was part of a special field in the special first transaction of a block, called a coinbase transaction.In Nakamoto's day, this field allowed miners to include up to 100 bytes of arbitrary data in each block they made.Today, that's been reduced to 97 bytes, but still most miners include a message of some sort in every block they make.

Nakamoto's message is especially important.It's the actual headline (although slightly garbled) of a real newspaper, the Financial Times, from the indicated date.This message, which may also express some of Nakamoto's frustration with the pre-Bitcoin financial system, provides extremely strong evidence that Nakamoto couldn't have mined his block earlier than the morning of January 3rd.(Based on the second block on the blockchain, dated January 8th, it's likely that Nakamoto didn't actually finish mining the Genesis Block until a few days later.)Why is this important?We also know that Nakamoto announced that the Bitcoin software was available on the 8th, and that there was another notable user (cryptographer Hal Finney) a few days later, so the proof that he didn't start mining until the 3rd shows that Nakamoto didn't attempt to mine all the early blocks himself in an attempt to create some sort of Ponzi scheme.If you want to see more of the blockchain, replace the number 255 in the command above with a higher number—but beware, the blockchain is pretty boring for its first few ten thousand blocks.