Bitcoin version 0.9 is released
-
It’s got updates to receive coins (BIP 70) and coin control and various other fixes and enhancements.
Read more @
https://bitcoinfoundation.org/blog/?p=541
Downgrading warnings
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).Running the old release with the -reindex option will rebuild the chainstate
data structures and correct the problem.Command-line options:
- New option: -nospendzeroconfchange to never spend unconfirmed change outputs
- New option: -zapwallettxes to rebuild the wallet’s transaction information
- Rename option ‘-tor’ to ‘-onion’ to better reflect what it does
- Add ‘-disablewallet’ mode to let bitcoind run entirely without wallet (when
built with wallet) - Update default ‘-rpcsslciphers’ to include TLSv1.2
- make ‘-logtimestamps’ default on and rework help-message
- RPC client option: ‘-rpcwait’, to wait for server start
- Remove ‘-logtodebugger’
- Allow `-noserver` with bitcoind
-
OK, 0.9 is better. I need copy it to FTC.
-
Bitcoin-cli
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.I don’t think this is a good idea. It was convenient to keep server & client in one executable.
What comes to other changes, the Coin Control was available for almost a year in non-official releases, so payment requests (BIP70) is the only interesting functionality added.
-
Next target , 0.9. I think after two months