Bitgetpublishes the proofVerifelsechecks it, independently

Verify your Bitget inclusion

Your browser recomputes the Merkle root from Bitget's open-source scheme and compares it against the root Verifelse recorded, confirming your balances were in the audited tree.

Snapshots Verifelse can verify

Your proof file must come from one of these Bitget audits. Each root was recorded from Bitget's published audit list, independently of your file.

LatestOct 21, 2026

Audit Au2026102112

Recorded root

1ef42111598bd71b

11 earlier snapshots
  • Sep 29, 2026Au202609291715893cf0dae1c552
  • Sep 15, 2026Au2026091600d393340f79f3a3d0
  • Aug 20, 2026Au2026082022d1822a31506cba59
  • Jul 20, 2026Au202607201752e1101cc3b46fe4
  • Jun 15, 2026Au2026061516cfc25f847a6bdb0e
  • May 20, 2026Au2026052008893d00af9b9ea454
  • Apr 17, 2026Au202604171043dbe928ec778c5d
  • Mar 17, 2026Au2026031714cfa672fa5f02bf4c
  • Feb 10, 2026Au20260210140f7a747e9d0de947
  • Jan 20, 2026Au202601210700795643f17d7588
  • Dec 14, 2025Au20251215067a9b97198947c5b8
  1. Provide the proof Bitget gave you

How your privacy is protected

  • Verification runs entirely in your browser. Your proof, balances, and account id are never sent to Verifelse.
  • We record only a one-way salted commitment of your leaf, so an inclusion is counted once without revealing the account.
  • Confirms inclusion in the published tree. It is not, by itself, proof of Bitget's solvency.