Post ABchmXkx2hjpChtmdM by pox@bitcoinhackers.org
 (DIR) More posts by pox@bitcoinhackers.org
 (DIR) Post #ABchmXkx2hjpChtmdM by pox@bitcoinhackers.org
       2021-09-21T13:18:13Z
       
       0 likes, 0 repeats
       
       @orionwl I'm trying to verify 22.0 and the key with which you seemed to have signed it is 9DEAE0DC7063249FB05474681E4AED62986CD25DThe one I've been using so far is 90C8 019E 36C2 E964Has it changed?
       
 (DIR) Post #ABchmYF5EfqCi9zqbI by orionwl@x0f.org
       2021-09-22T15:05:21Z
       
       0 likes, 0 repeats
       
       @pox yes, things have changed with 22.xthe 'release key' is no longer in use, attestations to the binaries are signed by everyone that does a reproducible (guix) buildsee https://github.com/bitcoin-core/bitcoincore.org/issues/793
       
 (DIR) Post #ABgh8g8mohVwDZqixM by pox@bitcoinhackers.org
       2021-09-24T13:17:00Z
       
       0 likes, 0 repeats
       
       @orionwl got it. How can I see which of the signing keys are trusted by people I already trust? Not sure how to verify the keys I see on github otherwise.