From d5b88dde721faa6173f00ded2b27252c8294e235 Mon Sep 17 00:00:00 2001 From: Peter Todd Date: Thu, 21 Sep 2023 02:10:14 -0400 Subject: [PATCH] Fix capitalization of OpenTimestamps in release notes --- .github/workflows/release.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/release.yaml b/.github/workflows/release.yaml index 6a02cad7b..7389def06 100644 --- a/.github/workflows/release.yaml +++ b/.github/workflows/release.yaml @@ -79,14 +79,14 @@ jobs: ## Verifying the Release Timestamp - From this new version onwards, in addition time-stamping the _git tag_ with [OpenTimeStamps](https://opentimestamps.org/), 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-${{ env.RELEASE_VERSION }}.txt.asc.ots`. + From this new version onwards, in addition time-stamping the _git tag_ with [OpenTimestamps](https://opentimestamps.org/), 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-${{ env.RELEASE_VERSION }}.txt.asc.ots`. Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands: ``` ots verify manifest-roasbeef-${{ env.RELEASE_VERSION }}.sig.ots -f manifest-roasbeef-${{ env.RELEASE_VERSION }}.sig ``` - Alternatively, [the open timestamps website](https://opentimestamps.org/) can be used to verify timestamps if one doesn't have a `bitcoind` instance accessible locally. + Alternatively, [the OpenTimestamps website](https://opentimestamps.org/) can be used to verify timestamps if one doesn't have a `bitcoind` instance accessible locally. These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.