Fix version back to 0.7.4, update README.md.

Author: chappjc

README.md

@@ -3,56 +3,59 @@
 <!--- #[![release version](https://badge.fury.io/gh/chappjc%2Fdcrspy.svg)](https://badge.fury.io/gh/chappjc%2Fdcrspy) -->
 [![Build Status](http://img.shields.io/travis/chappjc/dcrspy.svg)](https://travis-ci.org/chappjc/dcrspy)
 [![GitHub release](https://img.shields.io/github/release/chappjc/dcrspy.svg)](https://github.com/chappjc/dcrspy/releases)
+[![Latest tag](https://img.shields.io/github/tag/chappjc/dcrspy.svg)
 [![ISC License](http://img.shields.io/badge/license-ISC-blue.svg)](http://copyfree.org)
-[![Gitter](https://badges.gitter.im/chappjc/dcrspy.svg)](https://gitter.im/chappjc/dcrspy?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)
 
 dcrspy is a program to continuously monitor and log changes in various data
 on the Decred network.  It works by connecting to both dcrd and dcrwallet
-and responding when a new block is detected via a [notifier registered with
+and responding to varioius event detected on the network via [notifiers registered with
 dcrd over a websocket][1].  Communication with dcrd and dcrwallet uses the [Decred JSON-RPC API][2].
 
-***Compatibility Notice*** - After Decred (i.e. dcrwallet and dcrd) version
-0.6.0, the notifications API was changed, requiring dcrspy to update it's
-notification handlers.  Practically, this means that for version 0.6.0 and
-earlier of Decred it is required to use the [compatibility release
+***Compatibility Notices***
+
+* After Decred (i.e. dcrwallet and dcrd) v0.6.0, the notifications API was
+changed, requiring dcrspy to update it's notification handlers.  Practically,
+this means that for version 0.6.0 and earlier of Decred it is required to use
+the [compatibility release
 "Millbarge"](https://github.com/chappjc/dcrspy/releases/tag/v0.6.0) or the
 [old-ntfns branch](https://github.com/chappjc/dcrspy/tree/old-ntfns), and for
 any Decred release *after* 0.6.0 use *at least* dcrspy v0.7.0, preferably
 [latest](https://github.com/chappjc/dcrspy/releases), or master. The version of
 dcrspy on master will use the new `version` RPC to check that the RPC server has
 a compatible API version.
+* After Decred v0.7.0, the getbalance RPC response was changed. For 
+Decred release 0.8.0 and builds of using dcrd commit
+[`f5c0b7e`](https://github.com/decred/dcrd/commit/f5c0b7eff2f9336a01a31a344a0bdb1572403e06)
+and later, it is necessary to use at least v0.8.0 of dcrspy.
 
 ## Types of Data
 
 The types of information monitored are:
 
-* Block chain data (from dcrd)
-* Stake and wallet information (from your wallet, optional).
-* Mempool ticket info (from dcrd)
-
-A connection to dcrwallet is optional. Only block data will be obtained when no
-wallet connection is available.
+* Block chain (from dcrd)
+* Stake and wallet (from your wallet, optional).
+* Mempool, including ticket fees and transactions of interest (from dcrd)
 
+A connection to dcrwallet is optional, but required for stake info and balances.
 See [Data Details](#data-details) below for more information.
 
-Transactions involving **watched addresses** may also be logged (using the
-`watchaddress` flag).  Watching for addresses receiving funds seems to be OK,
-but watching for sending funds from a watched address is experimental.
+Transactions sending to **watched addresses** may be reported (using the
+`watchaddress` flag).
 
 ## Output
 
 Multiple destinations for the data are planned:
 
-1. **stdout**.  JSON-formatted data is send to stdout. **DONE**.
-1. **File system**.  JSON-formatted data is written to the file system. **DONE**.
-1. **Database**. Data is inserted into a MySQL database. NOT IMPLEMENTED.
 1. **Plain text summary**: balances, votes, current ticket price, mean fees,
    wallet status. **DONE**.
-1. **RESTful API** over HTTPS. IN PROGRESS.
+1. **JSON (stdout)**.  JSON-formatted data is send to stdout. **DONE**.
+1. **File system**.  JSON-formatted data is written to the file system. **DONE**.
 1. **email**: email notification upon receiving to a watched address. **DONE**.
+1. **Database**. Data is inserted into a MySQL or MongoDB database.
+1. **RESTful API**.
 
 Details of the JSON output may be found in [Data Details](#data-details).  The
-plain text summary looks something like the following (_wallet data redacted_):
+plain text summary looks something like the following (_wallet data simulated_):
 
 ~~~none
 Block 35561:
@@ -61,6 +64,7 @@ Block 35561:
         Window progress:   138 / 144  of price window number 246
         Ticket fees:  0.0101, 0.0101, 0.0000 (mean, median, std), n=1
         Ticket pool:  42048 (size), 17.721 (avg. price), 745115.63 (total DCR locked)
+        Node connections: 49
 
 Wallet and Stake Info at Height 35561:
 - Balances
@@ -73,6 +77,7 @@ Wallet and Stake Info at Height 35561:
         mempool tickets:      0 (own),            6 (all)
         Ticket price:      22.663  |    Window progress: 138 / 144
         Wallet's price:     23.8100;  fee:   0.1940 / KiB
+          (Approximately N tickets may be purchased with the set fee.)
         Totals:        541  votes,     919.84 subsidy
                          1 missed,          1 revoked
 ~~~
@@ -208,22 +213,22 @@ dcrspy is functional, but also a **work-in-progress**.  However, I will try to k
 
 * Verify Go installation:
 
-      go env GOROOT GOPATH
+        go env GOROOT GOPATH
 
 * Ensure $GOPATH/bin is on your $PATH
 * Install glide
 
-      go get -u -v github.com/Masterminds/glide
+        go get -u -v github.com/Masterminds/glide
 
 * Clone dcrspy repo
 
-      git clone https://github.com/chappjc/dcrspy.git $GOPATH/src/github.com/chappjc/dcrspy
+        git clone https://github.com/chappjc/dcrspy.git $GOPATH/src/github.com/chappjc/dcrspy
 
 * Glide install, and build executable
 
-      cd $GOPATH/src/github.com/chappjc/dcrspy
-      glide install
-      go install $(glide nv)
+        cd $GOPATH/src/github.com/chappjc/dcrspy
+        glide install
+        go install $(glide nv)
 
 * Find dcrspy executable in `$GOPATH/bin`, and copy elsewhere (recommended).
 
@@ -233,7 +238,7 @@ folders.
 
 ## Updating
 
-First, update the repository:
+First, update the repository (assuming you have `master` checked out):
 
     cd $GOPATH/src/github.com/chappjc/dcrspy
     git pull
@@ -277,6 +282,7 @@ Application Options:
   -d, --debuglevel=        Logging level {trace, debug, info, warn, error, critical} (info)
   -q, --quiet              Easy way to set debuglevel to error
       --logdir=            Directory to log output (./logs)
+      --cpuprofile=        File for CPU profiling.
   -c, --cmdname=           Command name to run. Must be on %PATH%.
   -a, --cmdargs=           Comma-separated list of arguments for command to run. The specifier %n is substituted for block height at execution, and %h is
                            substituted for block hash.
@@ -333,7 +339,7 @@ debuglevel=debug
 ;cmdargs="127.0.0.1,-n,8"
 
 ; Monitor mempool for new tickets, displaying fees
-;mempool=true
+mempool=true
 ;mp-min-interval=4
 ;mp-max-interval=120
 ;mp-ticket-trigger=4

main.go

@@ -5,7 +5,7 @@
 //
 // Types of information monitored:
 //	1. Block chain data (from dcrd)
-//  2. Stake information (from your wallet)
+//  2. Wallet and stake information (from dcrwallet)
 //  3. mempool (from dcrd)
 //
 // See README.md and TODO for more information.
@@ -25,6 +25,7 @@ import (
 	"net"
 	"os"
 	"os/signal"
+	"runtime/pprof"
 	"strconv"
 	"strings"
 	"sync"
@@ -33,7 +34,6 @@ import (
 	"github.com/decred/dcrd/chaincfg/chainhash"
 	"github.com/decred/dcrrpcclient"
 	"github.com/decred/dcrutil"
-	"runtime/pprof"
 )
 
 const (

sample-dcrspy.conf

@@ -9,7 +9,7 @@ debuglevel=debug
 ;cmdargs="127.0.0.1,-n,8"
 
 ; Monitor mempool for new tickets, displaying fees
-;mempool=true
+mempool=true
 ;mp-min-interval=4
 ;mp-max-interval=120
 ;mp-ticket-trigger=4

version.go

@@ -10,8 +10,8 @@ type version struct {
 
 var ver = version{
 	Major: 0,
-	Minor: 8,
-	Patch: 0,
+	Minor: 7,
+	Patch: 4,
 	Label: "beta",
 	Nick:  "Fletch Lives"}