v0.3.78 — Chain-DB restore, sync modes, maintenance, SW freshness

Restore chain DB from the official Klever snapshot

New Restore DB action (batch bar on the overview) replaces a node's chain database with the official Klever FullNode snapshot (kleverchain.<network>.latest.tar.gz, tens of GB) — for when a node only has the latest epoch but you need the full archival DB (e.g. for an indexer).

Per node: preflight free-disk check (refuses if it wouldn't fit), stop, rotate the old DB aside (db.old, kept for rollback if space allows), stream-download straight through gzip+tar (never staging the archive on disk), extract only the db/ subtree (a stray config/ can't clobber live config), chown 999:999, start. Multiple nodes run one at a time. Progress streams live over WebSocket; the request is fire-and-forget so an hour-long restore doesn't hold an HTTP connection.

Provisioning sync mode

The Provision modal now offers Fast bootstrap (--start-in-epoch, default), Full DB snapshot (downloads the archive before first start — an archival node in one step), or Full sync from genesis.

No more alert spam on deliberate stops

Stopping a node from the dashboard marks it as in maintenance; offline alerts are suppressed for maintenance nodes. Cleared on start/restart and self-healing — discovery clears it as soon as the node is seen running again.

Fresh nodes show "initializing"

A just-started node that legitimately reports syncing now shows an initializing badge for its first 10 minutes of uptime instead of looking like a problem.

Fix: stale assets in a long-open tab (Service Worker)

CSS/JS/pages are now network-first (cache is an offline fallback only); only icons/fonts/manifest stay cache-first. Fixes old styles being served after a deploy until a hard refresh — the broken-layout-in-an-open-tab bug.

Full Changelog: v0.3.77...v0.3.78

Full Changelog: v0.3.77...v0.3.78