Fix reorg issues

[electrum-server.git] / README.leveldb

diff --git a/README.leveldb b/README.leveldb
index ff08823..70c7626 100644 (file)
--- a/README.leveldb
+++ b/README.leveldb
@@ -8,17 +8,9 @@ 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. Run bitcoind.
+1. Run novacoind.
 
-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.
+Install version 0.4.4.6u5 or higher. Previous versions won't provide sufficient getblock/getblockbynumber functionality.
 
 __________________________________________________________
 
@@ -68,7 +60,8 @@ _________________________________
 5. enjoy!
 
 Once the server is synchronized, it will listen to ports, and the
-normal way to stop it is to type: ./server.py stop
+normal way to stop it is to use the 'stop' script. This script will
+wait until the database is closed.
 
 Other commands are available: 
 
@@ -79,8 +72,8 @@ Other commands are available:
 ______________________
 Troubleshooting:
 
-* if your server or bitcoind is killed because is uses too much
-memory, configure bitcoind to limit the number of connections
+* if your server or novacoind is killed because is uses too much
+memory, configure novacoind to limit the number of connections
 
 * if you see "Too many open files" errors, you may need to increase
 your user's File Descriptors limit. For this, see