NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #2754 by repository stars
Latest stable
v0.8.8
Last release 13 days ago
09 Nov 2026
Ships on a steady schedule
a new release about every 9 days
Nearly every release is documented
notes for 25 of 26 stable releases
Nothing withdrawn
no release was ever pulled
4 years old
1150 releases · first in 2023
Drag across the ruler to compare, or tap a release to open it.
This release fixes a regression introduced in v0.8.6 that could prevent asset invoices from settling.
This release fixes a regression introduced in v0.8.6 that could prevent asset invoices from settling.
See the full changes since v0.8.7.
The release tag points to commit 6e0fef585a972426723dc953f483cfe5109949b9.
There are no new database migrations relative to v0.8.8. Back up your databases before upgrading.
If you use Taproot Assets channels, follow the operational safety guidelines and arrange a controlled update of affected nodes. Users upgrading from a version older than v0.8.6 must also review the v0.8.6 upgrade instructions, including the guidance for nodes with a configured RFQ oracle. Restarting a node does not clear pending HTLCs.
Download the archive for your platform, manifest-v0.8.8.txt, and manifest-roasbeef-v0.8.8.sig. The detached PGP signature authenticates the manifest, which contains the SHA-256 hashes of the release archives and binaries.
Download the release signing key and check that its primary fingerprint is A5B61896952D9FDA83BC054CDC42612E89237182 before importing it:
gpg --show-keys --with-fingerprint roasbeef.asc
gpg --import roasbeef.asc
gpg --verify manifest-roasbeef-v0.8.8.sig manifest-v0.8.8.txt
shasum -a 256 <downloaded-archive>
Compare the archive hash with its entry in manifest-v0.8.8.txt.
The manifest and signature also have OpenTimestamps proofs:
ots verify manifest-v0.8.8.txt.ots
ots verify manifest-roasbeef-v0.8.8.sig.ots
Bitcoin confirmation is required to verify the timestamp attestation. If a proof reports pending confirmation, retry after the confirmations arrive.
The release binaries are built with Go 1.27.3. From the v0.8.8 source tag, run:
make docker-release tag=v0.8.8
To build a single platform, add sys=<OS-ARCH>. The release also includes taproot-assets-source-v0.8.8.tar.gz and vendor.tar.gz for a contained rebuild. See the reproducible build guide for the build and verification steps. Compare the resulting hashes with the entries in manifest-v0.8.8.txt.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
In this release, we rebuild tapd and tapcli with Go 1.27.3 to address CVE-2026-111943. Go's crypto/x509 verifier now rejects certificate chains contai…
In this release, we rebuild tapd and tapcli with Go 1.27.3 to address
CVE-2026-111943. Go's
crypto/x509 verifier now rejects certificate chains containing a specific
set of intermediate certificates due to security concerns around their
operation. We recommend that all users upgrade.
Updating the Go installation on a host does not patch an existing binary.
Install the new release binaries, or rebuild from the v0.8.7 tag with
Go 1.27.3.
See the release-specific notes and full changes since v0.8.6.
The release tag points to commit
5be24d78f5bb7fe6628f1564817db3257cb4272a.
There are no new database migrations relative to v0.8.6. Back up your databases before upgrading.
If you use Taproot Assets channels, follow the operational safety guidelines and arrange a controlled update of affected nodes. Users upgrading from a version older than v0.8.6 must also review the v0.8.6 upgrade instructions, including the guidance for nodes with a configured RFQ oracle. Restarting a node does not clear pending HTLCs.
Download the archive for your platform, manifest-v0.8.7.txt, and
manifest-roasbeef-v0.8.7.sig. The detached PGP signature authenticates the
manifest, which contains the SHA-256 hashes of the release archives and
binaries.
Download the release signing key
and check that its primary fingerprint is
A5B61896952D9FDA83BC054CDC42612E89237182 before importing it:
gpg --show-keys --with-fingerprint roasbeef.asc
gpg --import roasbeef.asc
gpg --verify manifest-roasbeef-v0.8.7.sig manifest-v0.8.7.txt
shasum -a 256 <downloaded-archive>
Compare the archive hash with its entry in manifest-v0.8.7.txt.
The manifest and signature also have OpenTimestamps proofs:
ots verify manifest-v0.8.7.txt.ots
ots verify manifest-roasbeef-v0.8.7.sig.ots
Bitcoin confirmation is required to verify the timestamp attestation. If a proof reports pending confirmation, retry after the confirmations arrive.
The release binaries are built with Go 1.27.3. From the v0.8.7 source tag,
run:
make docker-release tag=v0.8.7
To build a single platform, add sys=<OS-ARCH>. The release also includes
taproot-assets-source-v0.8.7.tar.gz and vendor.tar.gz for a contained
rebuild. See the reproducible build guide
for the build and verification steps. Compare the resulting hashes with
the entries in manifest-v0.8.7.txt.
This release tightens RFQ handling edge cases, address decoding, and proof verification. The signed v0.8.6 tag points to commit 734ce74dd1e816a833a972
This release tightens RFQ handling edge cases, address decoding, and proof verification. The signed v0.8.6 tag points to commit 734ce74dd1e816a833a9727bba741718019fef18.
If you were running a tapd node with a configured oracle, you must update due to an important bug fix.
rejecthtlc=true in lnd.conf (or lnd.rejecthtlc=true in LiT's lit.conf). Check affected channels with lncli listchannels, then settle or reconcile pending HTLCs before replacing binaries. Restarting does not clear pending HTLCs.rejecthtlc blocks onward HTLCs. A node can still send and receive its own payments. The default asset invoice expiry is 5 minutes and is separate from the quote lifetime.
Verify the signed tag with git verify-tag v0.8.6. The developer public keys are in scripts/keys.
Download manifest-v0.8.6.txt and the archive for your platform. Run shasum -a 256 <archive> and compare the result with that archive's entry in the manifest. The release also includes taproot-assets-source-v0.8.6.tar.gz and vendor.tar.gz for a contained rebuild; see the reproducible build guide.
The release archives were built with Go 1.26.3. The Linux amd64 tapd binary records the tagged commit as its VCS revision and reports a clean source tree. The manifest currently has no detached GPG signature or OpenTimestamps files attached, so verification of the manifest itself depends on reproducing the build or another trusted copy.
This release initiates an upgrade of the Taproot Assets transition proof format. Existing users must upgrade to v0.8.5 before block 971,750 (expected
This release initiates an upgrade of the Taproot Assets transition proof format. Existing users must upgrade to v0.8.5 before block 971,750 (expected date, October 17th, 2026) or their proofs may be rejected by updated Universe servers.
Specifically, upgraded clients will refuse to verify legacy proof formats confirming on or after block 971,750, so attempting to send assets using older tapd versions will create invalid transition proofs from that block onwards.
Additionally, existing asset channels must be upgraded before block 971,750. To upgrade, both peers must upgrade to v0.8.5, and then any kind of state update must occur on the channel (e.g. a payment or keysend) before block 971,750. A safe route, if a peer cannot be trusted to upgrade and update state in time, is to just close existing asset channels with it, and reopen only after upgrading. Note that the close, cooperative or force, must confirm before block 971,750.
For more details see the proof activation guide, especially the 'Migrating a channel' section.
Note that downgrading from v0.8.5 to previous tapd versions is not presently supported. You should create backups of tapd database state before upgrading to tapd v0.8.5.
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.8.5.sig and manifest-v0.8.5.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.8.5.sig manifest-v0.8.5.txt
You should see the following if the verification was successful:
gpg: Signature made Thu Oct 1 18:52:23 2026 PDT
gpg: using EDDSA key 296212681AADF05656A2CDEE90525F7DEEE0AD86
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.
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.8.5.sig.ots and manifest-v0.8.5.txt.ots.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-roasbeef-v0.8.5.sig.ots -f manifest-roasbeef-v0.8.5.sig
ots verify manifest-v0.8.5.txt.ots -f manifest-v0.8.5.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.
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.26.3, 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.8.5
gpg: Signature made Thu Oct 1 18:14:35 2026 PDT
gpg: using EDDSA key 296212681AADF05656A2CDEE90525F7DEEE0AD86
gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [ultimate]
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.8.5 /verify-install.sh v0.8.5
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/taproot-assets [command-line options]
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.8.5.tar.gz are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf tapd-source-v0.8.5.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.5" ./cmd/tapd
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.5" ./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"
⚡ ⚡ ⚡ See the in-repo release notes for other high-level changes made since v0.8.4. ⚡ ⚡ ⚡
Note that downgrading from v0.8.4 to previous tapd versions is not presently supported. You should create backups of tapd database state before upgrad
Note that downgrading from v0.8.4 to previous tapd versions is not presently supported. You should create backups of tapd database state before upgrading to tapd v0.8.4.
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.8.4.sig and manifest-v0.8.4.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.8.4.sig manifest-v0.8.4.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.
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.8.4.sig.ots and manifest-v0.8.4.txt.ots.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-roasbeef-v0.8.4.sig.ots -f manifest-roasbeef-v0.8.4.sig
ots verify manifest-v0.8.4.txt.ots -f manifest-v0.8.4.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.
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.26.3, 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.8.4
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]
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.8.4 /verify-install.sh v0.8.4
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/taproot-assets [command-line options]
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.8.4.tar.gz are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf tapd-source-v0.8.4.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.4" ./cmd/tapd
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.4" ./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"
⚡ ⚡ ⚡ See the in-repo release notes for a detailed list of high-level changes made since v0.8.3. ⚡ ⚡ ⚡
Tag generated using command make release-tag .
Tag generated using command make release-tag.
Note that downgrading from v0.8.3 to previous tapd versions is not presently supported. You should create backups of tapd database state before upgrad
Note that downgrading from v0.8.3 to previous tapd versions is not presently supported. You should create backups of tapd database state before upgrading to tapd v0.8.3.
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.8.3.sig and manifest-v0.8.3.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.8.3.sig manifest-v0.8.3.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.
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.8.3.sig.ots and manifest-v0.8.3.txt.ots.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-roasbeef-v0.8.3.sig.ots -f manifest-roasbeef-v0.8.3.sig
ots verify manifest-v0.8.3.txt.ots -f manifest-v0.8.3.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.
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.26.3, 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.8.3
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]
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.8.3 /verify-install.sh v0.8.3
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/taproot-assets [command-line options]
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.8.3.tar.gz are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf tapd-source-v0.8.3.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.3" ./cmd/tapd
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.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"
⚡ ⚡ ⚡ See the in-repo release notes for a detailed list of high-level changes made since v0.8.2. ⚡ ⚡ ⚡
Tag generated using command make release-tag .
Tag generated using command make release-tag.
Note that downgrading from v0.8.2 to previous tapd versions is not presently supported. You should create backups of tapd database state before upgrad
Note that downgrading from v0.8.2 to previous tapd versions is not presently supported. You should create backups of tapd database state before upgrading to tapd v0.8.2.
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.8.2.sig and manifest-v0.8.2.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.8.2.sig manifest-v0.8.2.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.
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.8.2.sig.ots and manifest-v0.8.2.txt.ots.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-roasbeef-v0.8.2.sig.ots -f manifest-roasbeef-v0.8.2.sig
ots verify manifest-v0.8.2.txt.ots -f manifest-v0.8.2.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.
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.26.3, 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.8.2
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]
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.8.2 /verify-install.sh v0.8.2
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/taproot-assets [command-line options]
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.8.2.tar.gz are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf tapd-source-v0.8.2.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.2" ./cmd/tapd
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.2" ./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"
⚡ ⚡ ⚡ See the in-repo release notes for a detailed list of high-level changes made since v0.8.1. ⚡ ⚡ ⚡
Tag generated using command make release-tag .
Tag generated using command make release-tag.
Tag generated using command make release-tag .
Tag generated using command make release-tag.
Tag generated using command make release-tag .
Tag generated using command make release-tag.
Note that downgrading from v0.8.1 to previous tapd versions is not presently supported. You should create backups of tapd database state before upgrad
Note that downgrading from v0.8.1 to previous tapd versions is not presently supported. You should create backups of tapd database state before upgrading to tapd v0.8.1.
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.8.1.sig and manifest-v0.8.1.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.8.1.sig manifest-v0.8.1.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.
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.8.1.sig.ots and manifest-v0.8.1.txt.ots.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-roasbeef-v0.8.1.sig.ots -f manifest-roasbeef-v0.8.1.sig
ots verify manifest-v0.8.1.txt.ots -f manifest-v0.8.1.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.
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.26.3, 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.8.1
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]
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.8.1 /verify-install.sh v0.8.1
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/taproot-assets [command-line options]
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.8.1.tar.gz are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf tapd-source-v0.8.1.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.1" ./cmd/tapd
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.1" ./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"
⚡ ⚡ ⚡ See the in-repo release notes for a detailed list of high-level changes made since v0.8.0. ⚡ ⚡ ⚡
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
TODO
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.8.1-rc3.sig and manifest-v0.8.1-rc3.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.8.1-rc3.sig manifest-v0.8.1-rc3.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.
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.8.1-rc3.sig.ots and manifest-v0.8.1-rc3.txt.ots.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-roasbeef-v0.8.1-rc3.sig.ots -f manifest-roasbeef-v0.8.1-rc3.sig
ots verify manifest-v0.8.1-rc3.txt.ots -f manifest-v0.8.1-rc3.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.
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.26.3, 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.8.1-rc3
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]
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.8.1-rc3 /verify-install.sh v0.8.1-rc3
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/taproot-assets [command-line options]
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.8.1-rc3.tar.gz are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf tapd-source-v0.8.1-rc3.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.1-rc3" ./cmd/tapd
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.1-rc3" ./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! ⚡️⚡️⚡️
TODO
TODO
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
TODO
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.8.1-rc2.sig and manifest-v0.8.1-rc2.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.8.1-rc2.sig manifest-v0.8.1-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.
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.8.1-rc2.sig.ots and manifest-v0.8.1-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.8.1-rc2.sig.ots -f manifest-roasbeef-v0.8.1-rc2.sig
ots verify manifest-v0.8.1-rc2.txt.ots -f manifest-v0.8.1-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.
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.26.3, 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.8.1-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]
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.8.1-rc2 /verify-install.sh v0.8.1-rc2
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/taproot-assets [command-line options]
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.8.1-rc2.tar.gz are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf tapd-source-v0.8.1-rc2.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.1-rc2" ./cmd/tapd
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.1-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! ⚡️⚡️⚡️
TODO
TODO
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
TODO
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.8.1-rc1.sig and manifest-v0.8.1-rc1.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.8.1-rc1.sig manifest-v0.8.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.
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.8.1-rc1.sig.ots and manifest-v0.8.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.8.1-rc1.sig.ots -f manifest-roasbeef-v0.8.1-rc1.sig
ots verify manifest-v0.8.1-rc1.txt.ots -f manifest-v0.8.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.
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.26.3, 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.8.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]
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.8.1-rc1 /verify-install.sh v0.8.1-rc1
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/taproot-assets [command-line options]
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.8.1-rc1.tar.gz are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf tapd-source-v0.8.1-rc1.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.1-rc1" ./cmd/tapd
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.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! ⚡️⚡️⚡️
TODO
TODO
Note that downgrading from v0.8.0 to previous tapd versions is not presently supported. You should create backups of tapd database state before upgrad
Note that downgrading from v0.8.0 to previous tapd versions is not presently supported. You should create backups of tapd database state before upgrading to tapd v0.8.0.
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.8.0.sig and manifest-v0.8.0.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.8.0.sig manifest-v0.8.0.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.
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.8.0.sig.ots and manifest-v0.8.0.txt.ots.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-roasbeef-v0.8.0.sig.ots -f manifest-roasbeef-v0.8.0.sig
ots verify manifest-v0.8.0.txt.ots -f manifest-v0.8.0.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.
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.26.3, 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.8.0
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]
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.8.0 /verify-install.sh v0.8.0
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/taproot-assets [command-line options]
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.8.0.tar.gz are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf tapd-source-v0.8.0.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.0" ./cmd/tapd
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.0" ./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! ⚡️⚡️⚡️
See the in-repo release notes for a detailed list of high-level changes made since v0.7.2.
InternalPortfolioPilot and initial ResolveRequest wiring by @ffranr in https://github.com/lightninglabs/taproot-assets/pull/1912MintingBatch.Copy tests with seedlings coverage by @ffranr in https://github.com/lightninglabs/taproot-assets/pull/1918BakeMacaroon RPC and tapcli support by @ffranr in https://github.com/lightninglabs/taproot-assets/pull/1960PortfolioPilot by @ffranr in https://github.com/lightninglabs/taproot-assets/pull/1954unit CI with optional verbosity and package parallelism by @ffranr in https://github.com/lightninglabs/taproot-assets/pull/1970isAssetInvoice check by @GeorgeTsagk in https://github.com/lightninglabs/taproot-assets/pull/2009ComputeView by @GeorgeTsagk in https://github.com/lightninglabs/taproot-assets/pull/1919Full Changelog: https://github.com/lightninglabs/taproot-assets/compare/v0.7.2...v0.8.0
Note that downgrading from v0.8.0-rc3 to previous tapd versions is not presently supported. You should create backups of tapd database state before up
Note that downgrading from v0.8.0-rc3 to previous tapd versions is not presently supported. You should create backups of tapd database state before upgrading to tapd v0.8.0-rc3.
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.8.0-rc3.sig and manifest-v0.8.0-rc3.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.8.0-rc3.sig manifest-v0.8.0-rc3.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.
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.8.0-rc3.sig.ots and manifest-v0.8.0-rc3.txt.ots.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-roasbeef-v0.8.0-rc3.sig.ots -f manifest-roasbeef-v0.8.0-rc3.sig
ots verify manifest-v0.8.0-rc3.txt.ots -f manifest-v0.8.0-rc3.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.
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.26.3, 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.8.0-rc3
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]
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.8.0-rc3 /verify-install.sh v0.8.0-rc3
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/taproot-assets [command-line options]
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.8.0-rc3.tar.gz are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf tapd-source-v0.8.0-rc3.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.0-rc3" ./cmd/tapd
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.0-rc3" ./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! ⚡️⚡️⚡️
See the in-repo release notes for a detailed list of high-level changes made since v0.7.2.
InternalPortfolioPilot and initial ResolveRequest wiring by @ffranr in https://github.com/lightninglabs/taproot-assets/pull/1912MintingBatch.Copy tests with seedlings coverage by @ffranr in https://github.com/lightninglabs/taproot-assets/pull/1918BakeMacaroon RPC and tapcli support by @ffranr in https://github.com/lightninglabs/taproot-assets/pull/1960PortfolioPilot by @ffranr in https://github.com/lightninglabs/taproot-assets/pull/1954unit CI with optional verbosity and package parallelism by @ffranr in https://github.com/lightninglabs/taproot-assets/pull/1970isAssetInvoice check by @GeorgeTsagk in https://github.com/lightninglabs/taproot-assets/pull/2009ComputeView by @GeorgeTsagk in https://github.com/lightninglabs/taproot-assets/pull/1919Full Changelog: https://github.com/lightninglabs/taproot-assets/compare/v0.7.2...v0.8.0-rc3
Note that downgrading from v0.8.0-rc2 to previous tapd versions is not presently supported. You should create backups of tapd database state before up
Note that downgrading from v0.8.0-rc2 to previous tapd versions is not presently supported. You should create backups of tapd database state before upgrading to tapd v0.8.0-rc2.
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.8.0-rc2.sig and manifest-v0.8.0-rc2.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.8.0-rc2.sig manifest-v0.8.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.
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.8.0-rc2.sig.ots and manifest-v0.8.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.8.0-rc2.sig.ots -f manifest-roasbeef-v0.8.0-rc2.sig
ots verify manifest-v0.8.0-rc2.txt.ots -f manifest-v0.8.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.
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.5, 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.8.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]
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.8.0-rc2 /verify-install.sh v0.8.0-rc2
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/taproot-assets [command-line options]
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.8.0-rc2.tar.gz are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf tapd-source-v0.8.0-rc2.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.0-rc2" ./cmd/tapd
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.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! ⚡️⚡️⚡️
See the in-repo release notes for a detailed list of high-level changes made since v0.7.2.
InternalPortfolioPilot and initial ResolveRequest wiring by @ffranr in https://github.com/lightninglabs/taproot-assets/pull/1912MintingBatch.Copy tests with seedlings coverage by @ffranr in https://github.com/lightninglabs/taproot-assets/pull/1918BakeMacaroon RPC and tapcli support by @ffranr in https://github.com/lightninglabs/taproot-assets/pull/1960PortfolioPilot by @ffranr in https://github.com/lightninglabs/taproot-assets/pull/1954unit CI with optional verbosity and package parallelism by @ffranr in https://github.com/lightninglabs/taproot-assets/pull/1970isAssetInvoice check by @GeorgeTsagk in https://github.com/lightninglabs/taproot-assets/pull/2009ComputeView by @GeorgeTsagk in https://github.com/lightninglabs/taproot-assets/pull/1919Full Changelog: https://github.com/lightninglabs/taproot-assets/compare/v0.7.2...v0.8.0-rc2
Note that downgrading from v0.8.0-rc1 to previous tapd versions is not presently supported. You should create backups of tapd database state before up
Note that downgrading from v0.8.0-rc1 to previous tapd versions is not presently supported. You should create backups of tapd database state before upgrading to tapd v0.8.0-rc1.
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.8.0-rc1.sig and manifest-v0.8.0-rc1.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.8.0-rc1.sig manifest-v0.8.0-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.
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.8.0-rc1.sig.ots and manifest-v0.8.0-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.8.0-rc1.sig.ots -f manifest-roasbeef-v0.8.0-rc1.sig
ots verify manifest-v0.8.0-rc1.txt.ots -f manifest-v0.8.0-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.
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.5, 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.8.0-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]
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.8.0-rc1 /verify-install.sh v0.8.0-rc1
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/taproot-assets [command-line options]
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.8.0-rc1.tar.gz are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf tapd-source-v0.8.0-rc1.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.0-rc1" ./cmd/tapd
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.8.0-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! ⚡️⚡️⚡️
See the in-repo release notes for a detailed list of high-level changes made since v0.7.2.
InternalPortfolioPilot and initial ResolveRequest wiring by @ffranr in https://github.com/lightninglabs/taproot-assets/pull/1912MintingBatch.Copy tests with seedlings coverage by @ffranr in https://github.com/lightninglabs/taproot-assets/pull/1918BakeMacaroon RPC and tapcli support by @ffranr in https://github.com/lightninglabs/taproot-assets/pull/1960PortfolioPilot by @ffranr in https://github.com/lightninglabs/taproot-assets/pull/1954unit CI with optional verbosity and package parallelism by @ffranr in https://github.com/lightninglabs/taproot-assets/pull/1970isAssetInvoice check by @GeorgeTsagk in https://github.com/lightninglabs/taproot-assets/pull/2009ComputeView by @GeorgeTsagk in https://github.com/lightninglabs/taproot-assets/pull/1919Full Changelog: https://github.com/lightninglabs/taproot-assets/compare/v0.7.2...v0.8.0-rc1
Note that downgrading from v0.7.2 to previous tapd versions is not presently supported. You should create backups of tapd database state before upgrad
Note that downgrading from v0.7.2 to previous tapd versions is not presently supported. You should create backups of tapd database state before upgrading to tapd v0.7.2.
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.2.sig and manifest-v0.7.2.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.7.2.sig manifest-v0.7.2.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.
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.2.sig.ots and manifest-v0.7.2.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.2.sig.ots -f manifest-roasbeef-v0.7.2.sig
ots verify manifest-v0.7.2.txt.ots -f manifest-v0.7.2.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.
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.2
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]
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.2 /verify-install.sh v0.7.2
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/taproot-assets [command-line options]
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.2.tar.gz are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf tapd-source-v0.7.2.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.7.2" ./cmd/tapd
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.7.2" ./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! ⚡️⚡️⚡️
See the in-repo release notes for a detailed list of high-level changes made since v0.7.1.
key.GetOp() instead of key.GetOutpoint() by @ffranr in #1981Note that downgrading from v0.7.2-rc1 to previous tapd versions is not presently supported. You should create backups of tapd database state before up
Note that downgrading from v0.7.2-rc1 to previous tapd versions is not presently supported. You should create backups of tapd database state before upgrading to tapd v0.7.2-rc1.
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.2-rc1.sig and manifest-v0.7.2-rc1.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.7.2-rc1.sig manifest-v0.7.2-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.
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.2-rc1.sig.ots and manifest-v0.7.2-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.2-rc1.sig.ots -f manifest-roasbeef-v0.7.2-rc1.sig
ots verify manifest-v0.7.2-rc1.txt.ots -f manifest-v0.7.2-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.
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.2-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]
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.2-rc1 /verify-install.sh v0.7.2-rc1
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/taproot-assets [command-line options]
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.2-rc1.tar.gz are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf tapd-source-v0.7.2-rc1.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.7.2-rc1" ./cmd/tapd
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.7.2-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! ⚡️⚡️⚡️
See the in-repo release notes for a detailed list of high-level changes made since v0.7.1.
key.GetOp() instead of key.GetOutpoint() by @ffranr in #1981Note that downgrading from v0.7.1 to previous tapd versions is not presently supported. You should create backups of tapd database state before upgrad
Note that downgrading from v0.7.1 to previous tapd versions is not presently supported. You should create backups of tapd database state before upgrading to tapd v0.7.1.
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.sig and manifest-v0.7.1.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.7.1.sig manifest-v0.7.1.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.
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.sig.ots and manifest-v0.7.1.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.sig.ots -f manifest-roasbeef-v0.7.1.sig
ots verify manifest-v0.7.1.txt.ots -f manifest-v0.7.1.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.
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
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]
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 /verify-install.sh v0.7.1
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/taproot-assets [command-line options]
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.tar.gz are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf tapd-source-v0.7.1.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.7.1" ./cmd/tapd
go install -v -mod=vendor -ldflags "-X github.com/lightninglabs/taproot-assets/build.Commit=v0.7.1" ./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! ⚡️⚡️⚡️
See the in-repo release notes for a detailed list of high-level changes made since v0.7.0.
migrate dependency by @ViktorT-11 in #1914SendStateVerifyPreBroadcast and supporting proof reanchor helpers by @ffranr in #1884Note 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 u
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.
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.
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.
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]
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]
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! ⚡️⚡️⚡️
See the in-repo release notes for a detailed list of high-level changes made since v0.7.0.
migrate dependency by @ViktorT-11 in #1914SendStateVerifyPreBroadcast and supporting proof reanchor helpers by @ffranr in #1884Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.