Reported by @k9ert: https://github.com/cryptoadvance/specter-desktop/pull/1482#discussion_r756783512
Confirmed on the 22.0x branch:
bitcoin-cli getnetworkinfo
{
"version": 220000,
"subversion": "/Satoshi:22.0.0/",
...
cc @achow101
Reported by @k9ert: https://github.com/cryptoadvance/specter-desktop/pull/1482#discussion_r756783512
Confirmed on the 22.0x branch:
bitcoin-cli getnetworkinfo
{
"version": 220000,
"subversion": "/Satoshi:22.0.0/",
...
cc @achow101
This should be the build id, which is always displayed now for clarity?
At some point someone asked the same thing about the --version, but I can't find the thread.
Cf.
$ bitcoin-core.cli --version
Bitcoin Core RPC client version v22.0.0
I'm not sure it is spurious. It's padded to have all the potential version numbers. In the past we had four-number versions in some cases (e.g. a small platform-specific update) so wouldn't entirely rule out an e.g. 23.0.1 with three numbers.
I guess if it's intentional then it's not a bug. The binary archive name can always be derived from the version field instead, if you know the rules. Or we could add yet another result to this RPC like version_rounded.
The binary name could also be changed to include the build id?
@Sjors Can this be closed?
I stopped caring :-)
(I assume everyone who ran into this has implemented a workaround by now)