Yes, Zcash halves, on roughly the same 4 year rhythm Bitcoin uses. The next one arrives at block height 4,406,400, and current projections put that in late 2028. Note the shape of that answer. A height is exact, a year is an estimate, and telling them apart is the first thing worth understanding here.
That is the answer most people arrive for, and it is worth knowing why it is a block number rather than a date. Blocks are produced at an average rate rather than a fixed one, so any calendar date attached to a halving is a projection that moves as block production drifts.
The part almost nobody covers is what actually changes when it happens, and the answer is mostly about miners.
When it happens, and why nobody can promise a date
A halving is triggered by height rather than by a calendar. The chain counts blocks, and at the appointed count the block subsidy drops by half. Nothing schedules it in time, and nothing can, because the only quantity the protocol controls is the count.
The next one sits at block 4,406,400, commonly projected for late 2028 with the exact day dependent on real block production (source: SimpleSwap).
Because blocks arrive on an average schedule rather than a fixed one, the calendar date is derived rather than declared. That is why the countdown pages dominating this search disagree with one another. One of them names November 16, 2028 in its own URL (source: NiceHash), a precision the underlying data does not support. Another competitor corrects the record directly, noting that a halving "scheduled" for November 2025 was a misperception and that the anchor is the block number instead.
If the rhythm sounds familiar, that is because the structure came across with the code Zcash started from. Our guide to how the Bitcoin halving works covers the shape, and the shape transfers intact.
One difference gets misreported often enough to be worth a sentence. Zcash blocks arrive far more often than Bitcoin's, which sounds like it should pull every halving forward. It does not, and the reason is a deliberate piece of arithmetic in the upgrade that made blocks faster. Our guide to Zcash tokenomics works through that calculation and shows the elapsed time coming out unchanged; here the only thing you need is the conclusion, which is that a faster chain did not buy an earlier halving.
So the schedule is Bitcoin's, running on a faster clock that cancels itself out. Which leaves the question of who feels it.
What a halving does to miners
Here is the part the countdown pages skip entirely. A halving is a fifty percent revenue cut, delivered overnight, to the group securing the chain. It is the only thing about a halving that anybody actually experiences on the day, and it lands on people rather than on a chart.
Miners are paid in two ways: the block subsidy, which is new coin issued by the protocol, and transaction fees paid by users. Our guide to who does what on a chain separates the roles, since only one of them is paid this way. On Zcash today the subsidy is the overwhelming majority of that income, so halving it halves miner revenue in all but name.
Nothing about the work changes. The same electricity, the same hardware, the same competition for the same blocks, at half the pay. Our guide to whether mining is profitable walks through the arithmetic that decides who survives that, and it is the same arithmetic here.
The immediate consequence is that the least efficient miners stop. Anyone whose costs sat between the old subsidy and the new one is now running at a loss, and the rational move is to switch off. Our guide to the machines this work runs on explains why efficiency differences between them are large enough for that line to fall in the middle of the field rather than at its edge. Zcash is not resistant to that hardware, so the same specialized machines compete here as elsewhere and the same efficiency spread applies (source: BitDegree).
Then the chain corrects itself. Fewer machines competing means blocks come slower, and the protocol responds by lowering the difficulty until the target rate is restored. Our guide to how difficulty adjusts covers that feedback loop, which is what keeps a halving from stalling a chain. Read it for the principle rather than the timing. The Zcash specification is explicit that the cadence differs, stating that unlike Bitcoin, the difficulty adjustment occurs after every block, using a rolling average of recent blocks and a damping factor rather than waiting for a fixed epoch to end. So the correction is continuous rather than periodic, and it begins on the very next block.
The end state is a smaller set of more efficient miners earning the same total, now halved, split fewer ways. That is the mechanism, and it runs the same way every time.
How the reward split changes the size of the cut
One Zcash-specific wrinkle changes the size of the cut, and a reader carrying assumptions across from Bitcoin will get it wrong. The percentage a halving removes stays identical. The amount does not, because miners were never receiving the whole subsidy in the first place.
The block subsidy is not paid entirely to miners. It is split by consensus rule, with a portion routed to development funding. The project's own network page records the arrangement, stating that as of November 2024, 80 percent of the block reward went to miners and 8 percent to the Zcash Community Grants committee. The remaining 12 percent went to a lockbox with no disbursement mechanism currently defined (source: Zcash), which is a different thing from being spent.
Treat that split as an article-time fact rather than a constant. It is set by consensus rule, it has been revised by network upgrades before, and the figures above carry their own date for that reason. Our guide to the Zcash dev fund covers who receives what and why it is contested.
What matters for a halving is the arithmetic that sits on top of that split, and it is worth doing slowly because the two effects are easy to conflate.
A halving cuts the subsidy in half. It does not touch the split. So a miner receiving four fifths of the subsidy before a halving receives four fifths of the halved subsidy afterwards, which is four fifths of a half rather than a half of everything. The proportion each recipient gets is unchanged and every recipient's absolute amount falls by the same fifty percent on the same block. Miners are already receiving a fraction of the subsidy rather than all of it, so a halving cuts an amount that was already reduced. The percentage change is identical; the absolute amount is smaller than a reader assuming Bitcoin's arrangement would expect.
What a miner actually does in the weeks around a halving
The mechanism above describes what happens to the network. This is what it looks like from inside an operation that has to survive it, which is where the abstraction turns into decisions.
Efficiency gets audited first. The protocol pays the subsidy per block on a schedule that is public years ahead, so nothing about the timing is a surprise to anyone running hardware (source: Electric Coin Co.). The number that matters is energy consumed per unit of work produced, because that is what decides whether a machine sits above or below the new break-even line. An operator who has never computed it for each machine individually usually discovers that the fleet average was hiding a tail of machines that were already marginal.
Power contracts get renegotiated or exited. Electricity is the largest recurring cost in almost every operation, and a fifty percent revenue cut moves the threshold rate a site can pay. Sites on variable tariffs feel this immediately; sites on fixed contracts feel it at renewal, which is why some operations look healthy for months after a halving and then close abruptly.
Older hardware gets switched off rather than sold. The resale market for machines thins at exactly the moment everyone wants to sell, so the realistic options are running them where power is cheapest, storing them against a later recovery, or scrapping them.
Payout thresholds get revisited, and this is the change small operators notice first even though it is the least important of the five. A miner earning half as much per block reaches a pool's minimum payout half as often, which lengthens the gap between payments without changing the annual total. Small operators frequently misread that as an underpayment, then contact support about a shortfall that does not exist. The total arriving over a month is unchanged in coin terms; only the spacing of the payments moved.
And then the difficulty falls. This is the part that rewards patience rather than action. Because the adjustment on Zcash runs after every block rather than on a fixed schedule, the correction begins immediately and accumulates over the following days. An operator who shuts down on day one, and one who waits a week, are looking at measurably different economics for the same hardware.
None of that is unique to Zcash except the adjustment cadence. What is unique is that the cut lands on a subsidy already split with other recipients, so the absolute figures are smaller than the same arithmetic on Bitcoin would suggest.
Four things a halving leaves untouched
Four assumptions travel with the countdown format, and each one sends readers looking for the wrong thing. Two concern supply, one concerns security, and the last concerns price.
It does not change the total supply. The ceiling is 21,000,000 and it is fixed by the schedule (source: Wikipedia). A halving is a step along that path rather than a change to it, and nothing about the endpoint moves.
It does not make the network less secure by itself. Security spending falls, then difficulty falls to match, and the chain keeps producing blocks at the target rate. Whether a smaller security budget is a problem is a real question and a separate one; our guide to what proof of work actually buys frames it properly.
It does not arrive on a date. Every calendar date attached to a halving is a projection from average block production. Treat the block height as the firmer of the two and the date as an estimate.
One caveat belongs with that, and it is the same caveat the reward split carries. The height is fixed by the consensus rules in force now. A proposal exists to replace the step function with a smooth issuance curve, which would end halvings as discrete events altogether; it currently carries the status Draft (source: Zcash Improvement Proposals), so nothing about it is scheduled. Treat the height as firm under today's rules rather than as permanent.
It tells you nothing about price. A supply schedule known years in advance to every participant carries no new information on the day it executes. Our page on what actually moves this asset sorts the real drivers into classes.
From where BloFin sits, the practical note is narrow. A halving changes miner economics on a known block height; it does not change how a ZEC balance is held, withdrawn, or moved. If your interest in the date is operational rather than speculative, the answer is that nothing you need to do changes.
How to work out the next halving yourself
Every input to this is published, so the date nobody can promise is at least a calculation you can run rather than a number you have to accept.
Start with the halving interval. It is a fixed number of blocks written into the consensus rules, and it does not drift (source: Zcash Improvement Proposals). Any source quoting the interval is quoting that rule.
Then find the height of the last halving. Adding one interval to it gives the height of the next one, and that height is firm under the rules in force today.
Then read the current block height from any explorer. Subtracting it from the target height gives the number of blocks still to be produced.
Then convert blocks into time. Zcash targets a block roughly every 75 seconds, so dividing the remaining blocks by 48 gives approximately the number of days, since 48 blocks is roughly an hour's production. That is the projection every countdown page is running, and doing it once shows why the answer moves.
The reason it moves is worth understanding rather than memorizing. The 75-second target is what difficulty adjustment aims at, not what the chain always achieves. When hash rate is rising, blocks arrive slightly faster than target until the next adjustment pulls them back; when it is falling, they arrive slightly slower. Those small deviations accumulate over the hundreds of thousands of blocks between halvings, which is why an estimate made a year out can be off by weeks and an estimate made a fortnight out is usually accurate to within a day.
Two cautions belong with the arithmetic. The interval is fixed by the rules currently in force rather than permanently, and a proposal to replace the step function with a smooth curve would end discrete halvings altogether if it ever activated. And the height is the firm figure while the date is the soft one, so anything that depends on the event should key off the height.
Doing this once has a benefit beyond the number. It shows exactly which input is uncertain, which makes it obvious why two countdown pages showing different dates can both be honest.
It also settles a question that comes up whenever someone compares the two chains. Bitcoin halves roughly every four years because it targets a block every ten minutes across an interval of 210,000 blocks. Zcash reaches the same four-year cadence with a much shorter block time by using a much larger interval, so the calendar matches while the block numbers do not. Anyone reading a Zcash height against a Bitcoin intuition will be out by a factor of roughly eight, and that is the single most common error in comparisons between the two schedules.
One further consequence follows from the shorter block time, and it is the reason the miner section above matters more here than it would elsewhere. Because blocks arrive roughly eight times as often, each one carries roughly an eighth of the reward, and difficulty adjusts after every block rather than after a fixed epoch. The revenue cut is the same fifty percent, but the network's correction to it begins sooner and arrives in far smaller increments. An operator watching the first hour after a Bitcoin halving sees almost nothing; an operator watching the first hour here sees the adjustment already under way.
Frequently asked questions
When exactly is the next Zcash halving?
At block height 4,406,400, which is the only precise answer available. Current projections place that in late 2028, commonly estimated around November, with the actual day depending on how fast blocks are produced between now and then. Countdown sites convert the remaining blocks into a date using an assumed rate, which is why they disagree with one another and why their figures drift. If you need the number for planning, use the height and check the current chain height against it rather than trusting any displayed date.
Does the halving make ZEC scarcer?
It slows the rate at which new coins enter circulation. Scarcity is a different claim. The total that will ever exist was fixed from the start, and every halving on the path there was known in advance. What changes on the day is the flow, not the ceiling, and the flow was already scheduled to change. Treat it as a step in a published plan rather than an event that alters the asset's supply properties.
How long does the adjustment take?
Beginning is not the same as finishing. The response starts on the very next block, but it works from an average of recent blocks and is deliberately damped, so it corrects gradually rather than in one step. That leaves a window where the pay has already fallen and the work has not yet got easier, which is the worst moment to be a marginal miner. Its length depends on how much capacity leaves and how fast, neither knowable in advance. Treat the halving and the adjustment as two events rather than one.
Is the Zcash halving the same as Bitcoin's?
The structure is inherited and the rhythm is close, at roughly four years for both. Two things differ. Zcash blocks arrive far more often, though the halving interval in blocks was scaled to match so the elapsed time did not change. And the Zcash block reward is divided by consensus rule instead of going wholly to miners, so a halving cuts an amount already reduced by that division.
Researched and written by the BloFin Academy editorial team with AI-assisted drafting. Primary sources include the Zcash project's own network documentation. All facts independently verified against cited documentation current as of August 2026. The block reward split and any current subsidy figure are set by consensus rule and have been revised by network upgrades, so both carry their dates in the text and should be re-checked rather than assumed.
This article is for educational purposes only and is not financial advice. Cryptocurrency is volatile and you can lose money. Regulatory treatment of privacy assets differs by jurisdiction and changes over time. Do your own research before making any decision.