This is a minor version update to Gordian Server that includes major, but backward-compatible new features. The main additions are:
- RPCAuth. For improved security, Gordian Server now uses
rpcauth
instead of plain text files. - arm64 and x86_64 Compatibility. Previous versions of Gordian Server were stuck using the older Intel Bitcoin binaries, but the newest version correctly selects a Bitcoin binary based on your machine's architecture.
- Updated Bitcoin Core. Gordian Server is now fully compatible with Bitcoin Core v25 and v26.
- Other Bug Fixes
See #169 and #182 for the major PRs incorporated into this new version. Thank you to @Fonta1n3 who is responsible for all the fixes and improvements.
Please note that Gordian Server is lightly supported. Some open Issues may remain bugs in the current version.
In particular, there have been some troubles doing updates from older version of Gordian Server when combined with updates to the Bitcoin Core version and the rpcauth
system. If you do not store private information on your server (such as seeds and keys) we suggest rebuilding it from scratch by "KILL ALL"ing the old setup from Settings and then installing the new binary. If you do have private information stored on your server, obviously don't do that. But, be aware the update may hang: just close out Server, kill any Server processes from your Activity Monitor, and restart if that occurs.
Gordian Server 1.1.0 has been tested on Intel, M1 Pro, and M2 machines, running Sonoma and some older OSes. Stability of at least a week was verified on both the Intel and M2 platforms. (The M1 Pro didn't run that long because it's a laptop.)
gordian-server-1.1.0.dmg
is the main file in this release. Everything else is for signature and binary verification. This release has been signed by christophera & shannona with their typical GPG keys (those are the *.asc files), but also new SSH keys (those are the *.sig files). The SSH keys have also been signed with the older GPG keys to demonstrate continuity and self-signed with the SSH keys to demonstrate control. We consider these best practices for updates in signing keys.