ScanTool v1.0.0

The main focus of this release was response time.

• Added multithreading for better efficiency and response times.
• Added a "caching" setting. This is a boolean value which can take the values true/false or on/off or simply 1/0. Caching speeds up response times for transactions that are in the cache and minimizes the number of requests that have to be made to the node. Since it caches the whole transaction when it gets a previous output, caching is likely to speed up responses even if the user never requests the same transaction twice. For example, if someone is requesting information about every transaction in a block, the system will cache all the transactions that contain previous outputs. No transaction will be requested from the node twice, so if two or more transactions have previous outputs from the same transaction, only the first of those will require a request to the node. The rest will be retrieved from the cache. Caution: There is currently no limit to the size of the cache. It is not recommended to run the application with caching turned on for long periods of time and/or under heavy use without monitoring memory. Caching should be considered to be in beta testing. In this release, it is turned off by default.
• Significant changes were made to the REST API v1. There are now 5 API calls called block, tx, input, output and current_block_height. The block and tx API calls return different JSON objects than before. See the REST API documentation for more information.
• A more accurate method is being used to convert floating point values to integers. This should prevent the application from returning incorrect output values.
• The web interface now has progress bars when loading blocks and transactions.
• The charts have been removed from the web interface in order to speed up response times. Charts could be re-introduced in a later release.