The Taproot deployment is buried insofar as consensus now not checks its standing to find out whether or not to implement the Taproot guidelines. The Taproot guidelines are enforced from genesis now, with the (hardcoded) exception of a single block.

Burying is usually for a efficiency enchancment ensuing from not needing to continually verify the deployment standing. Since Taproot guidelines are at all times used, there isn’t any have to specify a buried deployment peak nor to take away the deployment parameters, and so the deployment parameters stay. The deployment code is simply referred to as when customers use getdeploymentinfo, and in that case, it might be helpful to have the historic deployment data somewhat than stating that it’s buried.