Three mid-tier crypto exchanges shut down in 2026. AscendEX stopped operating on 1 July. BitMEX announced its closure on 23 July and shut on 23 September. CoinEx is winding down in steps: it set spot trading to end on 29 September, with withdrawals staying open until 22 December. By mid-year, RootData's tracker counted 99 crypto projects that had died this year, but those three are the ones that matter here, because people used them like accounts.
Most of the coverage stops at the closure. Who lost access and how long the withdrawal window is. That's the front office. I want to write about the back office, because that's where I spend my time: I build a tool that takes a small accounting practice's bank data and puts it into the spreadsheet the practice already runs on. I looked hard at crypto as a source for it in August, and I decided not to build it. The reasons I said no are the same reasons this is going to hurt someone in about a year.
What actually closed them
The easy story is "MiCA killed them". It's close, but the date people quote is wrong. MiCA started applying to crypto-asset service providers on 30 December 2024. The 1 July 2026 date that keeps showing up is only the outer limit of the grandfathering window (Article 143(3)), the grace period for providers already operating under national rules, and several member states ended it earlier than that.
So, the regulation didn't arrive in July. It arrived eighteen months earlier, and July was when the last excuse ran out. For a mid-tier venue the choice was a full licence, with the compliance cost that comes with it, or leave. Three of them left.
The tax year outlives the venue
Here is the part that makes it an accounting problem and not a news story.
The EU's crypto reporting directive (DAC8) has been in force since 1 January 2026. Exchanges collect data through 2026 and file the first reports between January and September 2027. So 2026 is the first year in which a European's crypto activity becomes visible to their tax authority as a matter of routine.
Put the two timelines next to each other. A client traded on one of these exchanges in the first half of 2026. Their accountant sees the numbers in spring 2027, maybe prompted by a letter from the tax authority, which by then has data the client never looked at. By then the venue that produced the history may not exist anymore, and the client may not be able to log back in to re-download the statement. Whatever the client exported before that point is now the only record, and I'd guess most clients won't export anything until someone asks them to.
Why an exchange export is worse than a bank statement
When I looked at crypto for my own tool, I expected it to be another source. Bank statement in, rows out. It isn't, for three reasons.
An exchange export is incomplete by design. It shows what happened inside that venue. Internal transfers, failed transactions and staking rewards show up inconsistently or not at all, depending on the venue and on which export you picked.
Cost basis lives across venues. Bought on one exchange, moved to a wallet, sold on another. No single exchange knows what the asset cost. The number the tax return actually needs is stitched together from several sources, and one of those sources just disappeared.
There is no authoritative statement to check against. With a bank, I can take the opening balance, add the transactions and check that I land on the closing balance the bank printed. If it doesn't tie out, something is missing and I know it. With an exchange, the export IS the unreliable object. There's nothing independent to reconcile it against, and after closure there never will be.
The third one is the one that bothers me most. A bank reconciliation fails loudly when rows are missing. An exchange history just looks shorter.
What I'd do this week, if I had a client on one of them
None of this needs a product. It needs a checklist, and it needs to happen soon: CoinEx withdrawals close on 22 December. After that, whatever is left moves into custody at a monthly fee of 5% of the original balance, and claims close in August 2028. BitMEX and AscendEX have given no guaranteed end date for theirs, which is not reassuring.
Export everything the venue still offers: trade history, deposits, withdrawals, fees and any staking or earn records. Separate files are fine, keep all of them.
Save the final balance screen (a screenshot is fine) the day before the last withdrawal. It's the closest thing to a closing statement you're going to get.
Note where every withdrawal went. That address or account is where the cost basis continues, and it's the thread the accountant will need to pull next year.
Convert to fiat at the transaction date, and keep the rate you used next to each row. Doing that in 2027 from memory is much harder.
Check it yourself, once: deposits minus withdrawals, plus or minus trades and fees, should land on zero after the final withdrawal. If it doesn't, something is missing, and you can still go back and look now. Access to any of these three could tighten without much more warning than they've already given.
Why I'm not building this
I'd argue the demand is real and it has a date on it. Even so, it's the wrong thing for me to build right now. It expires by design (CoinEx closes withdrawals on 22 December, and the other two could follow). The buyer is a crypto holder and not the accountant I sell to, and cost basis across venues is a different product from the one I'm building. The tools that already do cost basis are mature and cheap.
So, I'm writing it down instead. If you're an accountant with a client on AscendEX, BitMEX or CoinEx, send them the checklist above now, while the withdrawal window is still open.
About the author
- Founder-Engineer & Full-Stack Architect · Building B2B utilities end-to-end on a single Hetzner VPS gil-neto.com
Comments
Join the discussionOne tricky case is when a withdrawal from a closing exchange and a deposit on another platform look like two separate transactions, even though they’re just two sides of the same transfer.
Say a client withdraws 2.4 ETH from BitMEX, pays a 0.003 ETH network fee, and receives 2.397 ETH in their own wallet before depositing it into another exchange. If the export from the first platform is missing, the receiving exchange might show an unexplained deposit with no original cost basis. Treating the withdrawal as a disposal and the deposit as a new acquisition could create a completely fictional gain.
I’d keep a transfer-matching ledger that links both sides using transaction hashes, timestamps, asset quantities, and destination addresses, while tracking fees separately. If the source record is missing, the match should remain provisional rather than silently inventing a cost basis.
The interesting question is what happens when the original exchange disappears before the match can be verified. Would you preserve that uncertainty explicitly in the accountant’s report, rather than forcing the reconciliation to balance?
Yes, I'd surface it. Forcing it to balance hides exactly what the accountant needs to know, which is that a piece of the history can't be checked anymore.
I'd split it in two. The transfer itself usually survives the exchange, because the withdrawal is on-chain. With the hash, the amount and the destination address you can still show that 2.397 ETH arrived in the client's wallet. What dies with the exchange is the other half, what the client paid for that ETH in the first place. So the match can be confirmed while the cost basis is still unknown, and I'd want the report to say those two things separately - transfer matched, cost basis missing because the source closed.
That's also why the checklist in the post asks where every withdrawal went.
The tricky part is that an on-chain match doesn't necessarily prove who owned the assets on either side. Take a client who withdraws 18.6 ETH from a failed exchange, pays a 0.012 ETH network fee, and sends the rest through a self-custody wallet before depositing it into an exchange that batches customer deposits. You might be able to trace the transaction hashes and reconcile the amounts, but the deposit address alone won't establish that the wallet belongs to the client or recover the original acquisition lots.
I'd keep transfer verification, wallet ownership evidence, and cost-basis provenance as separate fields. That way, even if the movement is fully traceable, the report can show exactly which part is supported by on-chain data and which part still depends on historical exchange records. Otherwise, a technically correct transfer match can still feed an unsupported cost basis into the gain calculation.
The question I'd be interested in is how you'd handle partial recovery of the old records, where some acquisition lots can be verified but the rest of the balance can't.