Fork Settings

The following consensus fork settings are implemented in the libbitcoin-blockchain and exposed in both Bitcoin Node (BN) and Bitcoin Server (BS). Enabling a fork causes the node to validate blocks and transactions using the associated rule change once the fork has activated. BIP68, BIP112 and BIP113 support added in version 3.3. Retarget (regtest), BIP141, BIP143 and BIP147 support added in version 3.4.

[fork]
# Allow minimum difficulty blocks, defaults to false (use true for testnet).
easy_blocks = false
# Retarget difficulty, defaults to true (use false for regtest).
retarget = true
# Add pay-to-script-hash processing, defaults to true (soft fork).
bip16 = true
# Disallow collision of unspent transaction hashes, defaults to true (soft fork).
bip30 = true
# Require coinbase input includes block height, defaults to true (soft fork).
bip34 = true
# Require strict signature encoding, defaults to true (soft fork).
bip66 = true
# Add check locktime verify op code, defaults to true (soft fork).
bip65 = true
# Assume bip34, bip65, and bip66 activation if enabled, defaults to true (hard fork).
bip90 = true
# Add relative locktime enforcement, defaults to true (soft fork).
bip68 = true
# Add check-sequence-verify op code, defaults to true (soft fork).
bip112 = true
# Use median time past for locktime, defaults to true (soft fork).
bip113 = true
# Segregated witness consensus layer, defaults to true (soft fork).
bip141 = true
# Version 0 transaction digest, defaults to true (soft fork).
bip143 = true
# Prevent dummy value malleability, defaults to true (soft fork).
bip147 = true

easy_blocks

See testnet differences.

bip16

See BIP16.

bip30

See BIP30.

bip34

See BIP34.

bip66

See BIP66.

bip65

See BIP65.

bip90

See BIP90.

bip68

See BIP68.

bip112

See BIP112.

bip113

See BIP113.