Bitcoin.org VS libbitcoin-system

Besides, the ARM version must have worked for me before because that's what I downloaded from the bitcoin.org download page when I installed 22.0

The level of security you employ should correlate with the amount of BTC you have. Would you leave your US dollars on Cashapp? If so you are probably fine leaving a little BTC on there. But long term your best option is cold storage, either buy a device (like Ledger NanoX) for $50-$100, or go to bitcoin.org and download the Bitcoin Core GUI, where you can create your own cold storage wallet. You can generate your own seed phrase with no third parties or extra costs.

Hello, I downloaded bitcoin core 25 from bitcoincore.org, but the only instructions I could find relating to the installation of the bitcoin daemon was on bitcoin.org (which seems to only offer up to bitcoin 22).

But if you check the link they posted, that's bitcoincore.org, not bitcoin.org That link is also the site that Bitcoin core on the releases page will link to as well.

What gives? What is offered at bitcoin.org is a download of Bitcoin Core 22.0...

https://bitcoin.org - No

Where is the best place to order. Is https://bitcoin.org/ the official site for this product?

Cryptocurrencies: Monero (XMR) and Bitcoin (BTC)

Here you can find a list of Bitcoin wallets listed on the bitcoin.org website, with various statistics to help you choose (Assuming you are on a windows desktop, but you could choose a mobile wallet if you preferred): https://bitcoin.org/en/choose-your-wallet?step=5&platform=windows

The recommended wallet on the website is Armory (https://www.bitcoinarmory.com/). I'm not sure if Electrum supports the minikey format so it may be best to stick to the advice of the author of the documentation. You can independently verify the existence of the Armory wallets listing on the bitcoin.org website too.

Is the code seeding by seconds since epoch, or nanoseconds since epoch truncated to 32 bits? Broken either way, just reading the code alongside cppreference.com it isn't obvious.

https://github.com/libbitcoin/libbitcoin-system/blob/a1b777f...

        const auto now = high_resolution_clock::now();

Last release 2019, master branch marked as non-functional. Doesn't seem to be very active. Their homepage https://libbitcoin.info/ looks polished, but no signs of recent life. This vulnerability seems unmentioned. Well, they claim it's not a vulnerability but a demo implementation that should not be used to store anything of value. But there is no prominent note about that and some users did exactly that.

Some extra relevant links:

https://github.com/libbitcoin/libbitcoin-system/pull/559

The pull request adding the vulnerability, the lack of review or collaboration is worth noticing. The prior code was already dubious in that AFAIK std::random_device library doesn't promise that the randomness is suitable for cryptography. I believe on common systems where this code was run the old code was not likely to be exploitable, but I wouldn't bet my money on it.

https://twitter.com/evoskuil/status/1688657656620167169

Developer commentary on this issue. I can't figure out what "long-documented intended usage" a seed command that mandates 128-bits of output but never has more than 32-bits of entropy would have.

https://archive.is/A7Jn6

The documentation the tweet references. I don't know how the 'Pseudorandom seeding' warning there would be distinguishable from warnings against CSPRNGs in favor of dice rolls or whatever. Nor can I figure out for whose convenience this function would serve except attackers.

  https://archive.is/HDe8h

https://github.com/libbitcoin/libbitcoin-system/wiki/Value-Proposition https://insights.bitcoinreserve.com/blog/bitcoin-has-no-intrinsic-value https://nakamotoinstitute.org/mempool/bitcoin-is-not-backed-by-nothing/