Mutinynet v29.0

Switches to use Bitcoin Inquisition instead of my old fork of Bitcoin Core. This will make it much easier to maintain and easily get updates for future versions. This was much needed so we can have things like TRUC, ephemeral anchors/dust, and other future improvements coming to Bitcoin Core on Mutinynet.

This will have an effect if you were using this implementation on mainnet (not recommended), Inquisition enforces that you can only run on signet or regtest. If you want an implementation that is compatible with both bitcoin mainnet and Mutinynet, Bitcoin Knots supports the signetblocktime config.

This will also have an effect on the soft forks activated on Mutinynet. With this, this will remove OP_VAULT and OP_PAIRCOMMIT. This is technically a hard fork, but Mutinynet is a dictatorship.

The soft forks now activated on Mutinynet are:

• Anyprevout
• CTV
• OP_CAT
• CSFS
• OP_INTERNALKEY

Pair Commit

Adds new OP_PAIRCOMMIT

Mutinynet CAT + LNHANCE

Mutinynet how has Covtools, CAT, and LNHANCE

Mutinynet Covtools

Mutinynet with the Covtools softfork activated!

Custom Signet blocktime

Binaries I compiled for a my custom signet blocktime PR