If I wasn't at my computer when the depeg event happened, and by the time I noticed several hours had passed, is there still a way to remedy this?
Yes, most mainstream market data websites preserve historical price data, letting you query a specific timestamp to find the market price at that time — even without your own real-time screenshot, this kind of objective market data can typically still be verified afterward. What's genuinely hard to remedy after the fact is a protocol's official real-time statement issued at the moment of the event, which might later be taken down or modified — for this kind of information, it's advisable to look for a backup or archived version as soon as you discover it.
In practice, discovering it a bit later usually doesn't cause an irremediable consequence, but it's advisable to start recording the moment you discover it, rather than simply giving up on recording because "the golden window has already passed" — the later you start recording, the fewer details typically remain verifiable.
After a depeg event happens, I'm planning to actively sell part of my position to reduce risk — how does this affect the subsequent taxable determination?
If you actively sell part of your position while the depeg event is being confirmed, that sale itself typically constitutes a clear disposition event, requiring the gain or loss to be calculated using the actual market price at the moment of sale (not the original anchor value). This transaction also becomes a dividing point on your entire holding period — the remaining unsold portion needs a separately determined reasonable taxable moment, based on the depeg event's eventual confirmed direction (brief fluctuation or permanent failure).
This means that if you plan to make this kind of risk-reducing sale, the earlier and more clearly you record that transaction's specific timing and execution price, the better, since you may later need to compare that transaction's data against the depeg event's own timeline to confirm the sequence and corresponding calculation logic.
If a protocol issues a remediation plan a few weeks after depegging, but the plan itself is still in a testing phase with unknown success, how should I record this?
This falls under the "partial depegging, mechanism continues attempting recovery with uncertain effect" scenario discussed in another term on this site — the hardest category to handle. A more resilient approach in practice is to individually record the timing the remediation plan was issued, the plan's specific content, and every subsequent progress update, building a complete event timeline, rather than only recording the two endpoints of "depegging happened" and "final outcome."
This progressively accumulated timeline, regardless of whether it eventually ends in recovery or failure, helps you (or the tax professional assisting you) go back and determine at which point objective evidence already sufficiently supported the judgment "this has already constituted a major state change," rather than vaguely reconstructing a fuzzy point in time based on impression after the fact.
If the stablecoin I hold spans multiple exchanges and self-custody wallets simultaneously, when a depeg event happens, do I need to record it separately on each platform?
Yes, even though the depeg event itself is a single market-level event (that token's market price is depegging overall), the positions you hold across different platforms are theoretically each independent asset batches, each potentially with different cost bases and holding histories, requiring separate recording and assessment. This is also an extension of the cross-platform data reconciliation issue discussed in another term on this site, applied to this particular scenario of a depeg event.
In practice, it's advisable that when a depeg event happens, you simultaneously confirm the actual quantity you hold on each platform, and separately record the market information each platform is showing at that moment, avoiding a situation where you only record data from one platform while overlooking positions scattered across others, causing part of your assets to be missed when it comes time to file.
The tax classification of a depeg event has already been explained in another term on this site — brief fluctuation, permanent failure, and partial depegging apply entirely different treatment logic. This article doesn't rehash that classification principle — instead it focuses on a more urgent question: the moment you discover a stablecoin you hold is depegging, what specific actions should you take immediately to preserve the data and options you'll need for future filing?
At the moment a depeg event happens, you won't know whether it will ultimately be brief fluctuation or permanent failure — that determination typically can only be confirmed in hindsight. But regardless of which outcome it eventually turns out to be, the golden window for recording is the moment the event happens, not once the dust has settled. Immediately screenshot and record the market price and transaction timestamp at that moment, and preserve any statement or explanation the protocol officially issues (if it does).
When depegging happens, a common intuitive reaction is "this is just temporary, I'll wait it out and let it recover" — this reaction isn't wrong by itself, but if you plan to rely on this assumption to take any trading action (like adding at the low point, or rushing to sell to hedge), recognize that these actions will create new dividing points on your holding timeline, making subsequent cost basis calculation more complex. If you're unsure you've thought it through, pausing action and observing first is typically the more resilient approach.
The days to weeks following a depeg event are typically the critical observation window for determining that event's eventual direction. Keep monitoring the protocol's official announcements and the token's market price movement, and record every significant development during this observation period (such as remediation measures the protocol announces, key turning points in market price) — this record will become an important basis for judging a reasonable taxable moment in the future.
If you actively traded this batch of assets at any point around the depeg event (adding to the position, partial selling), you need to first confirm the timing of those trades relative to when the depeg event is confirmed to have occurred — this sequence affects which market price your active trade's cost basis should be calculated at, and also determines whether the entire holding period needs splitting into different segments handled separately.
At the moment a depeg event happens, most people's intuitive reaction is to focus on the impact to their own net worth, temporarily overlooking what needs handling on the tax side — but the highest-value moment for tax-related recordkeeping happens to be precisely those first few days after the event, since the verifiability of market data declines as time passes. It's advisable to treat "record immediately" and "keep tracking subsequent development" as two separate habits — the former is something to do right at that moment, the latter is something to keep doing over the following weeks. Doing both properly is what gives you complete data to support your judgment when the time to file eventually comes.
⚠️ This article was researched against the most current regulations and official guidance available at the time of writing, but tax rules change frequently, and the applicable rules can vary by jurisdiction and individual circumstance. This content is intended to help you understand concepts and general direction — it does not constitute formal tax or legal advice. Before filing, please verify current rules directly with the official tax authority in your jurisdiction, or consult a qualified tax professional.