# Disclosure: Btcd consensus bugs due to usage of signed transaction version

**URL:** <https://delvingbitcoin.org/t/disclosure-btcd-consensus-bugs-due-to-usage-of-signed-transaction-version/455>\
**Category:** Implementation\
**Created:** [January 22, 2024, 2:51pm UTC](https://delvingbitcoin.org/t/disclosure-btcd-consensus-bugs-due-to-usage-of-signed-transaction-version/455 "2024-01-22T14:51:40Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![0xB10C](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/0xb10c/32/15_2.png) [@0xB10C](https://delvingbitcoin.org/u/0xB10C)\
**Post date:** [January 27, 2024, 12:12am UTC](https://delvingbitcoin.org/t/disclosure-btcd-consensus-bugs-due-to-usage-of-signed-transaction-version/455/5 "2024-01-27T00:12:32Z")

</div>

It seems like this was exploited on testnet (a day after being published here) in block 000000002f4830471b6b346578546615c031b99da5e7fabeac119b63f1843f82 with [5839f20446d7b9446e82c00117ee3699fa84154e970d57f09add60deef2eaa18](https://mempool.space/testnet/tx/5839f20446d7b9446e82c00117ee3699fa84154e970d57f09add60deef2eaa18). I tried to sync a btcd v0.23.4 node on testnet, which seems stuck on 2575398. A btcd v0.24.0 node is fine.

 ![image](https://delvingbitcoin.org/uploads/default/original/1X/4afb2c0d76d275440215ddd8825f2692f769252b.png)

According to [https://forkmonitor.info/nodes/btc](https://forkmonitor.info/nodes/btc), their mainnet btcd v0.23.3 node is still fine. I also haven’t seen a non-standard transaction exploiting this on mainnet in the past days.

---

_[View the full topic](https://delvingbitcoin.org/t/disclosure-btcd-consensus-bugs-due-to-usage-of-signed-transaction-version/455)._