<p>The Taproot deployment is buried insofar as consensus no longer checks its status to determine whether to enforce the Taproot rules. The Taproot rules are enforced from genesis now, with the (hardcoded) exception of a single block.</p>
<p>Burying is generally for a performance improvement resulting from not needing to constantly check the deployment status. Since Taproot rules are always used, there's no need to specify a buried deployment height nor to remove the deployment parameters, and so the deployment parameters remain. The deployment code is only called when users use <code>getdeploymentinfo</code>, and in that case, it may be useful to have the historic deployment information rather than stating that it is buried.</p>

CC BY-SA 4.0
2023-03-14T15:20:43.973Z
Is that hardcoded exception a block that would violate Taproot rules?
Son Kaos999
CC BY-SA 4.0
2023-03-14T15:24:59.223Z
Yes. There is a single block mined prior to Taproot activation that violates the Taproot rules. All other blocks in the blockchain pass with the Taproot rules.
Ava Chow
CC BY-SA 4.0
2023-03-29T10:48:44.987Z
What block and what does it violate exactly? Thanks
Paul Otto
CC BY-SA 4.0
2023-08-30T19:19:15.523Z
@PaulOtto Block 692261 contains a taproot-invalid spend.
Pieter Wuille
CC BY-SA 4.0
2023-03-13T17:19:54.763Z
2023-03-13T17:19:54.763Z
Ava Chow
<p>Bitcoin Inquisition recently had a <a href="https://bitcoincore.reviews/bitcoin-inquisition-16" rel="nofollow noreferrer">PR about soft fork activation</a> and as part that PR, it buries taproot and references <a href="https://github.com/bitcoin/bitcoin/pull/23505" rel="nofollow noreferrer">a closed PR</a> to Bitcoin Core to bury taproot. Will the taproot deployment be buried in Bitcoin Core and if so, what needs to be in place to bury it?</p>

<bitcoin-core-development><taproot><soft-fork><activation><bip90-buried-deployments>
Why isn't the taproot deployment buried in Bitcoin Core?
Schmidty
# Why isn't the taproot deployment buried in Bitcoin Core?

(Asked by: username_0 on 2023-03-13)

Bitcoin Inquisition recently had a [PR about soft fork activation](https://bitcoincore.reviews/bitcoin-inquisition-16) and as part that PR, it buries taproot and references [a closed PR](https://github.com/bitcoin/bitcoin/pull/23505) to Bitcoin Core to bury taproot. Will the taproot deployment be buried in Bitcoin Core and if so, what needs to be in place to bury it?

**Tags:** bitcoin-core-development, taproot, soft-fork, activation, bip90-buried-deployments


---

## 1 answers

### Answer by username_1 on 2023-03-13. Score: 10 | Accepted answer

The Taproot deployment is buried insofar as consensus no longer checks its status to determine whether to enforce the Taproot rules. The Taproot rules are enforced from genesis now, with the (hardcoded) exception of a single block.

Burying is generally for a performance improvement resulting from not needing to constantly check the deployment status. Since Taproot rules are always used, there's no need to specify a buried deployment height nor to remove the deployment parameters, and so the deployment parameters remain. The deployment code is only called when users use `getdeploymentinfo`, and in that case, it may be useful to have the historic deployment information rather than stating that it is buried.

> **Comments:**
> **username_2**: Is that hardcoded exception a block that would violate Taproot rules?  
> **username_1**: Yes. There is a single block mined prior to Taproot activation that violates the Taproot rules. All other blocks in the blockchain pass with the Taproot rules.  
> **username_3**: What block and what does it violate exactly? Thanks  
> **username_4**: @PaulOtto Block 692261 contains a taproot-invalid spend.  

---

