6eb25d6b25
Build All Platforms / test-linux-unit (push) Failing after 40s
Build All Platforms / build-linux-qt (push) Failing after 40s
Build All Platforms / build-linux-daemon (push) Failing after 40s
Build All Platforms / build-windows-qt (push) Has been cancelled
Build All Platforms / build-windows-daemon (push) Has been cancelled
Build All Platforms / build-macos (push) Has been cancelled
Build All Platforms / release (push) Has been cancelled
Build All Platforms / Trigger TRI-PI ARM64 Build (push) Has been cancelled
New RPC commands: - addnode: add/remove/onetry .onion peers at runtime - disconnectnode: immediately drop a peer connection - getchaintips: diagnose chain forks and orphan branches - invalidateblock: rewind chain past a bad block - reconsiderblock: re-activate a previously invalidated block Also includes: - systemd service files for Linux deployment - Bootstrap/snapshot guide for OpenClaw nodes - Upgrade notes from 2026-04-14 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.5 KiB
1.5 KiB
TRI Node Upgrade to v5.8.0 - April 14, 2026
This document outlines the process and results of upgrading the TRI network nodes to version 5.8.0.
Initial State
- DNS2:
v5.7.9@ block2,203,611 - DNS3:
v5.7.5@ block2,204,954 - Contabo Seeds:
v5.7.9@ block2,203,594
Nodes were on multiple versions and forks.
Upgrade Process
- Version Confirmation: Verified
v5.8.0was available on GitHub. - Upgrades:
- DNS2 upgraded to
v5.8.0viadpkg. - DNS3 upgraded to
v5.8.0viadpkg. - Contabo seeds (
tri-seed-1to4) upgraded tov5.8.0viadpkginside their containers.
- DNS2 upgraded to
- Chain Reset: To resolve forks, the chain data (blocks, chainstate, peers) was wiped on DNS2 and all Contabo seeds. Wallets and configs were preserved. DNS3 was left as the canonical chain source.
Current Status
- All nodes are now running
v5.8.0. - Nodes are currently re-syncing to the canonical chain. Monitoring is in progress.
DNS2 Wallet Corruption and Recovery
- Symptom:
triangles.serviceon DNS2 was in a crash loop. Logs showed a recurringCDB() : can't open database file wallet.dat, error -30973error. - Diagnosis:
wallet.datfile was corrupted. - Recovery:
- The corrupted wallet was moved to
wallet.dat.corruptedfor safety. - The latest wallet backup (
dns2-wallet_20260414_031501.dat) was restored from Dropbox. - The
triangles.servicewas restarted.
- The corrupted wallet was moved to
This restored the wallet to a healthy state.