This marks the third public release of
poold, and the second minor release after the initial public release. This release contains no new features. Instead, this release packages a number of important bug fixes related to account management, and the REST API server.
Verifying the Release
In order to verify the release, you'll need to have
gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
curl https://keybase.io/guggero/pgp_keys.asc | gpg --import
Once you have the required PGP keys, you can verify the release (assuming
manifest-v0.3.4-alpha.txt.asc are in the current directory) with:
gpg --verify manifest-v0.3.4-alpha.txt.asc
You should see the following if the verification was successful:
gpg: Signature made Mi 29 Jul 2020 14:59:19 CEST gpg: using RSA key 6E01EEC9656903B0542B8F1003DB6322267C373B gpg: Good signature from "Oliver Gugger <email@example.com>" [ultimate]
That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the
sha256 hash of the archive with
shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.
Verifying the Release Binaries
Our release binaries are fully reproducible. Third parties are able to verify that the release binaries were produced properly without having to trust the release manager(s). See our reproducible builds guide for how this can be achieved. The release binaries are compiled with
go1.15.5, which is required by verifiers to arrive at the same ones.
make release command can be used to ensure one rebuilds with all the same flags used for the release. If one wishes to build for only a single platform, then
make release sys=<OS-ARCH> tag=<tag> can be used.
Finally, you can also verify the tag itself with the following command:
The signature on the tag itself can be verified with:
git verify-tag v0.3.4-alpha
Building the Contained Release
Users are able to rebuild the target release themselves without having to fetch any of the dependencies. In order to do so, assuming that
poold-source-v0.3.4-alpha.tar.gz are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz tar -xvzf lnd-source-v0.3.4-alpha.tar.gz GO111MODULE=on go install -v -mod=vendor ./cmd/poold GO111MODULE=on go install -v -mod=vendor ./cmd/pool
-mod=vendor flag tells the
go build command that it doesn't need to fetch the dependencies, and instead, they're all enclosed in the local vendor directory.
Additionally, it's now possible to use the enclosed
release.sh script to bundle a release for a specific system like so:
make release sys="linux-arm64 darwin-amd64"
- Fix a problem in REST server that resulted in the
grpc: the client connection is closingerror: #175
no order founderror when trying to close an account: #180
- Remove irritating error message
Unable to determine spend for account xxxx: context canceled: #181
- Fix startup problem when pending batch was found in database: #179
- Fix typo in
- Add debug commands and wrap some errors to add more information: #178
Contributors (Alphabetical Order)