We’ve just released GRIDNET Core version 1.1.0.
It is already available for download from right over here.
there were reports of ⋮⋮⋮ Core having troubles with synchronization with the current state of the ⋮⋮⋮ Decentralized State Machine. The situation should be now largely improved. We’ll be tweaking the performance in following days yet still, the overall stability seems solid.
we’ve added a very performance-wise efficient logging mechanism.
The location of the log file is reported as the node bootstraps. It may differ on-per node basis as the software attempts to write the most suitable location it would have write-access to. In general the path of the log-file should be in the form of:
C:\Users\**[USERNAME]**\AppData\Local\Temp\GRIDNETLog.txtfeel free to upload these logs right over here should you encounter any trouble. These logs never contain any kind of personal data, but for IP addresses.
Note that running the software does not require Administrative permissions on Microsoft Windows, you MAY want to grant it Admin Rights on first run through as it attempts to tweak some parameters of GPU-settings to ensure best performance of winning. It actually tries to tweak the maximum time interval an OpenCL Kernel is allowed to run. The time the kernel runs is tweaked dynamically based on your hardware specification.
we’ve added one more indicator seen above - [BQ] which indicated the current length of the block processing queue. Recall that [BQ] - stands for the current block-height. [Sync] - the current state of synchronization with the rest of the network. If you see ‘Low Connectivity’ sign - that means that you are currently connected with less than 3 nodes.
the caching sub-system of the ⋮⋮⋮ Decentralized Web-Anonymization service was rewritten entirely. It now supports lots of advanced statistics and improved performance and stability. You’ll be seeing utilities allowing you to get an insight of these internals soon enough.
lots of improvements the Decentralized User Interface update mechanics. Especially to how the update-packages are extracted and processed on Microsoft Windows, in a privileges-constrained environment - when not running as Administrator.
lots and lots of other minor tweaks