Files
lnd/scripts/keys
Olaoluwa Osuntokun 81ff01c9cc scripts/keys: update roasbeef keys with new expiry
My key recently expired, in this commit, we update the keys to the new
refreshed version. These are the same keys, but with an expiry further
out.

Here's a clear sign of the latest Bitcoin block hash:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

000000000000000000013215ef7c32bc0427f388fc83623affe712f388
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQQpYhJoGq3wVlaize6QUl997uCthgUCaPi6xwAKCRCQUl997uCt
hpqNAQC5VnnbO6h/PjywGhU4LLRvH8SdgdDEMSc7xrtWd1vgPgD+IDrHqiAb+h38
ORBnUVJCVuZrPebtdnYXVQhII91eaw4=
=WRbl
-----END PGP SIGNATURE-----
2025-10-22 12:07:38 +01:00
..
2022-06-09 09:28:46 +02:00
2025-08-11 11:47:40 +02:00
2025-08-07 12:30:42 +02:00
2024-09-16 10:49:18 +02:00

Release verification keys

This directory contains all keys that are currently signing lnd releases.

The name of the file must match exactly the suffix that user is going to use when signing a release. For example, if the key is called eugene_.asc then that user must upload a signature file called manifest-eugene_-v0.xx.yy-beta.sig, otherwise the verification will fail. See the release documentation for details on how to create the signature.

In addition to adding the key file here as a .asc file the scripts/verify-install.sh file must also be updated with the key ID and the reference to the key file.