Repository navigation
xchain-node v0.23.3
Release v0.23.3 manifest, for the release/v0.23.3 maintenance line (release-management section 7, maintenance line). This line is what mainnet runs; master carries v0.26.x.
src/release-manifest.json is generated with bin/write-release-manifest.js --version 0.23.3 from the pushed signed origin tags. Five components move to v0.23.3 and every other component keeps its v0.23.0 pin:
| Component | Tag | Change |
|---|---|---|
| xchain-decoder | v0.23.3 | runtime Node 25.9.0 to 22.23.4 (CVE-2026-111497) |
| xchain-encoder | v0.23.3 | Node 22.23.2 to 22.23.4 |
| xchain-utxo-tracker | v0.23.3 | Node 22.23.2 to 22.23.4 |
| xchain-hub | v0.23.3 | Node 22.23.2 to 22.23.4 |
| xchain-indexer | v0.23.3 | refuses Content-Encoding: br request bodies with 415; stays on Node 22.23.2 for the xchain-vm consensus runtime pin |
| xchain-vm, xchain-sync, xchain-explorer, xchain-sdk | v0.23.0 | unchanged |
The package version moves to 0.23.3 with one changelog entry. The trainActivation block carries no new height: nothing in this train changes derived state, and the mainnet activation census reads 0 values changed.
The GitHub Release for v0.23.3 is published with --latest=false, so releases/latest keeps resolving to the newest v0.26.x release and no node's no-ref update all moves backward.