Topic: Current Bitcoin Core? (Read 232 times)

Anything that asks you to spend money before you can withdraw is a red flag.
And it looks like they are trying to double-scam you with that so-called "encryption software".

BTW, it's better if you can post a new thread since it's off-topic to this thread.
Since it's not a "scam accusation" topic, you can try to post in Beginners and Help board or Service Discussion: go to your selected board then click "new topic" (right side) to create a new thread.

Well yeah, something I like about the Windows build process is that it doesn't require Visual Studio which is a gigantic package to download and install in the first place, not to mention the system requirements for running it and compiling stuff... good ol' MinGW ./configure && make && make install.

If you're more worried about signatures and hashes of the new binaries than about the actual content of the last updates / code changes, you could always compile yourself!
On GitHub, you can find the Windows Build Notes.

Every Bitcoin Core maintainer has a signing key. Generally, maintainers are highly better before they are given the maintainership responsibility, meaning you should be able to trust all of them (or at least most of them), so while you don't have to have all those keys imported into your PGP software, it's good to have multiple (arbitrary, if you want) keys imported just in case someone's Github account gets compromised for whatever reason.

Let me see.

I do confirm that bitcoin-23.0-win64-setup.exe does have an SHA256 equivalent of "4198eba8ac326d8746ab43364a44a5f20c157b6701f8c35b80d639a676df9011".
I do confirm that I've imported achow101's public key (0x152812300785C96444D3334D17565732E08E5E41) which is one of which you can't verify the signatures with.
I do confirm that SHA256SUMS is signed by achow101:

(I haven't imported any other public key, that's why it can't check the rest of the signatures)

Thanks.  While I did check the SHA256 hash of the Window's installer that I downloaded from here: https://bitcoincore.org/en/download/ and range a hash for the exe which turned back this digest:  4198eba8ac326d8746ab43364a44a5f20c157b6701f8c35b80d639a676df9011 that matched the SHASUMS file, I also note that someone else did the same as per this site and was having installation issues.  It's these kinds of issues that give me pause for upgrading.

Here's the issues that some operating in France experienced for reference: https://github.com/bitcoin/bitcoin/issues/25726

Lastly, with respect to verifying files, I don't know which keys that I should trust for importing the signatures for this version or how exactly I would be able to identify trustworthy signatures. 

Here's the list that my system didn't identify as unavailable signatures

0x152812300785C96444D3334D17565732E08E5E41
0x0AD83877C1F0CD1EE9BD660AD7CC770B81FD22A8
0x590B7292695AFFA5B672CBB2E13FC145CD3F4304
0x28F5900B1BB5D1A4B6B6D1A9ED357015286A333D
0x637DB1E23370F84AFF88CCE03152347D07DA627C
0xCFB16E21C950F67FA95E558F2EEB9F5CC09526C1
0xF4FC70F07310028424EFC20A8E4256593F177720
0xD1DBF2C4B96F2DEBF4C16654410108112E7EA81F
0x287AE4CA1187C68C08B49CB2D11BD4F33F1DB499
0xF9A8737BF4FF5C89C903DF31DD78544CF91B1514
0xC388F6961FB972A95678E327F62711DBDCA8AE56
0x9DEAE0DC7063249FB05474681E4AED62986CD25D
0xE463A93F5F3117EEDE6C7316BD02942421F4889F
0x9D3CC86A72F8494342EA5FD10A41BDC3F4FAFF1C
0x4DAF18FE948E7A965B30F9457E296D555E7F63A7
0x28E72909F1717FE9607754F8A7BEB2621678D37D
0x74E2DEF5D77260B98BC19438099BAD163C70FBFA

Thanks.

Just verify the file signature manually then you are good to go.

There is a tutorial on Windows regarding how to do it, see it at https://bitcoincore.org/en/download/ and there will be "Windows verification instructions".


You should use bitcoincore.org.

My apologies. The current version for bitcoin core on bitcoin dot or is v22 and v23 from bitcoin core dot org.  Thanks.

Hi everyone,  I wanted to try and vet some concerns I've had over the past few years regarding updating my Bitcoin core nodes.  It's my hope that the community here can help pet them to rest but if not I can always stick to my v.20x nodes. 

As you know there is no one single piece of software that makes bitcoin bitcoin, but if you look at it in terms of dominant influence over the ecosystem, you would have to say it would be the bitcoin core node.  That being said, here are two big flags I've seen recently that have me hesitant on upgrading from an older version of core:


- The first red flag issue I had when the download package the Windows signing key for one of their releases (sometime after v 20.1).

- The current issue is there is an obvious discrepancy between what bitcoin dot org and bitcoincore dot org list as the current version (the former states v 23 and the later v 24).

Obviously there have been tons and tons of changes since v. 20 and clearly the most powerful organizations on earth do not want bitcoin to eat their lunch (banks, governments etc).  That said I'm sure that these entities have been constantly trying to tweak bitcoin to their liking-whatever that may entail.  That said, if anyone has any feedback on the two noted concerns above I'd really appreciate it. 

TIA!