From: Owen Gunden <ogunden@phauna•org>
To: Pieter Wuille <bitcoin-dev@wuille•net>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] bitcoin.org missing bitcoin core version 22.0
Date: Wed, 20 Oct 2021 19:49:19 +0000 [thread overview]
Message-ID: <20211020194919.GA118497@jauntyelephant.191.37.198.vultr.com> (raw)
In-Reply-To: <mP71HoRgYl2eMSvdc0w6btXHIXGN6snpz5CYemWm507aSGhR5ewAx3NuZYtNSRBQr02D9Wm_UU2IFmtHqkqiinsgjQdwGerwOEak1_Fh3hc=@wuille.net>
On Wed, Oct 20, 2021 at 07:37:48PM +0000, Pieter Wuille wrote:
> On Wednesday, October 20th, 2021 at 3:20 PM, Owen Gunden via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> > I also notice that, as of 22.0, Wladimir is no longer signing the
> > releases, and I have no trust in my gpg network of the people who seem
> > to have replaced him.
>
> This is not correct. Here are Wladimir's attestations on the 22.0
> release:
> https://github.com/bitcoin-core/guix.sigs/tree/main/22.0/laanwj
>
> There is no separate special release key anymore though. Instead, the
> build attestations (by anyone) can be used as your trust basis.
Ah, that explains it, thanks Pieter. I was looking for a signature from
the release key 01EA 5486 DE18 A882 D4C2 6845 90C8 019E 36C2 E964,
which was still being supplied as recently as 0.21.1.
> There is no new website. The Bitcoin Core project website has been
> https://bitcoincore.org for years.
Some of us are very old :).
next prev parent reply other threads:[~2021-10-20 19:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 14:47 Prayank
2021-10-20 19:20 ` Owen Gunden
2021-10-20 19:37 ` Pieter Wuille
2021-10-20 19:49 ` Owen Gunden [this message]
2021-10-20 19:43 ` Charles Hill
2021-10-20 20:18 ` Kate Salazar
2021-11-05 8:17 ` Prayank
2021-11-05 10:52 ` damian
2021-11-05 14:45 ` yanmaani
2021-11-08 3:02 ` ZmnSCPxj
2021-11-09 12:49 ` Prayank
-- strict thread matches above, loose matches on Subject: below --
2021-10-20 21:50 Andrew Chow
2021-10-20 12:54 Owen Gunden
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211020194919.GA118497@jauntyelephant.191.37.198.vultr.com \
--to=ogunden@phauna$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=bitcoin-dev@wuille$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox