GRIDNET Core 1.5.5 Release Notes

Introduction

Download URL: here

PRELUDE: all the screen snippets found below were taken from our YouTube LIVE development streams and were discussed in detail on our Discord server (LIVE-DEVELOPMENT section) the moment it was implemented. If you are passionate about computers and decentralization, you definitely want to join our ever growing Discord server.

These Release Notes come with the following supplementary material:

GRIDNET Core 1.5.5 emerged from an urgent need to address critical network issues, particularly a problematic block that required immediate attention - block 79094. However, what began as a targeted hot-fix evolved into a comprehensive update that brings significant improvements across multiple layers of our system.

While we initially thought the aforementioned problem would solve itself (after all it was well over a year since any hiccups at the consensus / difficulty alignment issues occurred) (…) hours were passing. Then, it became obvious that our Development Team stepping into action was inevitable. We’ve worked closely with our Community members and multiple Operators, also getting ourselves involved in remote on-premises debugging. Soon after a differential release (with no actual official installer) initiated a Hard Fork at blockchain height 79094, marking a new chapter in GRIDNET’s evolution. A Legendary Wizardly Party began and the Hard Fork was a massive success - and it is all thanks to you - our wonderful Community of Operators! We thank you so much :heart:

All development was conducted, as always, through YouTube LIVE sessions, maintaining our commitment to transparency and community involvement. The breadth of improvements in this release demonstrates our ability to turn challenges into opportunities for substantial system-wide enhancements.

Security and Integrity Enhancements

Advanced Self-Integrity Validation

Our most significant security upgrade involves sophisticated self-checking mechanisms that ensure the integrity of both the Core system and its OpenCL components. This comprehensive validation system represents a breakthrough in blockchain security, detailed in our technical documentation at https://talk.gridnet.org/t/gridnet-core-1-5-5-technical-update-advanced-security-integrity-mechanisms/.



The validation system operates on multiple levels:

  1. Core Binary Validation: Continuous monitoring of critical system components
  2. OpenCL Infrastructure Verification: Real-time validation of mining operations
  3. Cross-Component Authentication: Ensuring all system parts work in harmony

These mechanisms provide unprecedented security while maintaining system performance, a balance that’s crucial for a mining-focused blockchain.

Mining System Overhaul

Revolutionary OpenCL Subsystem

The OpenCL subsystem has been completely reimagined, addressing long-standing issues and introducing cutting-edge features:

Multi-GPU Architecture Support

We’ve achieved a breakthrough in mixed hardware support, enabling:

  • Seamless operation of AMD and NVIDIA GPUs in the same system
  • Optimized performance for each GPU type
  • Dynamic workload distribution based on hardware capabilities

This was accomplished through extensive remote debugging sessions with our community operators, whose diverse hardware setups provided invaluable testing environments.

Kernel Management and Compilation

Enhanced Kernel Compilation Process

Our two-phase kernel compilation system has been significantly upgraded, introducing:

  1. Advanced Progress Tracking

    • Real-time compilation progress bar showing actual compilation stages
    • Detailed status updates for each compilation phase
    • Immediate feedback on compilation failures and optimizations
  2. Platform-Specific Optimizations

    • AMD-specific optimization flags leveraging GCN architecture capabilities
    • NVIDIA-specific optimizations utilizing CUDA capabilities through OpenCL
    • Proper SIMD alignment ensuring optimal memory access patterns
    • Custom vector width selection based on GPU architecture

      Above one may see custom optimisation arguments passed to kernel compilation process based on detected platform and supported OpenCL interface revision. Above is on Geforce 4090

      and Geforce 1080

:point_up_2: now that’s interesting; due to optimisations employed GPUs might be returning no to accurate results, but - these results are verified. on CPU in any case; thus invalid nonce values would simply be neglected.

The scheduling sub-system keeps track of the frequency of false positives. Should these become unusually high for any given GPU - the system would attempt to restart the OpenCL sub-system (Context) assigned to a particular GPU. Normally, were these brute arthimetic not in place - false nonce positives could indicate issues with GPU ( memory getting too hot etc.)


:point_up_2: 4 AMD GPUs working in tandem
3. Comprehensive Failure Tracking

Each GPU maintains a compilation history:
- Timestamp of attempts
- Detailed error logs
- Specific failure points
- Hardware-specific optimization attempts
  • after kernel compilation Core would now provide a detailed per sub-kernel OpenCL one way hash transformation kernel function report which looks as follows:
Kernel Analysis Report
=====================
SIMD Width: 64
Using Newly Compiled Program

Kernel 'shavite':
  Max Work Group Size: 256
  Preferred Multiple: 32
  Local Memory Required: 0KB
  Aligned Max Size: 256

Kernel 'keccak':
  Max Work Group Size: 256
  Preferred Multiple: 32
  Local Memory Required: 0KB
  Aligned Max Size: 256

Kernel 'hamsi':
  Max Work Group Size: 0
  Preferred Multiple: 32
  Local Memory Required: 16KB
  Aligned Max Size: 0

Kernel 'blake':
  Max Work Group Size: 256
  Preferred Multiple: 32
  Local Memory Required: 0KB
  Aligned Max Size: 256

Kernel 'jh':
  Max Work Group Size: 256
  Preferred Multiple: 32
  Local Memory Required: 0KB
  Aligned Max Size: 256

Kernel 'skein':
  Max Work Group Size: 256
  Preferred Multiple: 32
  Local Memory Required: 0KB
  Aligned Max Size: 256

Advanced Logging System

The OpenCL build process now provides detailed insights:

  • Kernel compilation stages with timing information
  • Extension availability and utilization status
  • Memory alignment and usage patterns
  • Device-specific capabilities and limitations

This granular information helps operators quickly identify and resolve any mining-related issues.

Proof-of-Work Enhancements

EMA-Based Difficulty Adjustment

Through extensive simulation and testing, we’ve significantly improved our difficulty adjustment algorithm:

  1. Coefficient Optimization

    • EMA coefficient more than doubled based on simulation results (remember, one can use the diff GridScript command to check current difficulty, but one can also use diff to see how the difficuty would look like were other adjustment coefficients in place. Use diff -help to see a detailed MAN-page with more how-to advise.
    • Faster convergence to network’s actual computational power (yet again, thanks to an increased Alpha base EMA coefficeint)
    • Reduced oscillation during rapid hashrate changes (72 hour adjustment window, during which all key-blocks are taken into account)
  2. Excel-Based Simulation Tool
    Revied The simulator allowed us to:

    • Model sudden hashrate changes
    • Analyze network recovery patterns
    • Fine-tune adjustment parameters
    • Visualize network behavior under various conditions

Extended Mining Capabilities and Network Analysis

Unlimited Partial Proof-of-Work Results

A significant advancement in our mining architecture removes the previous cap of 254 nonce results per kernel execution. This enhancement:

  • Allows GPUs to return unlimited potential solutions
  • Prepares the system for future mining pool integration
  • Enables accurate measurement of actual mining contribution
  • Will support fair reward distribution based on partial PoW contributions

This upgrade is particularly significant for our future mining pool implementation, where miners will be rewarded proportionally to their computational contributions, even when they don’t solve complete blocks.

Advanced Difficulty Analysis

Logarithmic Distance Measurement

We’ve introduced a sophisticated logarithmic distance calculation that:

  • Precisely measures how close partial solutions are to the target difficulty
  • Provides accurate assessment of mining performance
  • Helps miners understand their actual contribution to the network
  • Offers detailed insights into hardware efficiency

Example output:

[Partial PoW] Distance from target: -30% (logarithmic)
[Partial PoW] You're getting closer! Keep those GPUs spinning!

Enhanced Network Statistics and Monitoring

Improved ‘chain -stats’ Command

The ‘chain -stats’ command has been significantly enhanced to provide:

  • Real-time network hashrate calculations
  • Current difficulty trends and predictions
  • Block propagation statistics
  • Network health indicators
  • Detailed blockchain metrics

Enhanced Block Data Lookups

Block investigation capabilities now include:

  • Detailed block architecture analysis
  • Transaction propagation metrics
  • Operator performance statistics
  • Network consensus indicators

Wizardly Commentary

We’ve added engaging and informative commentary that provides:

  • Technical insights into mining performance
  • Encouraging feedback for close solutions
  • Humorous wizardly observations
  • Performance improvement suggestions
    Some of this can be seen below:

Examples:

"By Merlin's beard! That was close - only 0.1% away from target difficulty!"
"The magical forces are strong with this one - keep pushing those computations!"
"Your GPUs are weaving quite the spell - multiple partial solutions detected!"

These enhancements combine to create a more informative, engaging, and technically advanced mining experience while preparing the groundwork for future features such as mining pools and advanced reward systems.

What’s Next? GRIDNET Core 1.6 - one of the biggest releases ever made - and another Hard Fork meaning a yet another Wizardly Party on the way! :mage:

2 Likes