From: Anthony Towns <aj@erisian•com.au>
To: bitcoindev@googlegroups.com
Subject: [bitcoindev] Bitcoin Inquisition 25.2 released
Date: Sat, 27 Apr 2024 13:12:33 +1000 [thread overview]
Message-ID: <ZixtIfqYCYl7cR/F@erisian.com.au> (raw)
Hi all,
Bitcoin Inquisition 25.2 is now available from:
https://github.com/bitcoin-inquisition/bitcoin/releases/tag/v25.2-inq
This includes support for the following proposed consensus changes:
* [BIP 119] OP_CHECKTEMPLATEVERIFY ([PR#33])
* [BIP 118] SIGHASH_ANYPREVOUT ([PR#34])
* [BIN-2024-1] aka [BIP 347] OP_CAT ([PR#39])
This is based on [Bitcoin Core 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] for more details.
Cheers,
aj
[BIP 119]: https://github.com/bitcoin/bips/blob/584f4a732ba94199fc097fbb9b4660db868dd712/bip-0119.mediawiki
[PR#33]: https://github.com/bitcoin-inquisition/bitcoin/pull/33
[BIP 118]: https://github.com/bitcoin/bips/blob/584f4a732ba94199fc097fbb9b4660db868dd712/bip-0118.mediawiki
[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
[BIP 347]: https://github.com/bitcoin/bips/pull/1525#issuecomment-2075518532
[PR#39]: https://github.com/bitcoin-inquisition/bitcoin/pull/39
[Bitcoin Core 25.2]: https://bitcoincore.org/en/releases/25.2/
[23.0 announcement]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-December/021275.html
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/ZixtIfqYCYl7cR/F%40erisian.com.au.
reply other threads:[~2024-04-27 3:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZixtIfqYCYl7cR/F@erisian.com.au \
--to=aj@erisian$(echo .)com.au \
--cc=bitcoindev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox