What this site is

BitMartExchange.app publishes independent, security-first research on the BitMart exchange app and the decisions that surround it: where to download software safely, how to harden an account, what a funding route actually costs, which jurisdictions can use what, and — the question underneath all of them — whether an exchange is the right place for your assets at all.

We write for someone who is about to move real money and wants to know what can go wrong before it does. That means covering the parts a marketing page omits: incident history, thin liquidity, fee layers that are disclosed in four different places, and the specific mistakes that are irreversible.

What this site is not

  • Not the official BitMart website. We are a third party writing about a product we do not operate.
  • Not financial advice. Nothing here is a recommendation to buy, sell or hold any asset. We are not licensed advisers and nothing on this site is personalised to your circumstances.
  • Not a support channel. We cannot help with locked accounts, missing deposits, frozen withdrawals or lost funds. Nobody on this site will ever contact you offering to.
  • Not a price prediction site. We do not publish forecasts, signals or targets. If we knew where prices were going we would not be writing guides.
  • Not a promoter. We do not encourage trading, and several pages here actively argue against behaviour that would earn us more commission.

Who writes it

The site is written by people who have worked in and around cryptoasset infrastructure since 2017 — through the 2018 drawdown, the 2020 DeFi expansion, the 2022 exchange collapses and the regulatory consolidation that followed. That period is the qualification: we have watched what happens to people who kept everything on a trading venue, and the pattern does not change.

We publish under the site's name rather than personal bylines. Security writing attracts targeted attention, and named authors covering exchange vulnerabilities become targets themselves. The trade-off is that you cannot check our individual credentials, so we compensate the way we would want a source to: every factual claim is attributed, every limitation is stated, and we say plainly when we do not know something.

How we research

  1. Primary sources first. Fee schedules, terms of service, security documentation and official announcements — read directly, not summarised from another article.
  2. Hands-on use. We install the apps, complete verification, run the flows and hit the errors. Guides describe screens we have actually seen.
  3. Public incident records. Breach reports, blockchain forensics from firms like PeckShield and Chainalysis, regulatory filings and enforcement actions.
  4. On-chain verification where possible. Claims about reserves, flows and incidents are checked against public chain data rather than taken on assertion.
  5. Regulatory primary sources. NYDFS materials, FinCEN guidance, MiCA texts and IRS publications — not blog posts about them.

Where we cannot verify something, we say so explicitly rather than filling the gap with a confident guess. You will see phrases like "not publicly disclosed" throughout the site. That is deliberate: absence of a disclosure is itself a finding, and dressing it up as knowledge would be the exact failure mode we are trying to help readers avoid.

Editorial standards

Every specific claim is attributed
Fees, limits, product availability and specifications are sourced to the official documentation they came from, with a note that they change. We deliberately avoid reproducing exact percentages that will go stale — a wrong number on a review page is worse than no number.
Downsides get equal space
Every review includes what we would tell a friend not to do. Our pros-and-cons component is built so the cons column is never shorter than the pros column, and that is an editorial rule rather than a design accident.
No hype, no urgency, no price talk
We do not use countdown framing, we do not describe any asset as an opportunity, and we do not publish predictions. If a page reads like it wants you to hurry, we have failed.
Security advice is conservative by default
Where a safer option costs a little more or takes a little longer, we recommend the safer option and explain the trade so you can decide otherwise.
Pages are dated and re-reviewed
Each page carries a last-reviewed date. This industry changes fast enough that an undated crypto guide is close to worthless.

How the site is funded

Affiliate commission. Some outbound links on this site are partner links, and if you open an account through one we may receive a commission at no additional cost to you. Every such link is marked rel="nofollow" and opens in a new tab, and every block containing one says so.

What that funding model does not buy:

  • It does not buy a verdict. Scores are set before any partner link is placed.
  • It does not buy silence. Our funding guides argue against card purchases, which are the highest-converting flow available to us.
  • It does not buy placement. We do not accept payment for coverage, ratings or mentions, from anyone.
  • It does not buy your data. We do not sell reader data — see the privacy section below, which is short because there is little to describe.

We would rather state the incentive plainly than pretend it does not exist. If you would prefer not to contribute to it, navigate to any platform directly. Nothing on this site is gated, and nothing changes if you do.

Corrections policy

We get things wrong. When we do, we want to know quickly, and we would rather hear it from a reader than from a search engine.

  1. Email contact@bitmartexchange.app with the page URL and the specific claim.
  2. Include a source where possible — a link to official documentation makes verification immediate.
  3. We verify against primary sources rather than taking either side on assertion.
  4. Substantive corrections are made and the review date updated. We do not silently rewrite a claim that materially misled readers; the change is reflected in the page's dating.

This applies to platforms too. If BitMart or any other operator believes something here is inaccurate, the same address works, and we will correct anything demonstrably wrong.

Privacy and data

This is a static site. There are no accounts, no logins, no comment system and no forms that collect personal data. We do not set advertising cookies, we do not run third-party trackers, and we do not build reader profiles.

Outbound partner links may set their own cookies on the destination site once you arrive there — that is how affiliate attribution works, and it is governed by that site's own privacy policy rather than ours. Email you send us is used only to answer you.

Full terms are on the Terms of Use page. Questions go to Contact.

The research itself. Every page stands on its own.