-
hidden-rpc v1.3.2 Stable
released this
2026-11-05 04:50:48 +00:00 | 0 commits to main since this releasehidden-rpc v1.3.2
A node can no longer sit dark for weeks thinking it is rebuilding
oldpc was unreachable for 41 days. Every attempt to rebuild its chain died at once, because a rebuild starts from Blurt's genesis file (
snapshot.json) and oldpc didn't have it. None of the fleet did. A safety lock then kept every other repair away, because it mistook the crash loop for a rebuild in progress.- No rebuild starts without the genesis file. It's fetched automatically, from Blurt's own download or IPFS, and used only if it's provably the exact file Blurt published (its IPFS content ID).
- Every node keeps its own copy (641 MB), so the next one that needs a rebuild has it already.
- A crash loop is never mistaken for a rebuild, and it escalates to the deeper repairs instead of restarting forever.
- If the file can't be fetched, the tray says so right away, with the fix:
sudo hidden-rpc-setup --genesis /path/to/snapshot.json. - The red-dot text stays true (oldpc's said "2h 0m" for 41 days), and it comes down while a rebuild runs.
- The forensics report shows blurtd's own error and whether the genesis file is there.
- Re-running the installer never upgrades Docker under a running node. An upgrade restarts Docker, which would cut a rebuild short.
Also includes v1.3.1's fixes: installs can't get stuck, Ctrl-C works, and forensics no longer hides what it finds.
To upgrade: run the installer on each node. A node that's mid-rebuild (like oldpc tonight) is left alone; it's safe to upgrade it any time.
Downloads
-
Source code (ZIP)
1 download
-
Source code (TAR.GZ)
6 downloads