Skip to content

XChain Platform v0.11.0

Latest
Latest

Choose a tag to compare

View all tags
@jdogresorg jdogresorg released this 26 Aug 03:49
v0.11.0
This tag was signed with the committer’s verified signature.
jdogresorg J-Dog
GPG key ID: 4361611A82F90B70
Verified
Learn about vigilant mode.
2e568ee
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

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.
Assets 18
Loading