i would just say "Bitcoin Core 0.21.0 includes an implementation of the proposed Taproot (BIP 341-342) consensus rules, without activation for mainnet. Experimenting with Taproot can be done on the new Signet network where it is already active. Activation parameters will likely be included in a future minor release, and the proposed rules will not be enforced without upgrading to it."
there is no forum of discussion for all bitcoin users
so companies decide Bitcoin protocol rules now?
you seem to want to use adoption of bitcoin core as telemetry (even if not through an explicit call-home)
jonatack: wrt https://github.com/bitcoin/bitcoin/pull/20849#issuecomment-754602325 -- I can reproduce the issue and was about to reply to your comment, but I wonder if that can be perceived as a step-by-step guide on how to create an evil node on the network that can circumvent the discouragement mechanism of anybody who connects to it...
As for rc4: i tried on macOS 11, verified the hash of bitcoin-0.21.0rc4-osx-unsigned.tar.gz (matched the others), verified the patched codesign_allocate, signed locally, verified the signed app (ok), gbuilt the signer with the created signature (failed)
the detached-sig-apply.sh takes the binary in bitcoin-0.21.0rc3-osx-unsigned.tar.gz, right?
^ the codesign_allocate is part of the bitcoin-0.21.0rc3-osx-unsigned.tar.gz? right?
[bitcoin] MarcoFalke opened pull request #20845: net: Log to net debug in MaybeDiscourageAndDisconnect except for noban and manual peers (master...2101-netLogDisconnect) https://github.com/bitcoin/bitcoin/pull/20845