-
Notifications
You must be signed in to change notification settings - Fork 65
Fork Settings
Eric Voskuil edited this page Aug 12, 2017
·
13 revisions
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.
[fork]
# Allow minimum difficulty blocks, defaults to false (use true for testnet).
easy_blocks = false
# 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
See testnet differences.
See BIP16.
See BIP30.
See BIP34.
See BIP66.
See BIP65.
See BIP90.
See BIP68.
See BIP112.
See BIP113.
Users | Developers | License | Copyright © 2011-2024 libbitcoin developers
- Home
- Build Server
- Download Server
- Frequently Asked Questions
- General Information
- Client Server Interface
- Configuration Settings
- Tutorials