What's New in v0.2.6
Gonka Network v0.2.6 delivers significant infrastructure improvements focused on scalability and operational efficiency. This release introduces optional PostgreSQL support for payload storage and refines the upgrade process to provide a smoother experience for new network participants.
PostgreSQL Integration for Large Deployments
The headline feature of v0.2.6 is optional PostgreSQL support for off-chain payload storage. While the default file-based storage remains suitable for smaller nodes, operators running larger deployments can now leverage PostgreSQL for improved performance and reliability.
Configuration Options
The PostgreSQL integration provides comprehensive configuration through environment variables:
Database Container Settings:
- POSTGRES_PASSWORD (required)
- POSTGRES_USER (default: payloads)
- POSTGRES_DB (default: payloads)
- POSTGRES_MIN_WAL_SIZE (default: 4GB)
- POSTGRES_MAX_WAL_SIZE (default: 16GB)
- POSTGRES_CHECKPOINT_TIMEOUT (default: 15min)
API Connection Settings:
- POSTGRES_HOST - Database host address (file storage used if not set)
- POSTGRES_PASSWORD - Database password
- POSTGRES_PORT (default: 5432)
- POSTGRES_USER (default: payloads)
- POSTGRES_DB (default: payloads)
Deployment Recommendations
For production environments, we recommend deploying PostgreSQL on a dedicated machine or ensuring its storage volume is mounted on a separate disk to optimize I/O performance and maintain system stability.
To enable PostgreSQL after the upgrade:
git pull
source config.env && docker compose -f docker-compose.postgres.yml up -d
Streamlined Upgrade Process
v0.2.6 introduces an improved upgrade workflow that minimizes version mismatches between on-chain binaries and deployment configurations. The new process creates releases from feature branches rather than main, reducing the window where new hosts might encounter version conflicts.
Key Process Improvements
- Reduced Version Drift: Container versions in the
/deploy/join/directory now stay synchronized with on-chain binary versions - Simplified New Host Onboarding: New participants joining after upgrades will encounter consistent version configurations
- Existing Host Compatibility: Current hosts are not required to upgrade their containers immediately
Technical Implementation
This release updates both api and node services, with container version modifications in deploy/join/docker-compose.yml. The upgrade has been thoroughly tested on testnet, with successful migration from v0.2.5 validated.
Migration Notes
Existing hosts can continue operating without immediate container updates. The new container versions are primarily intended for hosts joining the network post-upgrade. This approach ensures network stability while providing improved infrastructure for future growth.
Testing and Validation
The v0.2.5 to v0.2.6 upgrade path has been extensively tested on testnet environments. Network operators and community members can request testnet access to validate the upgrade process or deploy private testnets for independent verification.
Looking Forward
v0.2.6 establishes a foundation for enhanced scalability and operational efficiency. The PostgreSQL integration addresses storage requirements for growing network usage, while the refined upgrade process ensures smoother network evolution as Gonka continues to expand.
For technical details and upgrade documentation, refer to the upgrade guide in the project repository.