I have explored the github, and per intuition, I switched from master branch to the branch called "24.x", that I suppose it refers to the bitcoin core version. Bitcoin core 24.0.1 is the software I installed. In this branch I found the txt file of builder keys --mentioned in the signature verification instructions on the bitcoincore.org download page for MacOS--;

This is the file, in branch 24.x:

bitcoin/contrib/builder-keys/keys.txt

As mentioned in bitcoin/contrib/builder-keys/README.md : The file keys.txt contains fingerprints of the public keys of builders and active developers.



Can anyone confirm this is the right list to use for the verification of Bitcoin Core 24.0.1?

I'm trying to verify my bitcoin core 24.0.1, but the verification instructed by bitcoincore.org for MacOS implies to search for GPG Keys in a github bitcoin repository that no longer exist. I'm a novice with this type of things, so I am not really able to search into the bitcoin github for myself. Can anyone help me find GPG Keys to verify?


ADDITIONAL:

I've asked ChatGPT for some help in the process, and it mentioned me of a way to verify the bitcoin core software, which I have performed, and resulted in a supposedly non-official bitcoin core, altough I downloaded it from https://bitcoincore.org.

Here is the process mentioned to me by the AI:

In the Bitcoin project on GitHub, the developer keys are not stored in a specific folder. Instead, they are included in the code commits and signed with the developers' GPG keys.

To verify the authenticity of your Bitcoin Core download, you can follow the instructions on the Bitcoin.org website:

    Download the source code from the Bitcoin GitHub repository: https://github.com/bitcoin/bitcoin

    Check the code out from the repository:

git clone https://github.com/bitcoin/bitcoin.git

    Navigate to the Bitcoin source code directory:

cd bitcoin

    Check the Git tags to see which version of the software you have downloaded:

git tag

    Check the signature of the tag:

git tag -v [tagname]

    The output of the command should indicate whether the signature is valid and made by one of the project's trusted developers.

__


The first tag after the "git tag" command resulted in "noversion". ChatGPT suggests to type the command "git describe", of which output resulted in "v21.99-guixtest1-7105-g39363a4b9". ChatGPT suggests the downloaded software is not an official release. It then suggests to try checking the hashes, which I suppose is the standard verification, instructed by bitcoincore.org.

Does this have any relevance?

Thank you!

Thanks. Is there a way to join the bitcoin network or become a full node without having to pass from an owned source that makes the/a software available? Because, I suppose, to become a full node is necessary to have a specific software, right?

Thanks for the note;

Since bitcoin comes with a software, I suppose there has to be a source/website where to find the original software; Isn't it so that there must be an official source, whence the original software is firstly available? It seems that the necessity to have a singular origin, which makes "centralized" at least the availability of the bitcoin software, is unavoidable. Or am I missing something?

Hi,

I wanted to join the network and contribute to it, so I downloaded Bitcoin Core from the bitcoin.org page. Little did I know, in the process of trying to verify the download (I am a novice in that, just following the steps in bitzuma's tutorial) I understood the latest Bitcoin Core software version was on another website, which is referred to as the official one.

I started syncing with the network straight away as I downloaded the software in the first place, and now is at 77% of progress.

Do I have to stop and download the latest release?
What issues may I incur if I continue using the 22.0?
Why does bitcoin.org, which is supposed to be the official bitcoin site, redirect to a version of the Bitcoin Core software that is old and implicitly non-official?