Database Migrations

Note that downgrading from v0.7.1.rc-1 to previous tapd versions is not presently supported. You should create backups of tapd database state before upgrading to tapd v0.7.1.rc-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 the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/lightninglabs/taproot-assets/main/scripts/keys/roasbeef.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.7.1-rc1.sig and manifest-v0.7.1-rc1.txt are in the current directory) with:

gpg --verify manifest-roasbeef-v0.7.1-rc1.sig manifest-v0.7.1-rc1.txt

You should see the following if the verification was successful:

gpg: Signature made Wed Sep 30 17:35:20 2020 PDT
gpg:                using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.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 Timestamp

In addition to time-stamping the git tag with OpenTimestamps, we also timestamp the manifest file along with its signature. Two files are included in our release artifacts: manifest-roasbeef-v0.7.1-rc1.sig.ots and manifest-v0.7.1-rc1.txt.ots.

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

ots verify manifest-roasbeef-v0.7.1-rc1.sig.ots -f manifest-roasbeef-v0.7.1-rc1.sig
ots verify manifest-v0.7.1-rc1.txt.ots -f manifest-v0.7.1-rc1.txt

Alternatively, the OpenTimestamps website can be used to verify these timestamps if one doesn't have a bitcoind instance accessible locally.

Assuming you are using the OpenTimestamps ots-git-gpg-wrapper you can verify the timestamp of the git tag by verifying the tag as explained in Verifying the Release Binaries.

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

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.25.2, which is required by verifiers to arrive at the same ones.

The 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:

$ git verify-tag v0.7.1-rc1
gpg: Signature made Tue Sep 15 18:55:00 2020 PDT
gpg:                using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [ultimate]

Verifying the Docker Images

To verify the tapd and tapcli binaries inside the docker images against the signed, reproducible release binaries, there is a verification script in the image that can be called (before starting the container for example):

$ docker run --rm --entrypoint="" lightninglabs/taproot-assets:v0.7.1-rc1 /verify-install.sh v0.7.1-rc1
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/taproot-assets [command-line options]

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 vendor.tar.gz and tapd-source-v0.7.1-rc1.tar.gz are in the current directory, follow these steps:

tar -xvzf vendor.tar.gz
tar -xvzf tapd-source-v0.7.1-rc1.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.7.1-rc1" ./cmd/tapd
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.7.1-rc1" ./cmd/tapcli

The -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"

⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️

Release Notes (Curated)

See the in-repo release notes for a detailed list of high-level changes made since v0.7.0.

Release Notes (Auto-Generated)

• v0.7.1-rc1 by @jtobin in #1951
• loadtests: remove from tree by @jtobin in #1910
• build: update CI+release version to Go 1.25.2 by @Roasbeef in #1847
• tapchannel: no passive assets in funding proofs by @jtobin in #1943
• tapgarden: prevent shutdown on non-critical Custodian errors by @ffranr in #1941
• Use latest version of the migrate dependency by @ViktorT-11 in #1914
• tapd+sqlc: separate SQL migrations from code migrations by @ViktorT-11 in #1881
• GitHub CI: modularize LiT setup, add reusable cleanup action, and adopt matrix builds by @ffranr in #1889
• CI: add reusable cleanup workflow and clear Go caches by @ffranr in #1878
• Assorted release maintenance by @jtobin in #1891
• tapchannel+tapfreighter: add parcel height hint by @jtobin in #1920
• Keep tapd running when authmailbox subscription fails by @ffranr in #1915
• tapfreighter: pre-broadcast guard for split root witnesses by @ffranr in #1904
• Improve HTLC interceptor setup handling and fix itest flake by @ffranr in #1899
• tapchannel: address fault tolerance gap for initiator during channel funding by @Roasbeef in #1898
• asset: fix split witness writeback by @bhandras in #1897
• tapfreighter: add SendStateVerifyPreBroadcast and supporting proof reanchor helpers by @ffranr in #1884