add txt

LIMX-SUPPORT · May 27, 2015 · a1df60e · a1df60e
1 parent 9150603
commit a1df60e
Show file tree

Hide file tree

Showing 3 changed files with 10 additions and 8 deletions.
diff --git a/README.md b/README.md
@@ -9,6 +9,8 @@ Copyright (c) 2014-2015 Dash Core Developers
 
 Copyright (c) 2014 Doge Core Developers
 
+Copyright (c) 2013 Dr Kimoto Chan
+
 Copyright (c) 2014-2015 LIMX Core Developers
 
 
@@ -26,7 +28,7 @@ Limecoinx Core:
 - Renamed client to identify with network from Satoshi to Core
 - Bumped protocol version to 70075
 - Masternode with 5000 LIMX
-- NEW Reward (50 LIMX /2 * 5 MIN)= 25 LIMX per Miner & 25 LIMX per Masternode or 40/10) 
+- NEW Reward = 40 LIMX per Miner/Pool & 10 LIMX per Masternode
 - NEW RPC PORT 8800 and NEW P2P Port Default 8886
 - Changed testnet address versions 
 - Defined BIP32 (HD) address versions

diff --git a/doc/guide-startmany.md b/doc/guide-startmany.md
@@ -4,7 +4,7 @@
 There are many ways to setup a wallet to support start-many. This guide will walk through two of them.
 
 1. [Importing an existing wallet (recommended if you are consolidating wallets).](#option1)
-2. [Sending 1,000 LIMX to new wallet addresses.](#option2)
+2. [Sending 5000 LIMX to new wallet addresses.](#option2)
 
 ## <a name="option1"></a>Option 1. Importing an existing wallet
 
@@ -56,9 +56,9 @@ Create a new wallet address for each MasterNode.
 
 Close your QT Wallet.
 
-### Send 14,400 LIMX to New Addresses
+### Send 5000 LIMX to New Addresses
 
-Just like setting up a standard MN. Send exactly 14,400 LIMX to each new address created above.
+Just like setting up a standard MN. Send exactly 5000 LIMX to each new address created above.
 
 ### Create New Masternode Private Keys
 
@@ -82,7 +82,7 @@ Copy the masternode private key and correspondig collateral output transaction t
 
 The masternode private key may be an existing key from [Option 1](#option1), or a newly generated key from [Option 2](#option2). 
 
-*Please note, the masternode priviate key is not the same as a wallet private key. Never put your wallet private key in the masternode.conf file. That is equivalent to putting your 1,000 LIMX on the remote server and defeats the purpose of a hot/cold setup.*
+*Please note, the masternode priviate key is not the same as a wallet private key. Never put your wallet private key in the masternode.conf file. That is equivalent to putting your 5000 LIMX on the remote server and defeats the purpose of a hot/cold setup.*
 
 ### Get the collateral output
 
@@ -95,7 +95,7 @@ Issue the following:
 Make note of the hash (which is your collaterla_output) and index.
 
 ### Enter your MasterNode details into your masternode.conf file
-[From the limecoinx github repo](https://github.com/darkcoin/darkcoin/blob/master/doc/masternode_conf.md)
+[From the limecoinx github repo](https://github.com/LIMX-SUPPORT/LimecoinX/blob/master/doc/masternode_conf.md)
 
 The new masternode.conf format consists of a space seperated text file. Each line consisting of an alias, IP address followed by port, masternode private key, collateral output transaction id and collateral output index, donation address and donation percentage (the latter two are optional and should be in format "address:percentage").
 
@@ -137,7 +137,7 @@ I usually confirm that remote is on the correct block by issuing:
 
 ```limecoinxd getinfo```
 
-And compare with the official explorer at http://explorer.limecoinxpay.io/chain/Limecoinx
+And compare with the a explorer at https://bchain.info/LIMX/
 
 ### Local
 

diff --git a/doc/masternode_conf.md b/doc/masternode_conf.md
@@ -16,7 +16,7 @@ mn3 127.0.0.4:18886 92Da1aYg6sbenP6uwskJgEY2XWB5LwJ7bXRqc3UPeShtHWJDjDv db478e78
 ```
 
 In the example above:
-* the collateral for mn1 consists of transaction http://test.explorer.limecoinx.fr/tx/2bcd3c84c84f87eaa86e4e56834c92927a07f9e18718810b92e0d0324456a67c, output index 0 has amount 5000
+* the collateral for mn1 output index 0 has amount 5000
 * masternode 2 will donate 33% of its income
 * masternode 3 will donate 100% of its income