Database Migrations

There is a database migration in this version, therefore downgrading to a previous version after installing v0.3.2-alpha.rc2 is not supported.

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

gpg --verify manifest-roasbeef-v0.3.2-rc2.sig manifest-v0.3.2-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

From this new version onwards, in addition time-stamping the git tag with OpenTimestamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts: manifest-roasbeef-v0.3.2-rc2.txt.asc.ots.

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

ots verify manifest-roasbeef-v0.3.2-rc2.sig.ots -f manifest-roasbeef-v0.3.2-rc2.sig

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

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.21.4, 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.3.2-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.3.2-rc2 /verify-install.sh v0.3.2-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.3.2-rc2.tar.gz are in the current directory, follow these steps:

tar -xvzf vendor.tar.gz
tar -xvzf tapd-source-v0.3.2-rc2.tar.gz
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.3.2-rc2" ./cmd/tapd
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.3.2-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 (auto generated)

What's Changed

Add GitHub CD release build workflow by @ffranr in #661
Expose anchor point in AssetStats by @GeorgeTsagk in #667
build(deps): bump go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc from 0.28.0 to 0.46.0 by @dependabot in #676
taprpc: change getinfo REST endpoint from POST to GET by @ffranr in #669
chain_bridge: fetch block headers over blocks when verifying proofs by @jharveyb in #660
universe: fix log entry when sync fails by @Roasbeef in #682
Check for existing asset in db before attempting to insert a new asset. by @ffranr in #687
split enableEmission into newGroupedAsset and groupedAsset by @jharveyb in #681
build: bump version to v0.3.2-alpha.rc1 by @Roasbeef in #688
chore: fix typos by @xiaolou86 in #686
build: fix github actions to ensure release artefacts are uploaded by @Roasbeef in #695
rpc+rpcserver: fix batch state typo by @GeorgeTsagk in #692
Drop and re-create genesis_info_view by @GeorgeTsagk in #689
Custodian emits a new asset-receive-complete event to notification subscribers by @ffranr in #659
build: bump Go version to Go 1.21.4 by @Roasbeef in #696
build: bump version to v0.3.2-alpha.rc2 by @ffranr in #702
taprpc: add missing cli autogen docs by @jharveyb in #703

New Contributors

@dependabot made their first contribution in #676
@xiaolou86 made their first contribution in #686

Full Changelog: v0.3.1...v0.3.2-rc2

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