v0.5.0-alpha RC1 #1222
guggero
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Database Migrations
tapdv0.5.0contains non-revertible database migrations. After runningtapdv0.5.0, these database migrations prevent downgradingtapdto a previous release. Create backups oftapddatabase state, before upgrading totapdv0.5.0. Please report any database migration issues.Breaking changes
Downstream Projects -
litdlitdv0.14.0-alphaenhancements require both channel peers to upgrade to alitdversion>= v0.14.0-alphato continue Lightning Channel functionality. See upgrade instructions below if you opened Asset channels with such an experimental version.tapdv0.5.0changesThe 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=trueneed to change the value touniverse.public-access=rw. Users specifying the command line flag--universe.public-accessjust need to append a value, for example--universe.public-access=rw.litdinstallations:To avoid loss of channel funds: Any
litdnode which ran Taproot Asset channels using anylitdv0.13.9xx-experimentalversions MUST FOLLOW all of the following procedures:litdv0.14.0-alphaenhancements require both channel peers to upgrade to alitdversion>= v0.14.0-alphato continue Lightning Channel functionality.If one channel peer is running
litdversion<= v0.13.9xx-experimentalchannel operations are are NOT forwards compatible with litdv0.14.0-alphaversions.litdversion <=,v0.13.9xx-experimentalmust 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 pendingchannelsis empty), both nodes must be upgraded to the newv0.14.0-alphaversion 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, first, verify and install
gpgorgpg2. If your gpg keychain hasn’t previously imported the public keys for release signers, import these public keys:Once you have the required PGP keys, you can verify the release (assuming
manifest-roasbeef-v0.5.0-rc1.sigandmanifest-v0.5.0-rc1.txtare 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
sha256hash 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
From this new version onwards, in addition time-stamping the git tag with OpenTimestamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts:
manifest-roasbeef-v0.5.0-rc1.txt.asc.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 timestamps if one doesn't have a
bitcoindinstance accessible locally.These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.
Verifying the Release Binaries
Our release binaries are fully reproducible. Third parties are able to verify that the release binaries were produced properly without having to trust the release manager(s). See our reproducible builds guide for how this can be achieved.
The release binaries are compiled with
go1.22.6, which is required by verifiers to arrive at the same ones.The
make releasecommand 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
tapdandtapclibinaries 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.gzandtapd-source-v0.5.0-rc1.tar.gzare in the current directory, follow these steps:The
-mod=vendorflag tells thego buildcommand 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.shscript 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-raceMakefile target by @gijswijs in Pass 'pkg' argument toflake-unit-raceMakefile target #1044WithinTolerancemethod and greater-than operators by @ffranr in Add fixed-pointWithinTolerancemethod and greater-than operators #1135trapto make sure old files always restored by @Roasbeef in scripts: usetrapto make sure old files always restored #1187AddAssetBuyOrderandAddAssetSellOrderRPCs by @guggero in [rfq]: add validation toAddAssetBuyOrderandAddAssetSellOrderRPCs #1192RWMutexfor cache by @jbrill in tapdb: Add Universe indices, optimize SQL queries,RWMutexfor cache #1174ListBurnsRPC by @GeorgeTsagk in AddListBurnsRPC #1178New Contributors
RWMutexfor cache #1174Full Changelog: v0.4.1...v0.5.0-rc1
This discussion was created from the release v0.5.0-alpha RC1.
Beta Was this translation helpful? Give feedback.
All reactions