Overview

Gonka Network v0.2.6-post1 represents a significant step forward in our infrastructure capabilities, introducing optional PostgreSQL support for payload storage and implementing a more robust upgrade process. This release focuses on scalability improvements and operational efficiency rather than breaking changes.

Key Changes

PostgreSQL Support for Payload Storage

The most significant addition in this release is optional PostgreSQL support for off-chain payload storage. While the default file-based storage remains suitable for smaller deployments, PostgreSQL integration addresses the needs of larger nodes requiring more robust data management.

Key features: - Seamless fallback to file storage when PostgreSQL is not configured - Configurable database parameters including WAL size and checkpoint timeout - Separate deployment configuration via docker-compose.postgres.yml - Recommended deployment on dedicated infrastructure for optimal performance

Configuration options:

# PostgreSQL container settings
POSTGRES_PASSWORD=your_secure_password
POSTGRES_USER=payloads  # default
POSTGRES_DB=payloads    # default
POSTGRES_MIN_WAL_SIZE=4GB
POSTGRES_MAX_WAL_SIZE=16GB

# API connection settings
POSTGRES_HOST=your_postgres_host
POSTGRES_PORT=5432      # default

Improved Upgrade Process

This release implements a refined on-chain upgrade workflow that addresses a critical operational challenge. Previously, there could be mismatches between container versions in the deployment directory and actual on-chain binary versions, creating confusion for new hosts.

The new process: 1. Community reviews upgrade proposals on GitHub 2. Upon approval, releases are created from feature branches 3. On-chain upgrade proposals are submitted 4. Merges to main occur only after successful on-chain execution

This approach ensures that new hosts always encounter consistent version information when joining the network.

Deployment and Migration

Existing hosts are not required to upgrade their containers immediately. The updated container versions primarily benefit new hosts joining after the on-chain upgrade completes. This backward compatibility reduces operational burden on existing network participants.

For hosts choosing to implement PostgreSQL storage:

git pull
source config.env && docker compose -f docker-compose.postgres.yml up -d

Technical Validation

The upgrade path from v0.2.5 to v0.2.6 has undergone comprehensive testing on our testnet environment. The on-chain migration completed successfully, and all core functionalities have been verified. We encourage community members to request testnet access for independent validation.

Impact and Recommendations

This release positions Gonka Network for improved scalability while maintaining operational simplicity. Small to medium deployments can continue using file-based storage, while larger operations can leverage PostgreSQL for enhanced performance and reliability.

Recommendations: - Deploy PostgreSQL on dedicated hardware or separate disk volumes - Monitor WAL size settings based on your node's transaction volume - Test the upgrade process in a staging environment before production deployment

The streamlined upgrade process reduces the risk of version mismatches and improves the overall developer and operator experience when joining or maintaining network infrastructure.