# Bitcoin Inquisition 25.2

**URL:** <https://delvingbitcoin.org/t/bitcoin-inquisition-25-2/838>\
**Category:** Implementation\
**Tags:** announcement, inquisition\
**Created:** [April 27, 2024, 2:46am UTC](https://delvingbitcoin.org/t/bitcoin-inquisition-25-2/838 "2024-04-27T02:46:36Z")\
**Posts on this page:** 1\
**Page:** 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:** [April 27, 2024, 2:46am UTC](https://delvingbitcoin.org/t/bitcoin-inquisition-25-2/838/1 "2024-04-27T02:46:36Z")

</div>

Bitcoin Inquisition 25.2 is now available from:

> **[Release Bitcoin Inquisition 25.2 · bitcoin-inquisition/bitcoin](https://github.com/bitcoin-inquisition/bitcoin/releases/tag/v25.2-inq)**
>
> What's Changed
> 
> chainparams: Use BINANA numbers rather than BIP numbers by @ajtowns in #46
> getdeploymentinfo: Report BINANA ids by @ajtowns in #47
> Re enable OP\_CAT by @0xBEEFCAF3 in #39
> Include pat...

This includes support for the following proposed consensus changes:

- [BIP 119](https://github.com/bitcoin/bips/blob/584f4a732ba94199fc097fbb9b4660db868dd712/bip-0119.mediawiki) OP\_CHECKTEMPLATEVERIFY ([PR#33](https://github.com/bitcoin-inquisition/bitcoin/pull/33))
- [BIP 118](https://github.com/bitcoin/bips/blob/584f4a732ba94199fc097fbb9b4660db868dd712/bip-0118.mediawiki) SIGHASH\_ANYPREVOUT ([PR#34](https://github.com/bitcoin-inquisition/bitcoin/pull/34))
- [BIN-2024-1](https://github.com/ajtowns/binana/blob/8264328e6c7fd9e9f30efb8273fb94700f001454/2024/BIN-2024-0001.md) aka [BIP 347](https://github.com/bitcoin/bips/pull/1525#issuecomment-2075518532) OP\_CAT ([PR#39](https://github.com/bitcoin-inquisition/bitcoin/pull/39))

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

The first two of these have been active on the default signet since block 106704 (2022-09-06), and the third should become active in a few days at block 193536.

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.