v0.13.4

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

You should now be able to list all of guggero's keys:

gpg --list-keys --with-subkey-fingerprints F4FC70F07310028424EFC20A8E4256593F177720

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

gpg --verify manifest-v0.13.4.sig manifest-v0.13.4.txt

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 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. Make sure the key used for the signature is listed in the output of the gpg --list-keys command from above.

Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes (which are

cat manifest-v0.13.4.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.13.4

What's Changed

• makeoffer: use correct keys by @guggero in #159
• go.mod: update lnd to v0.18.3-beta by @starius in #161
• build(deps): bump github.com/jackc/pgx/v5 from 5.3.1 to 5.5.4 by @dependabot in #163
• build(deps): bump github.com/opencontainers/runc from 1.1.12 to 1.1.14 by @dependabot in #162
• build(deps): bump github.com/btcsuite/btcd from 0.24.0 to 0.24.2 in /tools by @dependabot in #164
• root+doc: change default API server to api.node-recovery.com by @guggero in #165

Full Changelog: v0.13.3...v0.13.4

v0.13.3

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

You should now be able to list all of guggero's keys:

gpg --list-keys --with-subkey-fingerprints F4FC70F07310028424EFC20A8E4256593F177720

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

gpg --verify manifest-v0.13.3.sig manifest-v0.13.3.txt

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 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. Make sure the key used for the signature is listed in the output of the gpg --list-keys command from above.

Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes (which are

cat manifest-v0.13.3.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.13.3

What's Changed

• Fix sweeptimelockmanual, bump version to v0.13.3 by @guggero in #157

Full Changelog: v0.13.2...v0.13.3

v0.13.2

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

You should now be able to list all of guggero's keys:

gpg --list-keys --with-subkey-fingerprints F4FC70F07310028424EFC20A8E4256593F177720

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

gpg --verify manifest-v0.13.2.sig manifest-v0.13.2.txt

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 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. Make sure the key used for the signature is listed in the output of the gpg --list-keys command from above.

Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes (which are

cat manifest-v0.13.2.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.13.2

What's Changed

• build(deps): bump github.com/btcsuite/btcd from 0.23.4 to 0.24.0 in /tools by @dependabot in #134
• gitignore: .idea folder by @hieblmi in #137
• signpsbt: allow signing multiple inputs by @guggero in #142
• update dependencies (LND v0.18.0-beta and co) by @starius in #138
• btc: filter address outputs, only return unspent by @guggero in #143
• Fixed typo in chantools_zombierecovery.md by @drmartinberger in #144
• Update readme with latest command line helptext. by @hieblmi in #145
• rescueclosed: make number of keys configurable by @guggero in #146
• zombierecovery: support MuSig2 to rescue Simple Taproot channels by @guggero in #141

New Contributors

• @hieblmi made their first contribution in #137
• @drmartinberger made their first contribution in #144

Full Changelog: v0.13.1...v0.13.2

v0.13.1

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

You should now be able to list all of guggero's keys:

gpg --list-keys --with-subkey-fingerprints F4FC70F07310028424EFC20A8E4256593F177720

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

gpg --verify manifest-v0.13.1.sig manifest-v0.13.1.txt

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 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. Make sure the key used for the signature is listed in the output of the gpg --list-keys command from above.

Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes (which are

cat manifest-v0.13.1.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.13.1

What's Changed

• build(deps): bump github.com/docker/docker from 24.0.7+incompatible to 24.0.9+incompatible by @dependabot in #127
• signpsbt+lnd: fix signing for P2WKH by @guggero in #129
• build(deps): bump golang.org/x/net from 0.21.0 to 0.23.0 by @dependabot in #130
• triggerforceclose: make compatible with all nodes, add Tor support by @guggero in #132

Full Changelog: v0.13.0...v0.13.1

v0.13.0

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

You should now be able to list all of guggero's keys:

gpg --list-keys --with-subkey-fingerprints F4FC70F07310028424EFC20A8E4256593F177720

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

gpg --verify manifest-v0.13.0.sig manifest-v0.13.0.txt

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 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. Make sure the key used for the signature is listed in the output of the gpg --list-keys command from above.

Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes (which are

cat manifest-v0.13.0.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.13.0

What's Changed

• doublespendinputs: allow RBF per default by @Tetrix42 in #118
• Fix Partial Signature Signing. by @ziggie1984 in #120
• signmessage: add signmessage cmd by @sputn1ck in #121
• build(deps): bump github.com/jackc/pgx/v4 from 4.18.1 to 4.18.2 by @dependabot in #125
• build(deps): bump google.golang.org/protobuf from 1.28.0 to 1.33.0 in /tools by @dependabot in #126
• recoverloopin: Sqlite option by @sputn1ck in #113
• Add createwallet and signpsbt subcommands by @guggero in #124

New Contributors

• @Tetrix42 made their first contribution in #118

Full Changelog: v0.12.2...v0.13.0

v0.12.2

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

You should now be able to list all of guggero's keys:

gpg --list-keys --with-subkey-fingerprints F4FC70F07310028424EFC20A8E4256593F177720

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

gpg --verify manifest-v0.12.2.sig manifest-v0.12.2.txt

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 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. Make sure the key used for the signature is listed in the output of the gpg --list-keys command from above.

Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes (which are

cat manifest-v0.12.2.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.12.2

What's Changed

• recoverloopin: allow setting output value by @sputn1ck in #114
• zombierecovery: add --matchonly flag to makeoffer, --numkeys to preparekeys by @guggero in #117

Full Changelog: v0.12.1...v0.12.2

v0.12.1

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

You should now be able to list all of guggero's keys:

gpg --list-keys --with-subkey-fingerprints F4FC70F07310028424EFC20A8E4256593F177720

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

gpg --verify manifest-v0.12.1.sig manifest-v0.12.1.txt

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 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. Make sure the key used for the signature is listed in the output of the gpg --list-keys command from above.

Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes (which are

cat manifest-v0.12.1.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.12.1

What's Changed

• build(deps): bump google.golang.org/grpc from 1.53.0 to 1.56.3 by @dependabot in #88
• build(deps): bump go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc from 0.25.0 to 0.46.0 by @dependabot in #93
• Update zombierecovery.md by @YuckFouBTC in #92
• build(deps): bump golang.org/x/crypto from 0.5.0 to 0.17.0 in /tools by @dependabot in #104
• build(deps): bump golang.org/x/crypto from 0.14.0 to 0.17.0 by @dependabot in #103
• sweeptimelockmanual: allow specifying the backup file directly by @guggero in #91
• sweepremoteclosed: add support for simple taproot channels by @guggero in #106
• multi: add new pullanchor command by @guggero in #100
• pullanchor: account for all anchor outputs. by @ziggie1984 in #109
• Support P2TR as sweep/change address everywhere by @guggero in #107

New Contributors

• @YuckFouBTC made their first contribution in #92

Full Changelog: v0.12.0...v0.12.1

v0.12.0

Changelog

• Update to lnd v0.17.0-beta compatibility.
• New dropgraphzombies command for forcing a re-sync of lnd's graph.
• Bug fixes.
• Add public signet support.
• Add more debug info to channels in dumpchannels command.

Full Changelog: v0.11.3...v0.12.0

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

You should now be able to list all of guggero's keys:

gpg --list-keys --with-subkey-fingerprints F4FC70F07310028424EFC20A8E4256593F177720

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

gpg --verify manifest-v0.12.0.sig manifest-v0.12.0.txt

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 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. Make sure the key used for the signature is listed in the output of the gpg --list-keys command from above.

Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes (which are

cat manifest-v0.12.0.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.12.0

v0.11.3

Changelog

• New doublespendinputs command for replacing an existing transaction in the mempool with a new one.
• Bug fixes.
• Update README with more information (DOs and DON'Ts) about using the tool.
• Update README with an overview table that describes each command in a bit more detail.

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

You should now be able to list all of guggero's keys:

gpg --list-keys --with-subkey-fingerprints F4FC70F07310028424EFC20A8E4256593F177720

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

gpg --verify manifest-v0.11.3.sig manifest-v0.11.3.txt

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 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. Make sure the key used for the signature is listed in the output of the gpg --list-keys command from above.

Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes (which are

cat manifest-v0.11.3.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.11.3

v0.11.2

Changelog

• Bug fixes

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

You should now be able to list all of guggero's keys:

gpg --list-keys --with-subkey-fingerprints F4FC70F07310028424EFC20A8E4256593F177720

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

gpg --verify manifest-v0.11.2.sig manifest-v0.11.2.txt

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 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. Make sure the key used for the signature is listed in the output of the gpg --list-keys command from above.

Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes (which are

cat manifest-v0.11.2.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.11.2