# Non-disclosure of a consensus bug in btcd

**URL:** <https://delvingbitcoin.org/t/non-disclosure-of-a-consensus-bug-in-btcd/1177>\
**Category:** Implementation\
**Tags:** announcement\
**Created:** [October 3, 2024, 2:19pm UTC](https://delvingbitcoin.org/t/non-disclosure-of-a-consensus-bug-in-btcd/1177 "2024-10-03T14:19:37Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![roasbeef](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/roasbeef/32/160_2.png) [@roasbeef](https://delvingbitcoin.org/u/roasbeef)\
**Post date:** [October 3, 2024, 8:00pm UTC](https://delvingbitcoin.org/t/non-disclosure-of-a-consensus-bug-in-btcd/1177/3 "2024-10-03T20:00:20Z")

</div>

I thought it would be useful to add some additional context here. It is the case that we wanted to further delay the disclosure, as we felt that disclosing just 3 months after a patch landed was too soon. Particularly given existing precedence set by other full node implementations to delay disclosure of sufficiently critical issues well beyond the 6 months we requested between patch and disclosure (observe some of the timelines carried out for the recent set of [bitcoind security disclosures here](https://bitcoincore.org/en/security-advisories/)).

Ultimately, Niklas and AntoineP _refused_ to delay an extra 3 months (to bring the total age of the release to 6 months), instead deciding to prematurely disclose themselves against the wishes of the `btcd` maintainers.

---

_[View the full topic](https://delvingbitcoin.org/t/non-disclosure-of-a-consensus-bug-in-btcd/1177)._