Josh Rickmar

Sort accounts internally by their account number.

2

When enumerated, accounts are now returned in increasing order by their account number. Fixes #23.

Creating transactions should not allow creating dust.

1

At the moment, dust outputs are not checked for when constructing a new transaction. At the very least, the send should fail. A nicer implementation would show an error next...

This should probably go somewhere in the Create Transaction view.

Make transaction inputs selectable when creating a transaction

2

There is a placeholder checkbox for this feature, but it is not implemented yet, and the checkbox does nothing.

The Wallet model class uses a Dictionary keyed by Account (numbers) to store account properties. When [used as an IEnumerable](https://msdn.microsoft.com/en-us/library/bb348449%28v=vs.110%29.aspx), the order is not defined. This can cause the ObservableCollection...

Right now, the System.String type is used for passphrases, the wallet seed, etc. This type is immutable and it is impossible (without unsafe) to clear it after it is finished...

Right now this is hardcoded as 1 block confirmation everywhere in the code. Instead, this should be user-selectable. Some kind of settings view could be added that enables changing this...

The intent is to only save transactions from the last 100 (coinbase maturity) blocks since these are needed to efficiently calculate a balance given any arbitrary number of confirmations, without...

The estimated fees in the account's transaction creation tab are always zero because this is unimplemented. Additionally, every created transaction uses a hardcoded fee of 1e4. The estimated fee should...