So as to add to Raghav’s reply above, Cobra lately posted this query on Twitter with a screenshot of what you see whenever you obtain Bitcoin Core on MacOS for the primary time.
He outlines what would should be accomplished for Bitcoin Core builders to deal with this:
The repair is trivial, simply signal the applying with an Apple developer account certificates, and notarize it, and it’ll run instantly for customers, with out exhibiting this warning.
However Andrew Chow defined on Twitter why Bitcoin Core builders haven’t accomplished this:
a notarized app will telephone residence to Apple’s servers to confirm that the notarization is legitimate. This privateness concern is what stopped the try and notarize Core, in any other case it might have been accomplished some time in the past. Many devs aren’t snug with that invasion of privateness.
Does a consumer trusting apple imply that they’re opting into apple being the ultimate arbiter of what they’ll run on their machine? As a result of AFAIU, that is what app notarization does. Apple can revoke notarizations thereby stopping an app from being put in.
Cobra argues that
Core makes requests to DNS seeds, which leaks the consumer’s privateness to random Core builders, however in some way, the consumer should not belief Apple, their very own OS supplier?
and
Apple’s walled backyard is a significant promoting level, many individuals like functions being vetted and pre-approved.
That summarizes the arguments for and in opposition to the Bitcoin Core builders addressing this consumer expertise drawback on MacOS. I might count on this to proceed to be a consumer expertise drawback for the foreseeable future.
