- Bitcoin & Blockchain/
- P2P Network Overview/
- BCH Specification/
- Historical Upgrades
- May 2023 Upgrade
- Bigger Script Integers
- May 2022 Upgrade
- Native Introspection
- ReverseBytes
- May 2021 Upgrade
- Multiple OP_RETURNs
- Accept more tx in mempool
- ASERT DAA
- November 2020 Upgrade
- May 2020 Upgrade
- SigCheck protection
- November 2019 Upgrade
- MinimalData
- Schnorr multisig
- Segwit Recovery
- May 2019 Upgrade
- Schnorr
- November 2018 Upgrade
- op_checkdatasig
- Schnorr signatures
- May 2018 Upgrade
- Reenable Opcodes
- November 2017 Upgrade
- Bitcoin Cash
- Tx signing digest
- BIP-0157
- BIP-0158
- BIP-0159
- BIP 152
- BIP 133
- BIP 9
- BIP-0112
- BIP-0113
- BIP-0068
- BIP-0066
- BIP-0065
- BIP-0037
- Mempool message
- BIP-0034
- BIP-0016
- Block Versions
- Protocol Versions
- Transaction Versions
Bitcoin Cash Protocol Upgrades
Upgrade-20180515
layout: specification
title: May 2018 protocol ugrade Specification
category: spec
date: 2018-04-09
activation: 1526400000
Summary
When the median time past of the most recent 11 blocks (MTP-11) is greater than or equal to UNIX timestamp 1526400000 Bitcoin Cash will execute a protocol upgrade according to this specification. Starting from the next block these consensus rules changes will take effect:
- Blocksize increase to 32,000,000 bytes
- Re-enabling of several opcodes
The following are not consensus changes, but are recommended changes for Bitcoin Cash implementations:
- Automatic replay protection for future protocol upgrade
- Increase OP_RETURN relay size to 223 total bytes
Blocksize increase
The blocksize hard capacity limit will be increased to 32MB (32000000 bytes).
OpCodes
Several opcodes will be re-enabled per may-2018-reenabled-opcodes
Automatic Replay Protection
When the median time past of the most recent 11 blocks (MTP-11) is greater than or equal to UNIX timestamp 1542300000 (November 2018 protocol upgrade) Bitcoin Cash full nodes implementing the May 2018 consensus rules SHOULD enforce the following change:
- Update
forkid
[1] to be equal to 0xFF0001.
ForkIDs beginning with 0xFF will be reserved for future protocol upgrades.
This particular consensus rule MUST NOT be implemented by Bitcoin Cash wallet software.
[1] The forkId
is defined as per the replay protected sighash specification.