Database Migrations

Note that downgrading from v0.7.0-rc2 to previous tapd versions is not presently supported. You should create backups of tapd database state before upgrading to tapd v0.7.0-rc2.

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.0-rc2.sig and manifest-v0.7.0-rc2.txt are in the current directory) with:

gpg --verify manifest-roasbeef-v0.7.0-rc2.sig manifest-v0.7.0-rc2.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.0-rc2.sig.ots and manifest-v0.7.0-rc2.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.0-rc2.sig.ots -f manifest-roasbeef-v0.7.0-rc2.sig
ots verify manifest-v0.7.0-rc2.txt.ots -f manifest-v0.7.0-rc2.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.24.6, 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.0-rc2
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.0-rc2 /verify-install.sh v0.7.0-rc2
$ 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.0-rc2.tar.gz are in the current directory, follow these steps:

tar -xvzf vendor.tar.gz
tar -xvzf tapd-source-v0.7.0-rc2.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.7.0-rc2" ./cmd/tapd
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.7.0-rc2" ./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.6.1.

Release Notes (auto-generated)

What's Changed Since v0.7.0-rc1

rpc: update new supply commit calls to use the global universe server rate limiter by @Roasbeef in #1785
tapd: add universe.disable-supply-verifier-chain-watch config flag by @ffranr in #1796
tools: migrate linter config to v2 by @jtobin in #1790
tapd: bump maxFeeRatio for funded psbts by @GeorgeTsagk in #1545
scripts: add jtobin release signing key by @jtobin in #1798
Mark pre-commit outputs spent on supply insert in supplyverifier by @ffranr in #1797
scripts: add darioanongba signing key by @darioAnongba in #1803
scripts: signing key maintenance by @jtobin in #1806
supplycommit+rpcserver: move ignore asset logic from RPC server to supplycommit pkg by @ffranr in #1801
rfq+taprpc: add asset ID and group key to PeerAccepted[Buy/Sell]Quote by @ffranr in #1805
allow building taprpc by itself by @ZZiigguurraatt in #1789
gemini: add config and style guidelines by @Roasbeef in #1804
Bump go to v1.24.6 by @GeorgeTsagk in #1815
cmd: add locator args to supplycommit fetch by @jtobin in #1819
tapdb: fix flaky TestQueryMessages due to close timestamps by @ffranr in #1816
itest: introduce rpcassert package with RPC helpers to reduce flakes by @ffranr in #1799
cli: include unset and zero-valued proto fields in JSON output by @ffranr in #1821
Filter AddrReceives by timestamp by @darioAnongba in #1794
Add support for fetching latest supply commitment via new locator type by @ffranr in #1823
itest: fix address receives test: timestamp in the future by @darioAnongba in #1828
taprpc: upgrade falafel to v0.9.2 by @darioAnongba in #1827
Full asset burn by @darioAnongba in #1791
tapgarden: harden MockKeyRing and fix flaky queueSeedlingsInBatch test by @ffranr in #1824
universerpc+itest: add and verify string outpoint in SupplyCommitChainData by @ffranr in #1822
Extract supply pre-commits from mint leaves during supply verifier sync by @ffranr in #1820
docs: add docs that detail the asset chan funding process by @Roasbeef in #1783
docs: add docs on e2e RFQ arch by @Roasbeef in #1787
taprpc+itest: whitelist FetchSupplyLeaves RPC and add integration test by @ffranr in #1829
Add block header support to supply RPCs and related integration tests by @ffranr in #1839
tapdb: error on dirty database versions by @ViktorT-11 in #1826
proof+tapsend: sanity-check STXO proof structure at creation time by @ffranr in #1836
rfq+server: properly configure gRPC keep alive settings for client+server by @Roasbeef in #1834
Feature bits by @GeorgeTsagk in #1748
Prepare tap channels for v1 proofs by @GeorgeTsagk in #1779
githubci: update Litd itest branch by @GeorgeTsagk in #1852
Improve troubleshooting logs for bug reports 1845 and 1850 by @ffranr in #1853
rpcserver: NewAddr universal courier connectivity check, offline skip, and local asset precheck by @ffranr in #1854
build: bump version to v0.7.0-rc2 by @jtobin in #1851

New Contributors

@ZZiigguurraatt made their first contribution in #1789

Full Changelog: v0.7.0-rc1...v0.7.0-rc2

lightninglabs/taproot-assets v0.7.0-rc2 on GitHub