Full Changelog: gorgona-v3.1.0...gorgonad-v3.4.6
fix: resolve chain hash divergence and P2P broadcast storm
CRITICAL: Requires simultaneous update of BOTH client and server.
The REPL protocol format changed (added prev_hash/curr_hash fields).
PROBLEM:
Nodes entered infinite sync storm: REPL → duplicate (-4) without hash
fix → GET_CHAIN_SAMPLE → SYNC_REC → REPL loop. Caused 100% CPU and
network flood.
ROOT CAUSE:
add_alert() returned -4 on existing IDs without correcting corrupted
prev_hash/curr_hash. Re-chaining ran on replicated alerts, breaking
the chain during mass sync.
SOLUTION:
- REPL now carries remote prev_hash and curr_hash
- add_alert() performs "Chain Healing" on duplicates: overwrites wrong
hashes with trusted peer values - Re-chaining disabled for replicated inserts (forced_id > 0)
- process_repl() triggers GET_CHAIN_SAMPLE only on true gaps
BREAKING CHANGE: REPL format changed from 10 to 12 fields.
All nodes MUST be updated atomically. Mixed clusters will fail.
Migration: Stop all → Deploy new → Start all simultaneously.
First sync emits "CHAIN HEALING" warnings, then stabilizes.
gorgona-3.1.0-2.x86_64.rpm.gz
gorgona-3.1.0-2.x86_64.rpm.sha256.txt
gorgona_3.1.0_amd64.deb.gz
gorgona_3.1.0_amd64.deb.sha256.txt
gorgonad-3.4.6-2.x86_64.rpm.gz
gorgonad-3.4.6-2.x86_64.rpm.sha256.txt
gorgonad_3.4.6_amd64.deb.gz
gorgonad_3.4.6_amd64.deb.sha256.txt
gorgonad_owrt_23.05.4.gz
gorgonad_owrt_23.05.4.sha256.txt
gorgona_owrt_23.05.4.gz
gorgona_owrt_23.05.4.sha256.txt