From: Kate Salazar <mercedes.catherine.salazar@gmail•com>
To: Owen Gunden <ogunden@phauna•org>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Cc: Prayank <prayank@tutanota•de>
Subject: Re: [bitcoin-dev] bitcoin.org missing bitcoin core version 22.0
Date: Wed, 20 Oct 2021 22:18:03 +0200 [thread overview]
Message-ID: <CAHiDt8A30DZtvsPnDDdtyVpho-NKKQhbP_4g8d0MGATawWvg_w@mail.gmail.com> (raw)
In-Reply-To: <20211020192054.GA117785@jauntyelephant.191.37.198.vultr.com>
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
Hi Owen,
On Wed, Oct 20, 2021 at 9:25 PM Owen Gunden via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> On Wed, Oct 20, 2021 at 04:47:17PM +0200, Prayank wrote:
> > > It seems confusing to have two sites that seemingly both represent
> > > bitcoin core.
> >
> > There is only one website which represents Bitcoin Core full node
> > implementation. You can download Bitcoin Core from
> > https://bitcoincore.org
>
> 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.
>
He is taking the most sensible way forward, decreasing bus factor.
Read: https://laanwj.github.io/2021/01/21/decentralize.html
>
> Given the level of security at stake here, my eyebrows are raised at
> this combination of items changing (new website + new gpg signers at the
> same time).
>
Don't worry and build your own release;
but if you do, always verify the tree hash.
Trust signed annotated tags.
Cheers!
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 2321 bytes --]
next prev parent reply other threads:[~2021-10-20 20:18 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
2021-10-20 19:43 ` Charles Hill
2021-10-20 20:18 ` Kate Salazar [this message]
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=CAHiDt8A30DZtvsPnDDdtyVpho-NKKQhbP_4g8d0MGATawWvg_w@mail.gmail.com \
--to=mercedes.catherine.salazar@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=ogunden@phauna$(echo .)org \
--cc=prayank@tutanota$(echo .)de \
/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