Skip to content

XChain Platform v0.12.0

Choose a tag to compare

View all tags
@jdogresorg jdogresorg released this 31 Aug 23:14
· 337 commits to master since this release
v0.12.0
This tag was signed with the committer’s verified signature.
jdogresorg J-Dog
GPG key ID: 4361611A82F90B70
Verified
Learn about vigilant mode.
324eea8
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.12.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.12.0 <service> <coin> <network>

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

What is in this train

  • ROLLCALL: hubs sign each epoch, gossip the signatures, and an elected publisher lands the roll call on chain. A source absent across consecutive rolled epochs is deactivated by a synthetic unstake, and rolling back the close restores what it changed.
  • ROLLCALL is inert on regtest. Arming a network commits every Bitcoin indexer on it to a wired Dogecoin peer, because an epoch close cannot decide a non-empty responsible set without one and correctly halts rather than read silence as absence. A single-coin regtest venue has no such peer and can never have one.
  • Anchors publish one bundle per network per cycle, replacing one anchor per chain. A bundle the attestation round could not attest is deferred rather than published unattested.
  • The database connector moves to 3.5.3, closing three high-severity advisories against the pinned 3.5.2, including one that reached a service through a stale bundled copy while the top-level dependency already read clean.
  • Refused cross-chain calls and refused anchors are recorded as events rather than dropped silently, and a stalled checkpoint cadence is recorded rather than passing as one tick in sixty.
  • Token balances with decimal places display at their true scale in the wallet.

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

Assets 18
Loading