What to save — before January 31, 2027

The exchange has announced full closure on January 31, 2027, with only limited account access afterward. Everything below lives inside your account or your inbox — once access ends, most of it is gone for good. Do this in one sitting, today. ← Back to main page

Before you start: preserving evidence means saving records that already exist — not creating new identity documents. Do not photograph or upload government ID. Redact your account email from screenshots if you prefer; balances and statuses are what prove a claim.

The checklist

Highest priority — only you have these

☐ Full account export (CSV). From your account's export/statement function: balances, deposit history, trade history, and — critically — the withdrawal request history showing each request's ID, date, amount, and status (pending / rejected / completed). Our registration form can parse a balances CSV in your browser and preview the table before anything is sealed.
☐ Balance screenshots. Per asset: total, available, and frozen amounts. Capture the whole page including URL bar and today's date. Screenshot any "pending" or "rejected" withdrawal rows on their own screens too.
☐ Withdrawal request IDs. Every request ID, transaction/hash field, and support ticket number — written down somewhere durable, not just left in the app.
☐ Every exchange email as a real file. In Gmail: open the email → ⋮ → "Download message" (.eml). In other clients: "Save as" / "Show original". The headers are what authenticate an email later — a screenshot proves much less. This includes the wind-down announcement, cutoff notices, support replies, and ticket closures.
☐ In-app notices. Announcement banners, the withdrawal-cutoff notice, feedback-portal text — screenshot them in place, with dates visible.
☐ Your own deposit records. Bank/card statements showing fiat deposits to the exchange; on-chain deposit transaction hashes from your own wallets to your exchange deposit addresses.
☐ Your account identifiers. Account ID / UID, registered-email hint, KYC status page — enough to match your claim to your account later.

For token projects and market makers

☐ Treasury / market-making account balances per asset, as above
☐ Listing agreements, market-making contracts, and any exchange correspondence about treasury custody
☐ Internal records of what was deposited for listing or liquidity purposes, with transaction hashes

For employees with wage claims

☐ Employment contract / offer letter
☐ Payslips, payroll records, and any correspondence about unpaid wages
☐ Note: wage claims rank differently from customer claims in most insolvency regimes — keep your file separate and consider your own counsel

How to store it

Two copies, two places. A local copy and a second copy off the same device — an encrypted drive, a different machine, or a sealed submission here.
Keep originals. Store the exported CSV and the .eml files unmodified alongside any annotated versions — originals authenticate; edits don't.
Write a one-page summary. Your account ID, per-asset balances, each withdrawal request (ID, date, amount, status), and the timeline of your contacts with support. Future-you — and any claims agent — will thank present-you.

Then register it. Once your evidence is preserved, add your claim to the register — sealed in your browser, pseudonymous, free. A row in the register is what turns your preserved file into part of a quantified claim pool.