Trusted keys cleanup phase 1: Update the trusted git root.
This is done in two parts to prevent the automatic update on the site from being broken.
This is step one in removing the following inactive keys:
32EE5C4C3FA15CCADB46ABE529D4BCB6416F53EC jonasschnelli (last use: f324ce32f53e7b0b149f9e7e83874ac4ff5fb92f in 2018)
1E7DD3547F244C757223FAC8FC6434FC3A31E956 btcdrak (never used?)
912FD3228387123DC97E0E57D5566241A0295FA9 btcdrak (last use: 32b7869956e3a70025e32b69bab11fc262ef84d8 in 2017)
The most recent of these commits is f324ce32f53e7b0b149f9e7e83874ac4ff5fb92f, so update the merge base to that.
In the next phase I will actually remove these keys, leaving the following keys (I have tested this trusted root by replacing the contents of contrib/verify-commits/trusted-keys and running the verify-commits script):
Trusted keys cleanup phase 1: Update the trusted git root.
This is done in two parts to prevent the automatic update on the site from being broken.
This is step one in removing the following inactive keys:
The most recent of these commits is f324ce32f53e7b0b149f9e7e83874ac4ff5fb92f, so update the merge base to that.
In the next phase I will actually remove these keys, leaving the following keys (I have tested this trusted root by replacing the contents of
contrib/verify-commits/trusted-keys
and running the verify-commits script):