Version 0.9.4

README.md

@@ -8,17 +8,22 @@ Application is written in python, but for your convinience it is compiled into s
 ## Main application window
 ![1](./doc/dmt-main-window.png)
 
-## Steps to configure app
+## Steps to configure
 Broadcasting message about a masternode (but also checking of a masternode's status) requires you to have access to a working Dash daemon (dashd) with JSON-RPC enabled. This can be Dash-QT on your local network or Dash daemon working as your masternode - before you broadcast message about your masternode, you have to have its dashd running, so it can help you to broadcast message about itself.
 
 ### Enable JSON-RPC of dashd
 To enable dashd JSON-RPC, edit file dash.conf located in a subdirectory .dashcore (linux) and configure the following parameters:
-  - rpcuser=any_alphanumeric_string_as_a_username
-  - rpcpassword=any_alphanumeric_string_as_a_password
-  - rpcport=9998
-  - rpcallowip=127.0.0.1
-  - server=1
 
+    - rpcuser=any_alphanumeric_string_as_a_username
+    - rpcpassword=any_alphanumeric_string_as_a_password
+    - rpcport=9998
+    - rpcallowip=127.0.0.1
+    - server=1
+    - addressindex=1
+    - spentindex=1
+    - timestampindex=1
+    - txindex=1
+
 Restart Dash daemon after file modification to make the new parameters working.
 
 ### Configure Dash daemon connection in DMT
@@ -34,19 +39,47 @@ Click "Test connection" to check if RPC communication works as expected.
 
 ### Create masternode's configuration
 In the main window click the button "New" and fill the information:
-  - Name: masternode's name within your config
-  - IP: Masternode's IP address, used for inbound communication
-  - port: Masternode's TCP port number, used for inbound communication
-  - MN private key: if you don't have one, you can generate a new random by clicking "Generate new" button. For this process is used a function from a widely respected pybitcointools library of Vitalik Buterin.
-  - Collateral: BIP32 path of your collateral, holding 1000 Dash. 
+
+    - Name: masternode's name within your config
+    - IP: Masternode's IP address, used for inbound communication
+    - port: Masternode's TCP port number, used for inbound communication
+    - MN private key: if you don't have one, you can generate a new random by clicking "Generate new" button. For this process is used a function from a widely respected pybitcointools library of Vitalik Buterin.
+    - Collateral: BIP32 path of your collateral, holding 1000 Dash. 
 
-Now, click the "->" button on the right side of the "Collateral" edit box. This will read Dash address related to the BIP32 path entered earlier from your Trezor. On this step you should see a dialog asking for a PIN and a password, of course if such were configured on your Trezor.
+Now, click the "->" button on the right side of the "Collateral" edit box. This will read Dash address related to the BIP32 path from your Trezor. While this step you should see a dialog asking for a PIN and a password, of course if such were configured on your Trezor.
 
 The last information, you must provide is the Collateral transaction hash and index. 
 
 ### Broadcasting information about Masternode.
 To broadcast information about your Masternode, click the button "Start Masternode using Trezor". This step will cause  dialogs for Trezor PIN/password to show up and finally Trezor will ask you for broadcast-message signature. 
 
+### Transfering funds (version >= 0.9.4)
+Beginning with version 0.9.4 DMT you can transfer MN earnings. This works in a bit different way, than with other Dash wallets - DMT gives a user 100% control on which 'unspent transaction outputs' (utxo) he/she whishes to transfer. This eliminates the need of 'Coin control' functionality, implemented in some wallets. 
+
+"Transfer funds" window lists all UTXOs of a currently selected Masternode (mode 1) or all Masternodes in configuration (mode 2). By default, all UTXOs, not used as MN collateral are checked. MN collateral's UTXOs (1000 Dash) are not only unchecked but also hidden, just tu avoid unintentional sending funds tied to a collateral's UTXO and thus breaking MN. You can show those hiddedn entries by unchecking "Hide collateral utxos" option.
+
+To show up the "Transfer funds" window, click the "Tools" button. Then, from popup menu, which expands, choose:
+ - "Transfer funds from current Masternode's address" (mode 1)
+ - "Transfer funds from all Masternodes addresses" (mode 2) 
+
+![1](./doc/dmt-transfer-funds.png)
+
+Select all UTXOs you wish to include in your transaction, verify transaction fee and click the "Send" button. After signing transaction with your hardware wallet, app will ask you if you want do broadcast transaction to Dash network. 
+
+![1](./doc/dmt-transfer-funds-broadcast.png)
+
+### Signing message with hardware wallet
+To sign message with your hardware wallet click the "Tools" button and then select the "Sign message with HW for current Masternode's address" menu item. 
+This will show the "Sign message" window:
+
+![1](./doc/dmt-hw-sign-message.png)
+
+### Changing hardware wallet's PIN/passphrase configuration
+Click the "Tools" button and then "Hardware Wallet PIN/Passphrase configuration" item. This will show up the configuration window:
+
+![1](./doc/dmt-hardware-wallet-config.png)
+
+
 ### Comments
 This app has been tested on Mac and Windows 7 with Masternode working on Debian 8 (Jessie). There are many other possible  configurations, so it is also possible, that something will not work in your environment. If such thing happens, you can reach me at blogin[at]nullteq.com, so I'll try to help you.