Skip to content

v0.3.3-alpha
Compare
Choose a tag to compare
@github-actions github-actions released this 08 Feb 20:32
· 1399 commits to main since this release
v0.3.3
aa1f3b1

This is a minor release that includes a series of bug fixes and enhancements. Most notably, the process of sending+receiving proof files when sending+receiving assets is now more robust. In addition, the resource requirements for running a public Universe server have been reduced.

Database Migrations

This contains a migration in the form of a new table to allow for reliable transmission of proof files when sending/receiving. And an update to an existing table that fixes a bug with the order of asset witnesses.

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

gpg --verify manifest-roasbeef-v0.3.3.sig manifest-v0.3.3.txt

You should see the following if the verification was successful:

gpg: Signature made Thu Feb  8 12:29:49 2024 PST
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.3.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.3.sig.ots -f manifest-roasbeef-v0.3.3.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.3
gpg: Signature made Wed 07 Feb 2024 10:58:03 PM UTC using RSA key ID 9B280306
gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>"

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

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

Full Changelog: v0.3.2...v0.3.3

What's Changed

  • A resource lease affecting active TCPs connections for Universe servers has been resolved: #719
  • tapd is now able to export additional Prometheus metrics: #716
  • A retry loop has been added to the process of exporting new proofs to Universe servers: #698
  • The proof courier will now more robustly attempt to obtain proofs to complete receives after a restart: #734
  • The integration tests system now covers all possible proof courier types: #712
  • tapd will now log any executed database migrations during start up: #772
  • Users can now side load proofs using the Universe RPC calls to complete a receive flow: #726
  • An edge case related to re-used script keys has been resolved, and the receive process now properly consults the local proof archive to short circuit logic. In addition, proofs stored on disk now contain an outpoint prefix to avoid over writing proofs: #730
Assets 17
Loading