- dYdX’s front end is not offered to US persons, and that fact drives most of the US tax thinking here — not the contracts.
- Permission and reportability are unrelated questions. A venue’s terms are a contract with that venue, not a definition of your tax base. If you hold a US filing obligation, realised gains are reportable — and the absence of a form changes your evidence, not your liability.
- It makes records harder, not easier. A position on a venue that does not serve you depends more on your own records, because nobody will ever produce a statement for it.
- The §1256 venue requirement is not met, as far as we can establish — no qualifying designation, and an appchain has no registrant that could hold one. What the gain is instead stays open.
- Staking is the part with real authority. Rev. Rul. 2023-14 puts reward units in gross income at fair market value when you gain dominion and control. The hard case is a reward that auto-compounds into a delegation subject to an unbonding period — arguably not immediately transferable.
- Unbonding is not a disposal. It is a liquidity restriction, not an exchange. Do not report the start or end of unbonding as a sale — but do record the dates, because they bear on when rewards became transferable.
dYdX is the perp venue with a tax situation no other venue on this site has, and it has nothing to do with the contracts. Its front end is not offered to US persons. The dYdX Foundation’s own terms state that its services and products are not available to residents of, or persons located or incorporated in, the United States, among other restricted territories.
That single fact generates most of what a US taxpayer needs to think about here, and it is not what people expect. It does not make the income invisible, and it does not make it untaxed. What it does is make the records harder and the questions sharper.
Whether you were permitted to use a platform and whether your gains are reportable are two unrelated questions. US federal income tax reaches income from whatever source derived. A venue’s terms of service are a contract between you and that venue; they do not define your tax base, and breaching them does not remove income from your return. So if you hold a US filing obligation and you realised gains on dYdX, those gains are reportable — and the absence of any form reporting them changes your evidence, not your liability.
The practical consequence runs the other way from what people hope: a position taken on a venue that does not serve you is more dependent on your own records, not less, because there is nobody who will ever produce a statement for it.
To be plain about what this page is: it is for someone reconciling activity that already exists — from a prior year, from before a restriction applied, from an entity in another jurisdiction, or from a non-US period of residence. It is not a guide to accessing a venue that excludes you, and nothing here should be read as suggesting a way around a restriction.
Platform structure, and why it matters for the tax analysis
dYdX’s current version runs on its own application-specific chain built with the Cosmos stack, rather than as a contract set on a general-purpose chain. Order matching and settlement happen on that chain; the website most people think of as “dYdX” is a front end operated separately from the protocol.
Two consequences for a US return:
- The venue prong of §1256 is not met. The 60/40 split requires a qualified board or exchange — broadly an SEC-registered national securities exchange, a CFTC-designated contract market, or a market Treasury has specifically determined has adequate rules. As far as we can establish dYdX holds none of those, and an appchain has no registrant that could hold one. That turns on public record rather than on a view about the product, so it is the most checkable statement here — and it describes the present, since designations change. What the gain is instead is open; the framework is on perpetual futures taxes.
- The front end and the protocol are different things, and your records may live only on the second. Access through an interface can end without the chain forgetting anything. That is better than a centralised venue closing your account, and worse than it sounds: the data is intact, and nothing is formatted for a tax return.
Staking DYDX on a Cosmos-style chain: the unbonding wrinkle
An appchain built this way generally secures itself by delegating the native token to validators, who distribute rewards to delegators. That is the fact pattern Rev. Rul. 2023-14 is closest to: a cash-method taxpayer who stakes a proof-of-stake cryptocurrency and receives validation reward units includes their fair market value in gross income in the year they gain dominion and control — broadly, when they can sell or otherwise transfer them — and that amount becomes basis. Of everything on this page, this is the part with real authority behind it. Note the conditions, though: they are the holding, and a delegator on a particular appchain is applying it rather than reading an answer out of it.
But delegation on chains of this design has a feature that makes the standard genuinely interesting: an unbonding period. Withdrawing a delegation typically takes a fixed number of days during which the stake is neither earning nor transferable.
The ruling turns on when you can sell or otherwise transfer the reward. Three distinct situations arise here and they do not share one answer:
- Rewards that accrue claimable. If a reward is claimable to your own account at will, the analysis resembles the ruling’s: income around the point you can reach it. The practical question is whether you measure at accrual or at claim — pick a convention and hold it.
- Rewards that auto-compound into the delegation. If a reward is added to staked principal rather than paid out, it is arguably subject to the same unbonding constraint as the principal — which is a real argument that transferability, and therefore income, is not immediate. Arguable, not settled.
- The principal in unbonding. Unbonding is not itself a disposal — you are not exchanging the token for anything. It is a liquidity restriction, not a realisation event. The error to avoid is treating the start or end of unbonding as a sale.
This is INTERPRETIVE. The ruling addresses receiving reward units; it does not address a reward that lands inside a locked delegation. We are applying its standard, and saying so.
Slashing is the other item worth naming. If a validator you delegated to is penalised and your stake is reduced, you have lost value through no transaction of your own. Whether that is a deductible loss, and of what character, depends on facts including whether your staking is part of a trade or business — and for someone who is not in a trade or business, the permanent suspension of miscellaneous itemized deductions makes a casual-investor loss hard to use. There is no guidance on slashing. Record the event, the amount and the date; do not assume a deduction.
Trading rewards paid in a token
Venues of this kind have at various points paid traders in the native token for volume or activity. The characterisation is relatively clean even though no guidance names it: a token received in return for doing something is generally income at its fair market value when you have dominion and control over it, and that value becomes your basis in the token. A later sale is a separate capital transaction measured against it.
The common and expensive mistake is the same one that catches airdrop recipients: skipping the income step because no form arrived, then selling against a zero basis. That pays tax on the full proceeds as gain and throws away the basis you were entitled to — and if the token fell between receipt and sale, you can end up taxed on value you never realised.
We are not asserting which reward programmes are currently running, at what rate, or in what form. Programmes of this kind start, change and end by governance vote. Not publicly verified; check the protocol’s current documentation.
Records: the chain has everything and owes you nothing
A non-custodial appchain is generally not issuing a 1099-B, 1099-DA or 1099-MISC, and that became more certain rather than less — the regulations that would have imposed broker reporting on decentralised front ends were repealed in April 2025 by a Congressional Review Act resolution.
What makes this venue different from a centralised one is that your history is not hostage to your account. Chain data persists whether or not an interface serves you. What makes it harder is that reading it usually means an indexer or a third-party tool rather than a download button, and the tooling layer is the part that changes.
The filing record checklist
- Your address or subaccount identifiers, written down somewhere that is not only the wallet. Without the identifier, the on-chain history is not findable, and this is the single most common unrecoverable failure.
- Every fill — timestamp, market, side, size, execution price, and fees separately from price.
- Funding payments — each one, with sign, timestamp and USD value. The item most often lost, and the one that decides which funding treatment you can support.
- Collateral in and out — the asset, the amount, and the USD value at the time. A stablecoin deposit still needs a dollar figure; a volatile asset needs one at every movement and has its own disposal history.
- Staking — each reward with date and USD value, which validator, whether it paid out or compounded, every bonding and unbonding event with dates, and any slashing with the amount.
- Token rewards — date, quantity and USD value on receipt. That is your basis.
- Liquidations — what closed, at what price, and what was taken as fee or penalty.
- The period each position belongs to, including your own residence and filing status at the time. On a venue with jurisdictional restrictions this is the context that makes a reconstructed history make sense years later.
Export on a schedule. The chain will still be there; the tool that turns it into rows may not be, and reconstructing a year of funding and staking events from raw transactions in April is a different job from keeping a log.
What we are not asserting
We did not open dYdX’s own documentation or terms from this environment — outbound access is blocked here, so the structural description above comes from publicly available accounts rather than from the source. Restricted-territory lists, chain architecture, reward programmes and unbonding parameters are all changeable, several by governance vote.
We are not asserting the current restricted-territory list, the current unbonding period, which reward programmes are live, what entity is your counterparty, or which jurisdiction any term selects. Where we have not confirmed something we say not publicly verified. If a parameter matters to your return, check it against the protocol’s current documentation on the day you rely on it — and for anything touching eligibility or residence, that is a conversation for a professional rather than a web page.
Where this fits
The characterisation framework and the venue comparison are on perpetual futures taxes. Hyperliquid and GMX cover the other large venues — GMX in particular raises the escrowed-reward timing question in its sharpest form. For basis, disposals and the Form 1040 digital-asset question see crypto taxes. If this activity is large enough to look like a business, the §475 mark-to-market election changes the capital-versus-ordinary question — and its deadline runs to the unextended due date of the prior year’s return, which is earlier than almost everyone assumes.
The unbonding question here has a close cousin on Drift, whose Insurance Fund staking carries a reported 14-day cooldown — but where the consideration is bearing credit risk rather than validating a chain, so the staking ruling is a worse fit there than it is here. Jupiter raises the opposite problem: fees reported to compound into a pool token’s unit price, with no receipt event at all.
The first one matters most here. Whether you are carrying on a trade or business — rather than investing — is what decides how funding you paid is treated, and on a high-funding book that is the difference between a deduction and nothing. It is worth settling before filing season, not during it.
Frequently Asked Questions
dYdX does not serve US users — do I still owe tax on gains I made there?
Yes, if you hold a US filing obligation. Whether you were permitted to use a platform and whether your gains are reportable are two unrelated questions: US federal income tax reaches income from whatever source derived, and a venue's terms of service are a contract between you and that venue rather than a definition of your tax base. Breaching them does not remove income from your return. The practical effect runs opposite to what people hope — a position on a venue that does not serve you depends more on your own records, not less, because nobody will ever produce a statement for it.
Do dYdX perps get Section 1256 60/40 treatment?
Very likely not, because the venue requirement is not met. §1256 requires a qualified board or exchange — broadly an SEC-registered national securities exchange, a CFTC-designated contract market, or a market Treasury has determined has adequate rules. As far as we can establish dYdX holds none of those, and an application-specific chain has no registrant that could hold one. That rests on public record rather than on a view about the product, though designations can change. What the gain is instead remains open.
How are DYDX staking rewards taxed?
This is the part with real authority behind it. Rev. Rul. 2023-14 holds that a cash-method taxpayer who stakes and receives reward units includes their fair market value in gross income in the year they gain dominion and control — broadly when they can sell or otherwise transfer them — and that amount becomes basis.
The wrinkle on a chain of this design is the unbonding period: a reward that pays out to your own account resembles the ruling's facts, while a reward that auto-compounds into a delegation subject to unbonding arguably is not immediately transferable, which is a real argument that income is not immediate. That part is an application of the ruling's standard rather than a holding.
Is unbonding or unstaking a taxable event?
Generally no. Unbonding is a liquidity restriction, not an exchange — you are not giving up the token for anything else, so there is normally nothing realised. The error to avoid is treating the start or the end of an unbonding period as a sale. What does need recording is the dates, because they bear on when rewards became transferable and therefore on when income arose under the dominion-and-control standard.
What happens if my validator gets slashed?
You have lost value without any transaction of your own, and there is no guidance on it. Whether that is a deductible loss, and of what character, depends on facts including whether your staking is part of a trade or business — and for someone who is not, the now-permanent suspension of miscellaneous itemized deductions makes a casual-investor loss hard to use. Record the event, the amount and the date, and do not assume a deduction.
Does dYdX issue a 1099?
Generally no. It is a non-custodial protocol that does not act as a broker, and the regulations that would have imposed broker reporting on decentralised front ends were repealed in April 2025 by a Congressional Review Act resolution. The absence of a form changes your evidence, not your liability. One thing works in your favour here: chain data persists whether or not any interface serves you, so the history is not hostage to an account — but reading it usually takes an indexer or a third-party tool rather than a download button.
How are trading rewards paid in a token taxed?
A token received in return for doing something is generally income at its fair market value when you have dominion and control over it, and that value becomes your basis. A later sale is a separate capital transaction measured against it. The expensive mistake is the airdrop mistake: skipping the income step because no form arrived, then selling against a zero basis — which taxes the full proceeds as gain and discards the basis you were entitled to. We are not asserting which reward programmes are currently running or at what rate; those change by governance vote.
What is the single most important record to keep for dYdX?
Your address or subaccount identifiers, stored somewhere that is not only the wallet. Everything else can be rebuilt from chain data eventually, but without the identifier the history is not findable at all — it is the most common unrecoverable failure on a non-custodial venue. After that: funding payments with signs and timestamps, and staking events with dates and USD values.
Trading perps and not sure where you stand?
Take the free Tax Snapshot and get matched with a CPA who has actually filed derivative positions like these — not one learning the product on your return.
Get My Free Tax Snapshot →Tax treatment depends on the specific instrument, activity, entity and taxpayer circumstances. TraderTax provides general educational information; your treatment may differ. Nothing here is advice on your return.