Skip to content

v0.8.1

Choose a tag to compare

@GitGab19 GitGab19 released this 05 Nov 17:12
09f538b

General release information

This is a PATCH release on top of v0.8.0. It keeps JDC on the Bitcoin Core version of the node it connects to (#400), and moves JDC and tProxy to the sv2-apps v0.9.1 images.

  • JDC now always runs with the Bitcoin Core version of its node (#399). The version saved at setup used to go stale when the node changed major version, for example when Umbrel's Bitcoin Node 1.5.0 moved nodes set to latest to Core 32.1. Between Core 31 and 32 a wrong version looks healthy: JDC gets templates and logs no errors, but every block it finds fails to reach Bitcoin Core. sv2-ui now reads the node's version before every JDC start. If the node runs another supported version, it saves that one and starts. If the version is unsupported or can't be read, JDC doesn't start, and the dashboard says why.
  • The wizard's Bitcoin step shows the node's version instead of asking for it.
  • The dashboard reports a found block that JDC couldn't submit.
  • Stop and Reset report a container that couldn't be stopped, instead of claiming success.
  • JDC and tProxy have no changes in sv2-apps v0.9.1: their images are rebuilds of the v0.9.0 code, since that release only changes JDS.

Who should upgrade: everyone running a JD stack, in particular anyone whose node changed major version after setup. No setup steps need repeating: a stale saved version is corrected on the next start.

JD stacks now need RPC access to the node. sv2-ui reads the version over RPC, through the data directory that holds the IPC socket, with the node's cookie and the rpcport and rpcbind set in bitcoin.conf. JDC doesn't start if that read fails, which happens when:

  • the RPC server is turned off,
  • the RPC port is set on the command line,
  • the RPC settings are in a file named by -conf or includeconf,
  • the cookie is moved with -rpccookiefile,
  • the IPC socket is outside the node's data directory.

Each has a small fix in the node's config, and the dashboard banner says what to check.

What's Changed

  • fix: keep JDC on the node's Bitcoin Core version by @GitGab19 in #400

Full Changelog: v0.8.0...v0.8.1