+# Release 1.9
+
+* The client connects to multiple servers in order to retrieve block headers and find the longest chain
+* SSL certificate validation (to prevent MITM)
+* Deterministic signatures (RFC 6979)
+* Menu to create/restore/open wallets
+* Create transactions with multiple outputs from CSV (comma separated values)
+* New text gui: stdio
+* Plugins are no longer tied to the qt GUI, they can reach all GUIs
+* Proxy bugs have been fixed
+
+
+# Release 1.8.1
+
+* Notification option when receiving new tranactions
+* Confirm dialogue before sending large amounts
+* Alternative datafile location for non-windows systems
+* Fix offline wallet creation
+* Remove enforced tx fee
+* Tray icon improvements
+* Various bugfixes
+
+
+# Release 1.8
+
+* Menubar in classic gui
+* Updated the QR Code plugin to enable offline/online wallets to transmit unsigned/signed transactions via QR code.
+* Fixed bug where never-confirmed transactions prevented further spending
+
+
+# Release 1.7.4
+
+* Increase default fee
+* fix create and restore in command line
+* fix verify message in the gui
+
+
+# Release 1.7.3:
+
+* Classic GUI can display amounts in mBTC
+* Account selector in the classic GUI
+* Changed the way the portable flag uses without supplying a -w argument
+* Classic GUI asks users to enter their seed on wallet creation
+
+
+# Release 1.7.2:
+
+* Transactions that are in the same block are displayed in chronological order in the history.
+* The client computes transaction priority and rejects zero-fee transactions that need a fee.
+* The default fee was lowered to 200 uBTC per kb.
+* Due to an internal format change, your history may be pruned when
+ you open your wallet for the first time after upgrading to 1.7.2. If
+ this is the case, please visit a full server to restore your full
+ history. You will only need to do that once.
+
+
+# Release 1.7.1: bugfixes.
+
+
# Release 1.7
* The Classic GUI can be extended with plugins. Developers who want to
1. user creates an unsigned transaction using the online (watching-only) wallet.
2. unsigned transaction is copied to the offline computer, and signed by the offline wallet.
3. signed transaction is copied to the online computer, broadcasted by the online client.
-
-* Raw transactions can also be loaded/signed/broadcasted via the GUI.
+ 4. All these steps can be done via the command line interface or the classic GUI.
* Many command line commands have been renamed in order to make the syntax consistent with bitcoind.