X-Git-Url: https://git.novaco.in/?p=electrum-server.git;a=blobdiff_plain;f=README.leveldb;h=ff088237ca4cb1b91978b3535591ea0ef0a8adbe;hp=036f63c115ae078b3457e3716c4661f257dd8c76;hb=4ce69b7ea24ead59ebbcc7ed335ea9762ae3724b;hpb=645b967079a4ed001009f1210dea4295fae9c149

diff --git a/README.leveldb b/README.leveldb
index 036f63c..ff08823 100644
--- a/README.leveldb
+++ b/README.leveldb
@@ -4,17 +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 pruning bitcoind. 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.
+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.
 
 __________________________________________________________