XChain Platform v0.11.0

XChain Platform v0.11.0.

One platform version names an exact, reproducible set of software. src/release-manifest.json in this release pins all twelve components by tag and commit; every pin is a master merge commit whose CI is green, and every component tag is GPG-signed by the XChain Platform release key.

Verifying this release

gpg --verify SHA256SUMS.asc SHA256SUMS
shasum -a 256 -c SHA256SUMS

The signing key is published at xchain-documentation/operations/release-signing.md and in tools/release/ in every train repo. Any other key is not an official release.

Installing this exact set

xchain-node install v0.11.0 <service> <coin> <network>

Installing at the tag resolves this manifest and clones each component at its pinned commit.

What is in this train

• Protocol time on testnet now reads from median-time-past rather than the raw block timestamp, which removes an admission stall where a confirmed transaction could take up to about two hours to appear. Armed for testnet only.
• The explorer status endpoint reports why the indexer trails and when the wait clears, so a deliberate pause for a block stamped in the future is distinguishable from a stuck indexer.
• Mempool data is read live from each coin's decoder API, so explorers serving from synced replicas can show pending transactions.
• The bundled consensus pin is verified at API boot, so a host carrying a drifted coin registry halts instead of serving from it.
• Installs verify downloaded artifacts, recover from a failed mirror, and end with a bootstrap restore summary.

Full per-component detail is in each repository's CHANGELOG at its v0.11.0 tag.

Operator notes

• Deploy the hubs together. The oracle clamp convergence leaves a straddle window of up to one re-seed interval, and a mixed-version hub set can disagree on the clamp reference.
• Deploy pinned, and verify per box by reading modules/*/src/coins/BTC.js rather than the node repository's own HEAD. The mainnet consensus pin is null pre-launch, so a node that misses this build does not fail closed.

XChain Platform 0.10.0

XChain Platform v0.10.0, the second release train. One platform version names an exact, reproducible set of software across every component.

Resolved component set

Every component below is pinned in release-manifest.json by tag and by commit, and every one changed in this train.

Component	Version	Pinned commit
xchain-node	0.10.0	ca16016fb904013292af154c85e8ddafdcdd7d34
xchain-hub	0.10.0	cbb97b97e1b670a8b28b40d4abe9f664d8eb284e
xchain-indexer	0.10.0	698be256cb062ba3f05bd5a4e69d9d2f1cb206e7
xchain-explorer	0.10.0	e4ca98a6af0f153d4ec928576e1f24568c3dfa8b
xchain-decoder	0.10.0	09170e9a32c67484ece203a6cfc6f149f530f0a7
xchain-encoder	0.10.0	27a2a87f892aed2b9602361ceb78f24a639050bb
xchain-sync	0.10.0	70a58033ff3b8468c26053afdfa4b8614e502bc8
xchain-utxo-tracker	0.10.0	c48b87be04a7115f78b2ec7d3031d25104be1706
xchain-vm	0.10.0	4db160dd6ebcb1a7c8e8309b45ce00ffb5f7793c
xchain-sdk	0.10.0	7bcefac0c28544f7fcb742629fc553e3d6e2c49e
xchain-contracts	0.1.0	da194411bdaa43add28fb1af1d345f92c89c0d2e
xchain-e2e-test	0.3.9	5db34052213ac847218844eef3c1fd2690f2c2b4
xchain-regtest-miner	0.1.21	ba73838eeaab95c942ef3cbbae9f6efccb9726bb

The last three keep their own version streams and are tagged v0.10.0 to mark the train they shipped in, so the version column and the tag differ for them. The commit is what pins; the tag names the train.

The manifest pins all twelve modules the installer clones. The v0.9.0 manifest listed eight, so a pinned install of that train still resolved four modules at their default branch. Anyone reproducing v0.9.0 should be aware of that; v0.10.0 and every train after it pin the full set.

Tier 2 applications ride their own rails and are not part of this train. The current wallet release is 0.339.0.

Highlights

Consensus. The ledger amount precision flag day is pinned on mainnet at heights above each chain's tip, so a carrying fleet cannot open a retroactive window. The contract state sub-root is armed from genesis on every testnet. Batch cost weighting prices a chunk-carrier DEPLOY as a row write rather than a VM run, so it can share a batch with 249 companions instead of 220.

Indexer. Free-form user-text columns accept any legal UTF-8, closing a defect where one legal broadcast carrying a four-byte character could halt every indexer on the chain at the same block. Schema shape baselines are anchored to immutable origin fixtures, so a baselined shape can no longer be edited and re-frozen in a single commit with no migration. Anchor proofs are bound to the reward's own chain.

Hub. Oracle publishing and attestation relay reserve their spend budget before an awaited broadcast, so concurrent sends can no longer spend past the per-window ceiling. Every publisher refuses phase one of a two-transaction encoding before signing. A refused proposal consumes its rotation slot, so a hub that was not the leader for one slot can propose again. New read RPC for slash proposals, returning evidence as a digest rather than verbatim text.

Explorer. Detail pages for validators, XCALLs, attestations, polls and anchors. Seven new read surfaces for platform data that previously had none. A staking panel on the address page. A slash proposals surface that reads as accusation rather than verdict. The visual layer moves into a loadable theme token file.

SDK. verifyLockedBalance binds a served proof to the quorum-signed checkpoint, and locked-balance arming now gates on a caller-supplied trusted height rather than the server-echoed one. Identity binding on proof verification refuses a proof that answers a different address or tick. The static batch validator applies the weighted budget the chain actually charges.

Node. Pinned installs verify downloaded release artifacts against the pinned signing key. The explorer can run a self-synced checkpoint mirror for deployments with no colocated hub schema. A bootstrap source reporting no lag, or a negative lag, is refused rather than read as healthy.

Each component's CHANGELOG.md carries its full entry for this release.

Verifying this release

Every train tag is signed with the XChain Platform Release Signing key, RSA 4096, fingerprint 1DA7 C489 6F56 EA22 CF49 1EDF 4361 611A 82F9 0B70.

git tag -v v0.10.0
gpg --verify SHA256SUMS.asc SHA256SUMS
sha256sum -c SHA256SUMS

The assets are the pinned manifest, one source tarball per train member built at cut time from its tagged commit, and the digests with their detached signature. The tarballs are built during the ceremony rather than taken from GitHub's auto-generated archives, because those are not byte-stable over time.

Installing

xchain-node install v0.10.0

A pinned install resolves every component to the exact commit recorded in the manifest and verifies the artifacts after clone. install develop and install master remain tracking installs with no pins, for development.

Testing

Every component's full suite passed on its release branch, and the three-coin regtest end-to-end matrix, the action, security and performance suites across Bitcoin, Litecoin and Dogecoin, passed against the frozen commits with zero failures on all three coins.

XChain Platform 0.9.0

XChain Platform 0.9.0

First release of the XChain Platform release train. Every train component now
shares one platform version, so XChain 0.9.0 names an exact, reproducible set
of software rather than a rough era.

Resolved component set

Component	Version	Changed this train
xchain-vm	0.9.0	yes
xchain-decoder	0.9.0	yes
xchain-indexer	0.9.0	yes
xchain-hub	0.9.0	yes
xchain-sync	0.9.0	yes
xchain-node	0.9.0	yes
xchain-encoder	0.9.0	yes
xchain-utxo-tracker	0.9.0	yes
xchain-explorer	0.9.0	yes

All nine changed, because this is the adoption jump onto the shared stream.

The version numbers go DOWN, deliberately

The platform stream starts at 0.9.0 for the testnet series; 1.0.0 is reserved
for mainnet. Most components carried a higher number in their own stream
(xchain-indexer was 2.7.17). A higher legacy number is an OLDER release.
Each changelog marks the boundary in place.

Install

xchain-node install v0.9.0     # this exact pinned set
xchain-node install            # resolves the latest release, same thing today

Both install every service and every bundled library at the commit
release-manifest.json pins, and verify each checkout against it.

Verify this release

git tag -v v0.9.0
gpg --verify SHA256SUMS.asc SHA256SUMS
sha256sum -c SHA256SUMS

Signed with the XChain Platform release key,
1DA7 C489 6F56 EA22 CF49 1EDF 4361 611A 82F9 0B70. See
Release Signing.

Known issues

Three suites are red for reasons that predate this release and are unchanged
by it: xchain-hub regression, xchain-sync e2e, and xchain-explorer
perf/integration/conformance. They were surfaced when CI began running again and
are tracked for follow-up. The hub failures include a slashing-counter reset
defect, so operators running validators should follow that work.