X-Git-Url: https://git.novaco.in/?p=electrum-server.git;a=blobdiff_plain;f=README.leveldb;h=ff088237ca4cb1b91978b3535591ea0ef0a8adbe;hp=78d86a379ba6f6c8430378da5f248445f945c70a;hb=240db7c28d2e6a0d0078c42f81b2b110615e88c6;hpb=83aa330a5e99e8da75668fca5a0c94566747e3ee

diff --git a/README.leveldb b/README.leveldb
index 78d86a3..ff08823 100644
--- a/README.leveldb
+++ b/README.leveldb
@@ -4,18 +4,21 @@ Pruning nodes use a lightweight database to store address histories.
 Only unspent coins are kept in that database; spent outputs are
 pruned.
 
-
+As of November 2013 all public servers operate this way.
+Please see HOWTO.md for more detailled information. The following is a 
+short outline:
 __________________________________________________________
-1. patch and compile bitcoind.
+1. Run bitcoind.
 
-Install version 0.8 or equivalent.
-Patch it with the patch distributed with Electrum.
+Install version 0.8.5 or higher.
+There is no need to patch bitcoind anymore.
+You need to run it with the config option txindex=1 .
+If you have not previously done so, you may need to reindex the bitcoind blockchain
 
 Note: Even though Electrum's database uses pruning, you cannot use it
 with a ultra-pruning bitcoind (forthcoming in 0.9 or later).
 A full bitcoin node is required in order to know for each address 
 if it has been used. Pruning occurs only at the level of the Electrum database.
-txindex=1 however is *not* needed!
 
 __________________________________________________________