Quote from: gmaxwell on Today at 08:20:27 AM

Not in a meaningful sense.

When new consensus changes are added to bitcoin they are added in advance, completely deactivated and inert. Later a version will be produced that doesn't change anything except arming the activation.

This avoids the risk that activation will be interrupted by unrelated issues in a new version. It also gives more time for developers to test the fully integrated version and reduced risk that issues introduced by merging will go undetected.

So 0.21.0 doesn't have taproot support and will continue to not have any taproot support even after taproot activates.

Thanks! Does activation just mean a node is running 0.21.1 or do they have to take extra steps after the the upgrade to 0.21.1?