v0.5.0-alpha #1265
guggero
announced in
Announcements
v0.5.0-alpha
#1265
Replies: 1 comment
-
congrats to you all,so great |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Database Migrations
tapd
v0.5.0
contains non-revertible database migrations. After runningtapd
v0.5.0
, these database migrations prevent downgradingtapd
to a previous release. Create backups oftapd
database state, before upgrading totapd
v0.5.0
. Please report any database migration issues.Breaking changes
Downstream Projects -
litd
litd
v0.14.0-alpha
enhancements require both channel peers to upgrade to alitd
version>= v0.14.0-alpha
to continue Lightning Channel functionality. See upgrade instructions below if you opened Asset channels with such an experimental version.tapd
v0.5.0
changesOracle RPC:
The RPC protobuf definitions for the Price Oracle have changed. Asset exchange rates are now expressed as
FixedPoint
to achieve better precision.The rationale for the change and the new math behind it are described in the new RFQ document.
Code examples for a Price Oracle server are available here.
Configuration changes:
The configuration value (
universe.public-access
) and command line flag (--universe.public-access
) now needs a value and is no longer a boolean. The value now controls whether the node's universe database can be accessed over RPC and either read (valuer
) or written to (valuew
) or both (valuerw
).So existing nodes with the configuration file value
universe.public-access=true
need to change the value touniverse.public-access=rw
. Users specifying the command line flag--universe.public-access
just need to append a value, for example--universe.public-access=rw
.Required-upgrade path for existing
litd
installations:To avoid loss of channel funds: Any
litd
node which ran Taproot Asset channels using anylitd
v0.13.9xx-experimental
versions MUST FOLLOW all of the following procedures:litd
v0.14.0-alpha
enhancements require both channel peers to upgrade to alitd
version>= v0.14.0-alpha
to continue Lightning Channel functionality.If one channel peer is running
litd
version<= v0.13.9xx-experimental
channel operations are are NOT forwards compatible with litdv0.14.0-alpha
versions.litd
version <=,v0.13.9xx-experimental
must be cooperatively closed before upgrading tov0.14.0-alpha
.lncli pendingchannels
: Ensure pending_htlcs response is empty before progressingExample:
lncli listchannels | jq '.channels[] | select(.pending_htlcs != [])'
lncli pendingchannels
is empty), both nodes must be upgraded to the newv0.14.0-alpha
version before new channels can be opened. Please coordinate the upgrade with your peer if you're not operating both nodes.Verifying the Release
In order to verify the release, you'll need to have
gpg
orgpg2
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:Once you have the required PGP keys, you can verify the release (assuming
manifest-roasbeef-v0.5.0.sig
andmanifest-v0.5.0.txt
are in the current directory) with:You should see the following if the verification was successful:
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 withshasum -a 256 <filename>
, compare it with the corresponding one in the manifest file, and ensure they match exactly.Verifying the Release Timestamp
In addition to time-stamping the git tag with OpenTimestamps, we also timestamp the manifest file along with its signature. Two files are included in our release artifacts:
manifest-roasbeef-v0.5.0.sig.ots
andmanifest-v0.5.0.txt.ots
.Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
Alternatively, the OpenTimestamps website can be used to verify these timestamps if one doesn't have a
bitcoind
instance accessible locally.Assuming you are using the OpenTimestamps
ots-git-gpg-wrapper
you can verify the timestamp of the git tag by verifying the tag as explained in Verifying the Release Binaries.These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.
Verifying the Release Binaries
Our release binaries are fully reproducible. Third parties are able to verify that the release binaries were produced properly without having to trust the release manager(s). See our reproducible builds guide for how this can be achieved.
The release binaries are compiled with
go1.22.6
, which is required by verifiers to arrive at the same ones.The
make release
command can be used to ensure one rebuilds with all the same flags used for the release. If one wishes to build for only a single platform, thenmake release sys=<OS-ARCH> tag=<tag>
can be used.Finally, you can also verify the tag itself with the following command:
Verifying the Docker Images
To verify the
tapd
andtapcli
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):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
andtapd-source-v0.5.0.tar.gz
are in the current directory, follow these steps:The
-mod=vendor
flag tells thego 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:⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️
Release Notes (auto generated)
What's Changed
flake-unit-race
Makefile target by @gijswijs in Pass 'pkg' argument toflake-unit-race
Makefile target #1044WithinTolerance
method and greater-than operators by @ffranr in Add fixed-pointWithinTolerance
method and greater-than operators #1135trap
to make sure old files always restored by @Roasbeef in scripts: usetrap
to make sure old files always restored #1187AddAssetBuyOrder
andAddAssetSellOrder
RPCs by @guggero in [rfq]: add validation toAddAssetBuyOrder
andAddAssetSellOrder
RPCs #1192RWMutex
for cache by @jbrill in tapdb: Add Universe indices, optimize SQL queries,RWMutex
for cache #1174ListBurns
RPC by @GeorgeTsagk in AddListBurns
RPC #1178tchrpc.SendPayment
by @GeorgeTsagk in Support user-generated RFQ ontchrpc.SendPayment
#1224GroupKeyReveal
V1 by @ffranr in AddGroupKeyReveal
V1 #1246New Contributors
RWMutex
for cache #1174Full Changelog: v0.4.1...v0.5.0
This discussion was created from the release v0.5.0-alpha.
Beta Was this translation helpful? Give feedback.
All reactions