v0.1.5-beta

Release Notes

This release of lndinit contains lnd compatibility updates and bug fixes.

Installation and configuration instructions can be found in the README.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import guggero's key from keybase:

curl https://keybase.io/guggero/pgp_keys.asc | gpg --import

Once you have his PGP key you can verify the release (assuming manifest-v0.1.5-beta.sig and manifest-v0.1.5-beta.txt are in the current directory) with:

gpg --verify manifest-v0.1.5-beta.sig manifest-v0.1.5-beta.txt

You should see the following if the verification was successful:

gpg: Signature made Do 25 Nov 2021 10:41:18 CET
gpg:                using RSA key F4FC70F07310028424EFC20A8E4256593F177720
gpg: Good signature from "Oliver Gugger <[email protected]>" [ultimate]
Primary key fingerprint: F4FC 70F0 7310 0284 24EF  C20A 8E42 5659 3F17 7720

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

cat manifest-v0.1.5-beta.txt

One can use the shasum -a 256 <file name here> tool in order to re-compute the sha256 hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

Finally, you can also verify the tag itself with the following command:

git verify-tag v0.1.5-beta

Verifying the Release Timestamp

From this new version onwards we'll also now timestamp the manifest file with OpenTimeStamps along with its signature. A new file is now included along with the rest of our release artifacts: manifest-v0.1.5-beta.sig.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following command:

ots verify manifest-v0.1.5-beta.sig.ots

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Changelog (auto-generated)

What's Changed

• build: update to use lnd v0.15.2 by default by @Roasbeef in #23

Full Changelog: v0.1.4-beta...v0.1.5-beta

v0.1.4-beta

Release Notes

This release of lndinit contains lnd compatibility updates and bug fixes.

Installation and configuration instructions can be found in the README.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import guggero's key from keybase:

curl https://keybase.io/guggero/pgp_keys.asc | gpg --import

Once you have his PGP key you can verify the release (assuming manifest-v0.1.4-beta.sig and manifest-v0.1.4-beta.txt are in the current directory) with:

gpg --verify manifest-v0.1.4-beta.sig manifest-v0.1.4-beta.txt

You should see the following if the verification was successful:

gpg: Signature made Do 25 Nov 2021 10:41:18 CET
gpg:                using RSA key F4FC70F07310028424EFC20A8E4256593F177720
gpg: Good signature from "Oliver Gugger <[email protected]>" [ultimate]
Primary key fingerprint: F4FC 70F0 7310 0284 24EF  C20A 8E42 5659 3F17 7720

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

cat manifest-v0.1.4-beta.txt

One can use the shasum -a 256 <file name here> tool in order to re-compute the sha256 hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

Finally, you can also verify the tag itself with the following command:

git verify-tag v0.1.4-beta

Verifying the Release Timestamp

From this new version onwards we'll also now timestamp the manifest file with OpenTimeStamps along with its signature. A new file is now included along with the rest of our release artifacts: manifest-v0.1.4-beta.sig.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following command:

ots verify manifest-v0.1.4-beta.sig.ots

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Changelog (auto-generated)

What's Changed

• github: create a daily build from master and lnd/daily-testing-only by @bhandras in #10
• README: fix init-wallet cmd by @erikarvstedt in #8
• readme: add Command Summary, Table of Contents by @thinkmassive in #12
• Dockerfile: set default 'checkout' ARG to 'main' by @thinkmassive in #17
• github: fix LNDINIT_VERSION to also match LND RCs by @thinkmassive in #18
• build: update to Go 1.18.3, use lnd v0.15.0 by default by @Roasbeef in #19

New Contributors

• @bhandras made their first contribution in #10
• @erikarvstedt made their first contribution in #8
• @thinkmassive made their first contribution in #12
• @Roasbeef made their first contribution in #19

Full Changelog: v0.1.3-beta...v0.1.4-beta

v0.1.3-beta

Release Notes

This release of lndinit contains bug fixes only.

Installation and configuration instructions can be found in the README.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import guggero's key from keybase:

curl https://keybase.io/guggero/pgp_keys.asc | gpg --import

Once you have his PGP key you can verify the release (assuming manifest-v0.1.3-beta.sig and manifest-v0.1.3-beta.txt are in the current directory) with:

gpg --verify manifest-v0.1.3-beta.sig manifest-v0.1.3-beta.txt

You should see the following if the verification was successful:

gpg: Signature made Do 25 Nov 2021 10:41:18 CET
gpg:                using RSA key F4FC70F07310028424EFC20A8E4256593F177720
gpg: Good signature from "Oliver Gugger <[email protected]>" [ultimate]
Primary key fingerprint: F4FC 70F0 7310 0284 24EF  C20A 8E42 5659 3F17 7720

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

cat manifest-v0.1.3-beta.txt

One can use the shasum -a 256 <file name here> tool in order to re-compute the sha256 hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

Finally, you can also verify the tag itself with the following command:

git verify-tag v0.1.3-beta

Verifying the Release Timestamp

From this new version onwards we'll also now timestamp the manifest file with OpenTimeStamps along with its signature. A new file is now included along with the rest of our release artifacts: manifest-v0.1.3-beta.sig.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following command:

ots verify manifest-v0.1.3-beta.sig.ots

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Changelog (auto-generated)

What's Changed

• store-secret: read up to EOF from stdin by @guggero in #7

Full Changelog: v0.1.2-beta...v0.1.3-beta

v0.1.2-beta

Release Notes

This release of lndinit contains bug fixes only.

Installation and configuration instructions can be found in the README.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import guggero's key from keybase:

curl https://keybase.io/guggero/pgp_keys.asc | gpg --import

Once you have his PGP key you can verify the release (assuming manifest-v0.1.2-beta.sig and manifest-v0.1.2-beta.txt are in the current directory) with:

gpg --verify manifest-v0.1.2-beta.sig manifest-v0.1.2-beta.txt

You should see the following if the verification was successful:

gpg: Signature made Do 25 Nov 2021 10:41:18 CET
gpg:                using RSA key F4FC70F07310028424EFC20A8E4256593F177720
gpg: Good signature from "Oliver Gugger <[email protected]>" [ultimate]
Primary key fingerprint: F4FC 70F0 7310 0284 24EF  C20A 8E42 5659 3F17 7720

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

cat manifest-v0.1.2-beta.txt

One can use the shasum -a 256 <file name here> tool in order to re-compute the sha256 hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

Finally, you can also verify the tag itself with the following command:

git verify-tag v0.1.2-beta

Verifying the Release Timestamp

From this new version onwards we'll also now timestamp the manifest file with OpenTimeStamps along with its signature. A new file is now included along with the rest of our release artifacts: manifest-v0.1.2-beta.sig.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following command:

ots verify manifest-v0.1.2-beta.sig.ots

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Changelog (auto-generated)

What's Changed

• main: don't pretty-print JSON by @guggero in #6
• Support standalone binary release by @guggero in #5
• Newline trim fix by @guggero in #4

Full Changelog: https://github.com/lightninglabs/lndinit/commits/v0.1.2-beta