Readme update.

README.md

@@ -9,16 +9,17 @@ Gav Wood, 2014.
 secp256k1 implementation: https://github.com/sipa/secp256k1.git
 Expects secp256k1 directory to be in same path as cpp-ethereum.
 
-(NOTE: secp256k1 requires a development installation of the GMP library, libssl and
-apparently libcrypto++.)
+(NOTE: secp256k1 requires a development installation of the GMP library, libssl and libcrypto++.)
 
-A decent C++11 compiler (I use GNU GCC 4.8.1) and a recent version of Boost (I use version 1.53).
+libcrypto++, version 5.6.2 or greater (i.e. with SHA3 support). Because it's so recent, it expects this to be built in a directory libcrypto562 in the same path as cpp-ethereum.
+
+A decent C++11 compiler (I use GNU GCC 4.8.1) and a recent version of Boost (I use version 1.53) and leveldb (I use version 1.9.0).
 
 CMake, version 2.8 or greater.
 
 On Ubuntu:
 
-	sudo apt-get install libgmp3-dev libcrypto++-dev libssl-dev libboost-all-dev cmake
+	sudo apt-get install libgmp3-dev libcrypto++-dev libssl-dev libboost-all-dev cmake libleveldb-dev
 
 ## Building
 
@@ -31,7 +32,5 @@ On Ubuntu:
 
 Read CodingStandards.txt thoroughly, before making alterations to the code base.
 
-Do *NOT* use an editor that automatically reformats whitespace away from astylerc or
-the formating guidelines as describled in CodingStandards.txt. Your contributions will be
-refused and your commits will be reversed.
+Do *NOT* use an editor that automatically reformats whitespace away from astylerc or the formating guidelines as describled in CodingStandards.txt. Your contributions will be refused and your commits will be reversed.