Bitcoin Cash's next network upgrade is scheduled for May 15, 2026 at 12:00:00 UTC, activating by Median Time Past (MTP) when the most recent 11 blocks reach timestamp 1778846400.
If you're a casual BCH user, this is mostly a background infrastructure event. If you run wallets, nodes, exchange infrastructure, merchant tools, explorers, or contract applications, you should treat it as an upgrade deadline.
Quick Status
| Item | What to know |
|---|---|
| Mainnet activation | May 15, 2026, 12:00:00 UTC |
| Activation rule | MTP >= 1778846400 |
| Test environment | Chipnet activated in November 2025 |
| BCHN release | v29.0.0 |
| Consensus changes | Loops, Functions, P2S, Bitwise |
Do You Need to Do Anything?
If you just hold BCH
Probably not much.
- If you keep BCH on an exchange or custodial platform, watch for a support notice from that provider.
- If you use a self-custody wallet for basic payments, keep the app updated, but this upgrade is mainly relevant to the infrastructure behind the scenes.
- As always, keep your seed phrase backed up and avoid rushing to move funds just because an upgrade is approaching.
If you run a node, payment service, or exchange
Yes, you should prepare before activation.
- Upgrade to a May 2026-compatible node release such as BCHN v29.0.0 or another compatible implementation.
- Test deposit, withdrawal, and transaction parsing flows against the new rules.
- Review monitoring and alerting around activation time, especially if your service pauses BCH operations during network upgrades.
- If you expose transaction data through APIs, review whether downstream clients assume older script patterns or standardness limits.
If you build wallets, explorers, or smart contract apps
This upgrade is important.
- Test on chipnet before mainnet activation.
- Review assumptions around script size, unlocking bytecode size, and token commitment sizes.
- Expect new contract forms and patterns after activation, especially those using loops, functions, or P2S.
- If you use BCHN, look at the new
patternsflag forgetblockandgetrawtransaction, and theupgrade_statusfield ingetblockchaininfo.
What Changes Technically?
The May 2026 upgrade activates four CHIPs:
- Loops adds bounded looping with
OP_BEGINandOP_UNTIL. - Functions adds reusable function definitions and calls with
OP_DEFINEandOP_INVOKE. - P2S makes Pay to Script outputs standard and expands some standardness limits.
- Bitwise re-enables low-level bitwise operations needed by more advanced contract logic.
If you want the fuller technical overview, read our companion article: Bitcoin Cash May 2026 Upgrade - What to Expect.
What This Unlocks
The most interesting impact is not just "more opcodes" - it is that BCH contracts become easier to express and more efficient to use.
- Smaller transaction sizes in many repeated-logic contracts
- Better contract maintainability because reusable functions reduce duplication
- More capable cryptographic scripts thanks to bitwise operations
- Safer, cleaner contract interactions with standard P2S outputs
- Richer CashToken and covenant designs because larger commitments and broader script flexibility reduce workarounds
This doesn't mean every BCH wallet or app changes overnight. It means the platform becomes friendlier to the next wave of contract and token tooling.
Readiness Checklist for Builders
Use this as a practical pre-upgrade checklist:
- Upgrade your node software.
- Test critical BCH flows on chipnet or another compatible test environment.
- Review any custom script classification logic, explorer parsers, and policy assumptions.
- Confirm your wallet or service handles post-upgrade transactions without brittle pattern matching.
- Prepare a simple status page or user notice for the activation window if you operate a public-facing BCH service.
- Plan post-upgrade monitoring so you can inspect the first new script types and contract patterns appearing on mainnet.
Final Take
For regular users, the May 2026 upgrade is mostly a sign that BCH development is still moving forward on a predictable yearly cadence. For developers and infrastructure teams, it is a meaningful improvement to the BCH contract environment and a real deployment milestone that deserves testing, rollout planning, and post-activation monitoring.
The closer we get to May 15, the more valuable clear guidance becomes. Good upgrade coverage is not just "here are the CHIPs" - it is helping users understand whether they need to act, and helping builders understand what to test.
