What Happens to a Price Feed During a Stock Split?
Stock splits don't move markets. But a price feed that can't tell the difference will. Pyth handles it.
Education
Apr 6, 2026

A 4:1 stock split cuts the reported price by 75% overnight. A 1:10 reverse split multiplies it by 10. These are not market events. No buying or selling pressure caused the move. The company's market cap has not changed.
But any system reading the raw price without context will interpret the change as a crash or a spike.
For traditional brokerages and portfolio trackers, corporate actions are a back-office problem handled by reference data teams and corporate action processors. For decentralized applications consuming price feeds, the problem is harder. There is no back office. The price feed is the system of record. If it gets the post-split price wrong, the consequences are immediate: false liquidations, corrupted collateral valuations, and cascading risk events.
What Are Corporate Actions?
Corporate actions are events initiated by a public company that change the structure or value representation of its shares. The most relevant for price feed infrastructure are:
Stock splits increase the number of outstanding shares by a fixed ratio while proportionally reducing the price per share. A 4:1 split means every shareholder receives 4 shares for every 1 they held, and the price adjusts to one-quarter of its pre-split value. Total market capitalization stays the same.
Reverse splits do the opposite. A 1:10 reverse split consolidates 10 shares into 1 and multiplies the price by 10. Companies typically execute reverse splits to raise their share price above exchange minimum listing requirements.
Delistings remove a stock from exchange trading entirely. The price feed must stop producing updates and clearly signal that the instrument is no longer active.
Each of these events produces a planned price discontinuity on a specific date known as the ex-date. Unlike gaps caused by earnings or macro events, the ex-date is announced in advance, sometimes weeks ahead. The challenge is not predicting when it will happen. The challenge is coordinating a precise, simultaneous adjustment across every data source contributing to the feed.
Why Corporate Actions Break Price Feeds
The core problem is simple: the price before the ex-date and the price after the ex-date are not comparable. A price feed that publishes $400 at market close on Monday and $100 at market open on Tuesday (after a 4:1 split) has not recorded a 75% decline. It has recorded a structural repricing. But any automated system consuming that feed without adjustment will treat it as a real price move.
The downstream effects depend on the application:
Lending protocols using the equity as collateral will calculate a sudden, massive drop in collateral value. Positions that were healthy at $400 appear catastrophically under-collateralized at $100. Automated liquidation logic will fire.
Perpetual futures platforms referencing the feed for mark price will see funding rates spike as the mark price diverges from the pre-split expectation. Traders holding positions through the ex-date face unexpected settlement amounts.
Options and structured products referencing equity feeds must adjust strike prices and contract multipliers in lockstep with the split. A feed that does not signal the corporate action leaves these instruments mispriced.
The problem compounds in overnight markets. Splits typically take effect at the start of trading on the ex-date. The overnight session preceding the ex-date is where the transition happens. If a venue like Blue Ocean ATS halts trading on the affected ticker during that window (which it does), the feed must also stop publishing. Any system that interprets the absence of updates as "price unchanged" rather than "trading halted for corporate action" will carry the stale pre-split price into the next session.
The Ex-Date Workflow
Handling corporate actions correctly requires a coordinated, multi-phase process across every publisher contributing to the affected feed. The process is not just about adjusting a number. It is about ensuring that every data source transitions simultaneously so the aggregate price is never corrupted.
Phase 1: Advance notice. Corporate actions are announced well before the ex-date. Reference data reflecting the upcoming action is produced and distributed, enabling consumers to initiate their own change management processes. For protocols and applications, this is the window to adjust positions, collateral parameters, and risk models.
Phase 2: Overnight halt. On the night before the ex-date, overnight trading venues halt trading on the affected ticker. No feed updates are generated during this window. A market schedule holiday is added via governance to prevent the production of any new price while the market is closed for that specific instrument.
Phase 3: Publisher adjustment. Before the next session opens, every publisher contributing to the affected feed must apply the split ratio to their pricing engine. This is not optional. Any publisher that is not ready must stop publishing to avoid corrupting the aggregate with an unadjusted price. Non-compliance exposes publishers to slashing risk within the Pyth network.
Phase 4: Rejection window. When the next session opens (typically pre-market at 4:00 AM ET), the aggregator computes the expected post-split price using the formula: last known price multiplied by the split denominator divided by the split numerator. Any publisher whose submitted price deviates beyond a configurable threshold from this expected value is rejected. Only correctly adjusted prices enter the aggregate. This rejection window can last up to 12 hours.
Phase 5: Normal aggregation. Once the rejection window expires and all contributing publishers are aligned, standard aggregation resumes. The feed is now producing the post-split price with full publisher consensus.
How This Works at the Infrastructure Level
Corporate actions on the Pyth Network are managed through governance instructions that update feed metadata. The implementation stores the action as structured data attached to the specific feed, including the type of action (split or reverse split), the adjustment factor expressed as a numerator and denominator, the activation type (tied to the US equity ex-date), and configurable rejection thresholds.
The aggregator maintains per-feed state, including the last known price. This state persists across restarts, which means the rejection logic remains effective even if infrastructure is cycled during the overnight window. The entire system is feature-flagged and operates at the aggregator level, making it possible to handle corporate actions on a per-feed basis without affecting other instruments.
This infrastructure was validated during the NFLX stock split on November 17, 2025. All contributing publishers reflected the adjusted price within the expected window during the pre-market session, and the aggregate transitioned cleanly without producing any corrupted price points.
What Builders Should Do
Applications consuming equity price feeds should not treat corporate actions as edge cases. They are scheduled events that require explicit preparation.
Monitor upcoming actions. Track announced splits, reverse splits, and delistings for every equity feed consumed. The advance notice period (often weeks) provides ample time to prepare.
Adjust internal parameters before the ex-date. Collateral ratios, liquidation thresholds, strike prices, position sizes, and any other parameter that references the nominal share price must be adjusted to reflect the post-action value.
Handle the overnight halt correctly. On the night before the ex-date, expect the feed to produce no updates for the affected ticker. Use the marketSession field and feedUpdateTimestamp to distinguish a corporate action halt from a market outage. These are fundamentally different conditions requiring different responses.
Do not carry stale pre-split prices into the next session. If the feed has not updated since before the halt, the last known price is the pre-split price. Using it as-is after the ex-date will produce catastrophically wrong calculations.
Validate the first post-action price. When updates resume, verify that the new price is consistent with the expected post-split value. A simple check: multiply the last pre-split price by the adjustment factor. If the first post-action price is within a reasonable tolerance of that expected value, the transition was successful.
Why This Matters
Corporate action handling is infrastructure that is invisible when it works. Most data consumers will never think about it. But the absence of this infrastructure creates some of the most severe failure modes in equity pricing: a 75% apparent crash that is actually a split, a 10x apparent spike that is actually a reverse split, or a feed that keeps publishing prices for a delisted stock.
For any application where pricing accuracy has financial consequences, the question is not whether corporate actions will affect the feeds being consumed. They will. The question is whether the price feed provider has the infrastructure to handle them correctly.
Pyth Pro delivers 3,000+ price feeds across equities, crypto, FX, commodities, and fixed income through a single integration. That includes 24/5 US equity coverage across all four trading sessions, sourced from the institutions that set prices. Book a demo with an authorized distributor here.
Disclaimer
This post is for informational and educational purposes only and does not constitute legal, financial, investment, or any other form of professional advice. All accuracy figures and performance metrics cited herein are based on historical observations during specific periods and are not a guarantee of future performance or data quality; actual results may vary materially depending on market conditions, liquidity, and other factors. References to specific exchanges, venues, protocols, or products are for illustrative purposes and do not constitute an endorsement or warranty of any kind. Digital assets, decentralized finance protocols, and related products carry significant risks, including the risk of total loss. Readers should conduct their own independent due diligence and consult qualified professionals before making any decisions based on the information presented here.
Similar stories


DeFi Use Cases Beyond Banking: Real Estate, Gaming, and More
Education
Apr 25, 2024


How DeFi Empowers Financial Inclusion and Accessibility
Education
Apr 16, 2024


Why Community Matters
Education
Apr 1, 2024


The Commodities Market Explained
Education
Mar 18, 2024


Everything You Need to Know About the Pyth Network
Education
Nov 3, 2023


What is a Blockchain Oracle?
Education
Jun 16, 2023