bitcoin/contrib/builder-keys
fanquake 11c7d001a9
Merge bitcoin/bitcoin#22700: builder-keys: Add dongcarl
7d95777417 builder-keys: Add dongcarl (Carl Dong)

Pull request description:

  https://keys.openpgp.org/search?q=04017A2A6D9A0CCDC81D8EC296AB007F1A7ED999

  This is my master key, will be bumping the expiration of subkeys or rotating when necessary.

ACKs for top commit:
  fanquake:
    ACK 7d95777417 - matches what I've got.

Tree-SHA512: 3a76b8eda81821b3221402501cf8191bce73118624b932aa80a7fc1a32a91e3825aeb2b03ed261bbf284b088e927c384f92e08eadddf7f94ed4de579d9f6d2b7
2021-08-16 10:58:55 +08:00
..
keys.txt Merge bitcoin/bitcoin#22700: builder-keys: Add dongcarl 2021-08-16 10:58:55 +08:00
README.md tree-wide: Rename gitian-keys to builder-keys 2021-07-08 11:29:54 -04:00

PGP keys of builders and Developers

The file keys.txt contains fingerprints of the public keys of builders and active developers.

The associated keys are mainly used to sign git commits or the build results of Guix builds.

The most recent version of each pgp key can be found on most pgp key servers.

Fetch the latest version from the key server to see if any key was revoked in the meantime. To fetch the latest version of all pgp keys in your gpg homedir,

gpg --refresh-keys

To fetch keys of builders and active developers, feed the list of fingerprints of the primary keys into gpg:

while read fingerprint keyholder_name; do gpg --keyserver hkp://subset.pool.sks-keyservers.net --recv-keys ${fingerprint}; done < ./keys.txt

Add your key to the list if you provided Guix attestations for two major or minor releases of Bitcoin Core.