# Bitcoin Inquisition 29.1

**URL:** <https://delvingbitcoin.org/t/bitcoin-inquisition-29-1/2019>\
**Category:** Implementation\
**Tags:** announcement, inquisition\
**Created:** [September 30, 2025, 7:21am UTC](https://delvingbitcoin.org/t/bitcoin-inquisition-29-1/2019 "2025-09-30T07:21:59Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![ajtowns](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/ajtowns/32/417_2.png) [@ajtowns](https://delvingbitcoin.org/u/ajtowns)\
**Post date:** [September 30, 2025, 7:21am UTC](https://delvingbitcoin.org/t/bitcoin-inquisition-29-1/2019/1 "2025-09-30T07:21:59Z")

</div>

Bitcoin Inquisition 29.1 is now available from

> **[Release Bitcoin Inquisition 29.1 · bitcoin-inquisition/bitcoin](https://github.com/bitcoin-inquisition/bitcoin/releases/tag/v29.1-inq)**
>
> Bitcoin Inquisition 29.1 is now available.
> It is based on Bitcoin Core 29.1 and includes heretical activation of BIP 118 (ANYPREVOUT), BIP 119 (CHECKTEMPLATEVERIFY), BIN-24-1 (BIP 347, OP\_CAT), BIN...

This is based on [Bitcoin Core 29.1](https://bitcoincore.org/en/releases/29.1/).

This includes support for the following proposed consensus changes:

- [BIP 118](https://github.com/bitcoin/bips/blob/584f4a732ba94199fc097fbb9b4660db868dd712/bip-0118.mediawiki) SIGHASH\_ANYPREVOUT ([PR#84](https://github.com/bitcoin-inquisition/bitcoin/pull/84))
- [BIP 119](https://github.com/bitcoin/bips/blob/584f4a732ba94199fc097fbb9b4660db868dd712/bip-0119.mediawiki) OP\_CHECKTEMPLATEVERIFY ([PR#85](https://github.com/bitcoin-inquisition/bitcoin/pull/85))
- [BIN-24-1](https://github.com/ajtowns/binana/blob/8264328e6c7fd9e9f30efb8273fb94700f001454/2024/BIN-2024-0001.md) aka [BIP 347](https://github.com/bitcoin/bips/blob/740e826c19391a7a290933f514c15518e00780f0/bip-0347.mediawiki) OP\_CAT ([PR#83](https://github.com/bitcoin-inquisition/bitcoin/pull/83))
- [BIN-24-3](https://github.com/bitcoin-inquisition/binana/blob/3477736b354a8523615695971c6250cc4f98d452/2024/BIN-2024-0003.md) aka BIP 348 OP\_CHECKSIGFROMSTACK ([PR#87](https://github.com/bitcoin-inquisition/bitcoin/pull/87))
- [BIN-24-4](https://github.com/bitcoin-inquisition/binana/blob/3477736b354a8523615695971c6250cc4f98d452/2024/BIN-2024-0004.md) aka BIP 349 OP\_INTERNALKEY ([PR#86](https://github.com/bitcoin-inquisition/bitcoin/pull/86))

The first two of these have been active on the default signet since block 106704 (2022-09-06), the third since block 193536 (2024-04-30), and the fourth and fifth have been triggered for activation so should be active at block 272592, due in a bit under a week.

Note that transactions making use of any of these new features will not be relayed by nodes that don’t support these features, so if you’d like your transaction to get to a miner, you’ll need to peer with other inquisition nodes. An easy way to do this is to specify `addnode=inquisition.bitcoin-signet.net`. By default, Bitcoin Inquisition nodes will advertise themselves via the subversion string, which can be viewed with `bitcoin-cli -netinfo 3`. See the [23.0 announcement](https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-December/021275.html) for more details.

This release includes support for the send side of [BIP 153](https://github.com/bitcoin/bips/pull/1937) template sharing ([PR#96](https://github.com/bitcoin-inquisition/bitcoin/pull/96)), so nodes that support receiving templates but do not support the inquisition consensus changes can still achieve compact block reconstruction without requiring a round trip, if they peer with an inquisition node.

---

_[View the full topic](https://delvingbitcoin.org/t/bitcoin-inquisition-29-1/2019)._
