Skip to content

v0.9.2 target release and migration

Node, CLI, and RPC documentation targets FullOn Core v0.9.2, commit 2188e4f94a1e9fe564a31c33e497b464556f3650. Its annotated tag object is 6688825a23c4fe580acea00b38299a1518131232, cross-checked with GitHub tag metadata. Source review date: 2026-11-02.

Scope

  • Complete RPC and history were rechecked for registration, structures, and availability.
  • Nodes, P2P, and account/ABI/code/action CLI examples were checked against this commit. Relevant CLI parameters are unchanged from the old baseline; references now pin the release.
  • Docker Compose retains an independent template revision and explicitly selects v0.9.2 node/tools, without pretending template defaults or CDT have the same version.
  • Contracts, system permissions, RWID, CDT, and wallets have independent versions. A Core upgrade does not verify their deployment or compatibility; their stated evidence boundaries remain.

Substantive changes from the old RPC reference

Area v0.9.2 target behavior
History diagnostics get_optimization_suggestions, get_cache_analysis, and get_maintenance_needs are registered under both prefixes; trigger_auto_optimize remains unregistered
History responses history_status and transaction account_index_complete expose coverage; missing legacy fields are not completeness guarantees
History recovery Filters, deadlines, response size, and persisted gaps affect queries; restart does not automatically delete/rebuild a gap-marked database
Builds and roles core/history builds; BP/RPC/seed runtime roles; configuration cannot enable compiled-out plugins
Management APIs Non-loopback/non-Unix management listeners rejected by default; signing remains Unix-only
Local recovery State/blocks operation locks and restore.pending prevent overlapping node/physical recovery; diagnose rather than deleting markers to bypass checks
Coverage maximum All-optional build: 76 logical operations / 86 paths, plus three conditional greylist operations; not a default-package or live-node guarantee

Select a release package

The official v0.9.2 release lists:

  • flon-node-0.9.2-<platform>: common/BP/RPC/seed core node.
  • flon-node-history-0.9.2-<platform>: History, Trace, and State History capability.
  • flon-tools-0.9.2-<platform>: fucli, fuwal, flon-util, funod-state-inspect, and funod-state-checkpoint.
  • Ubuntu 22.04 amd64 node/tools/combined deb packages, Linux x86_64 and macOS arm64 portable archives, and checksums.

Tags use v; archive/deb version components generally do not. Names do not prove every platform, Docker image, or CDT image exists.

Upgrade and verify

  1. Confirm network-approved version, chain ID, features, and data compatibility; retain old packages, configuration, and a consistent data backup.
  2. Select the role/platform package or image and verify official checksums/digests. Pulling an image does not replace an existing container.
  3. Stop the original process, then use a compatible snapshot or replay as required. Do not assume old binaries can read newer state or remove recovery markers to experiment.
  4. Check running versions rather than filenames/image tags:
funod --full-version
fucli version full
fuwal --full-version
  1. Check get_info version/chain ID, advancing head/LIB, supported APIs, role plugins, and history health. BPs also need schedule and signer checks.

This work reviews source/release metadata and documentation only. No mainnet/testnet node was started, upgraded, or modified, and no chain writes were performed. Historical 2026-09-03 live observations keep their date and are not new deployment evidence.

Review evidence

The pinned source, SHA-256 hashes, and registered-route manifest covers builds, registration, History structures, HTTP management checks, CLI, P2P, and presets. Source changes require regeneration and review, not just a version-string edit.