Skip to main content
AVOID.NET
← Bitrue4 decisions on this page

Audit log

Every state-changing event for Bitrue: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.

  1. #1publishby system:backfill
    2026-05-20 18:36:42Z
    Score: ? → ? (no score change)
    anchoranchored
    chain
    ●mainnet-betaslot 421,041,192
    sig
    fEhodEupMjY8…yJWeNW5Gexplorer ↗
    hash
    31umhcZkPpvK…ouA3WnGzsha256 → base58
    verifying row…full verify ↗
    canonical bytes (5026 B) ▸
    {"actor":"system:backfill","investigation_id":"43cef8ae-9c17-4fa8-aedc-da32e514e543","kind":"publish","page_slug":"bitrue","published_at":"2026-05-20T18:36:42.761Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Bitrue","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://iq.wiki/wiki/bitrue"},{"credibility":3,"name":"","type":"other","url":"https://www.cbinsights.com/company/bitrue/people"},{"credibility":3,"name":"","type":"other","url":"https://en.everybodywiki.com/Bitrue_Inc"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://www.coindesk.com/business/2023/04/14/crypto-exchange-bitrue-drained-of-23m-in-hack-of-ether-shiba-inu-other-tokens"},{"credibility":3,"name":"","type":"other","url":"https://cointelegraph.com/news/crypto-exchange-bitrue-suffers-23m-hack-due-to-hot-wallet-eploit"},{"credibility":3,"name":"","type":"other","url":"https://coinedition.com/bitrue-hack-wallet-launders-funds-tornado-cash/"},{"credibility":3,"name":"","type":"other","url":"https://coinedition.com/bitrue-hacker-tornado-cash-laundering-crypto-security-update/"},{"credibility":3,"name":"","type":"other","url":"https://www.tronweekly.com/bitrue-hacker-launders-23m-via-tornado-cash-nets-9-3m-profit-in-eth/"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://www.bitrue.com/blog/Bitrue-Secures-VASP-Registration-in-Lithuania"},{"credibility":3,"name":"","type":"other","url":"https://blockchainreporter.net/bitrue-gets-lithuanian-vasp-license-expanding-eu-digital-services/"},{"credibility":3,"name":"","type":"other","url":"https://coinjournal.net/news/bitrue-gets-virtual-asset-service-provider-approval-in-lithuania/"},{"credibility":3,"name":"","type":"other","url":"https://cexfinder.com/gemini-singapore-bitrue-lithuania-licenses/"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://beincrypto.com/xrp-forensics-calls-out-bitrue-for-shuttering-users/"},{"credibility":3,"name":"","type":"other","url":"https://github.com/ccxt/ccxt/issues/20613"},{"credibility":3,"name":"","type":"other","url":"https://www.ipetitions.com/petition/crypto-exchange-bitrue-is-stealing-money-from-its"},{"credibility":3,"name":"","type":"other","url":"https://www.trustpilot.com/review/www.bitrue.com"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://www.coindesk.com/business/2023/04/14/crypto-exchange-bitrue-drained-of-23m-in-hack-of-ether-shiba-inu-other-tokens"},{"credibility":3,"name":"","type":"other","url":"https://brokerchooser.com/safety/bitrue-broker-safe-or-scam"},{"credibility":3,"name":"","type":"other","url":"https://tradersunion.com/scam-or-safe/bitrue-review/"}]}],"sources_used":[],"summary":"Bitrue is a Singapore-incorporated centralized cryptocurrency exchange founded in 2018 that suffered a confirmed $23 million hot wallet exploit in April 2023, with stolen funds subsequently laundered through Tornado Cash as recently as June 2025. The exchange holds no license from Singapore's Monetary Authority (MAS) and relies on a VASP registration in Lithuania — a lower-tier regulatory framework — while accumulating a persistent record of user complaints alleging unjustified account freezes and asset seizures.","timeline":[{"date":"2018-07-01","event":"Bitrue founded in Singapore by Curis Wang and co-founders, initially supporting five cryptocurrencies with XRP focus.","source":""},{"date":"2021-02-12","event":"XRP Forensics publicly calls out Bitrue for freezing user accounts without clear justification; Bitrue cites arbitrage trading ban.","source":""},{"date":"2023-04-14","event":"Attacker exploits a Bitrue hot wallet at 07:18 UTC, draining approximately $23 million in ETH, QNT, GALA, SHIB, HOT, and MATIC. All withdrawals suspended.","source":""},{"date":"2023-04-18","event":"Bitrue restores withdrawal services after security review. Exchange states all affected users will be compensated in full.","source":""},{"date":"2023-12-01","event":"User alleges Bitrue seized $12,000 in assets citing a 'trading attack' involving automated scripts; case documented on GitHub.","source":""},{"date":"2024-03-01","event":"Previously dormant Bitrue hack wallet reactivates; attacker sells 4,207 ETH, generating approximately $16.3 million in DAI.","source":""},{"date":"2024-10-28","event":"Bitrue Lithuania UAB receives VASP registration from Lithuania's FNTT (registration 306725033), the exchange's first formal regulatory credential.","source":""},{"date":"2025-06-01","event":"On-chain analyst @EmberCN reports Bitrue hack wallet laundering approximately $12.65 million (4,600 ETH) through Tornado Cash in structured multi-stage operations. Total stolen proceeds estimated at $32.4 million after ETH appreciation.","source":""}]},"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 1c05e523-1376-4501-93a0-a9efb5314fb6
  2. #2rescoreby systemsystem
    2026-10-10 18:48:41Z
    Score: 18 → 71 (+53)
    Rescored under Scoring v2, the published formula (avoid.net/scoring): 18 → 71. Problems weighed by who is responsible: concerns that are not fraud −9.6, incidents the subject suffered −3.2, problems around the subject, caused by others −0.8; legitimacy credit long-running +10, regulated +10.
    anchoranchored
    chain
    ●mainnet-betaslot 455,368,605
    sig
    4S9nXKwMfbVV…ZdGefrGaexplorer ↗
    hash
    A8ujvPnWPEY5…YkdTpyjzsha256 → base58
    verifying row…full verify ↗
    canonical bytes (653 B) ▸
    {"actor":"system","decided_at":"2026-10-10T18:48:41.827Z","decision":"rescore","investigation_id":"43cef8ae-9c17-4fa8-aedc-da32e514e543","new_score":71,"page_slug":"bitrue","prev_score":18,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 18 → 71. Problems weighed by who is responsible: concerns that are not fraud −9.6, incidents the subject suffered −3.2, problems around the subject, caused by others −0.8; legitimacy credit long-running +10, regulated +10.","score_delta":53,"score_model":"v2","sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision dd9bd2e4-3ff6-4559-93ae-97d13d3f803c
  3. #3reviewby reviewerreviewer
    2026-10-27 18:49:04Z
    Score: 71 → 71 (no score change)
    The core hack facts (date, time, amount, tokens, compensation pledge) and the June 2025 laundering figures match the cited sources, and the Lithuanian FNTT registration matches Bitrue's own announcement. Items unchecked include the Singapore regulatory statement, MiCA transition, and 2021 XRP Forensics episode (source 403). One archive URL points to an unrelated article. No shutdown or sanction was found, so the page's status is consistent.
    anchoranchored
    chain
    ●mainnet-betaslot 462,177,981
    sig
    4f8bCpdYviV7…Vj5DHejDexplorer ↗
    hash
    3ycSaxcFTfEG…UFxJQzYwsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1288 B) ▸
    {"actor":"reviewer","artifact_identity":"7479c7e67e43a3ad5b9fc5d45d3c7e13","blocked_count":1,"decided_at":"2026-10-27T18:49:04.804Z","decision":"review","disputed_pct":0.375,"findings_hash":"4iHYGwp9royUz5HtrQi792Tg49CWFQb2BFXghQ1DJTbg","investigation_id":"43cef8ae-9c17-4fa8-aedc-da32e514e543","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":71,"page_content_hash":"9e12d2d2070bbbc9ae77f8ba4bb086ce0f2907547eb129cbaeb2758af375e7e7","page_slug":"bitrue","prev_score":71,"reason":"The core hack facts (date, time, amount, tokens, compensation pledge) and the June 2025 laundering figures match the cited sources, and the Lithuanian FNTT registration matches Bitrue's own announcement. Items unchecked include the Singapore regulatory statement, MiCA transition, and 2021 XRP Forensics episode (source 403). One archive URL points to an unrelated article. No shutdown or sanction was found, so the page's status is consistent.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 868183a3-fae2-446a-b538-b119c2e24bb1
  4. #4review reviseby judgejudge
    2026-10-27 18:49:05Z
    Score: 71 → 71 (no score change)
    Of 9 claim findings, 1 was excluded because its source blocked the reviewer (claim_findings[5]), and 3 of the remaining 8 (37.5%) could not be verified because no source was found: the 'first formal regulatory credential' timeline claim (claim_findings[4]), the Lithuanian MiCA transition (claim_findings[6]) and the Singapore regulatory statement (claim_findings[7]). The central allegations, the April 2023 hack and the June 2025 laundering figures, were confirmed against cited sources (claim_findings[0], [1]), and nothing was found to contradict the page. Because the unverified items are unsourced rather than disputed, the penalty is set at the low end of the band. Smaller issues are a loosely attributed gain (claim_findings[2]) and an archive link that points to an unrelated article (claim_findings[8]).
    anchoranchored
    chain
    ●mainnet-betaslot 462,177,986
    sig
    2yYKD6fhPD2t…ikfre3Doexplorer ↗
    hash
    3zkdyoLrYzji…GGS5JCEFsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1489 B) ▸
    {"actor":"judge","artifact_identity":"7479c7e67e43a3ad5b9fc5d45d3c7e13","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T18:49:04.804Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.375,"investigation_id":"43cef8ae-9c17-4fa8-aedc-da32e514e543","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":71,"page_slug":"bitrue","prev_score":71,"reason":"Of 9 claim findings, 1 was excluded because its source blocked the reviewer (claim_findings[5]), and 3 of the remaining 8 (37.5%) could not be verified because no source was found: the 'first formal regulatory credential' timeline claim (claim_findings[4]), the Lithuanian MiCA transition (claim_findings[6]) and the Singapore regulatory statement (claim_findings[7]). The central allegations, the April 2023 hack and the June 2025 laundering figures, were confirmed against cited sources (claim_findings[0], [1]), and nothing was found to contradict the page. Because the unverified items are unsourced rather than disputed, the penalty is set at the low end of the band. Smaller issues are a loosely attributed gain (claim_findings[2]) and an archive link that points to an unrelated article (claim_findings[8]).","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 6b05bc9c-6d27-4d09-9702-79b90ed2b89b
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine — python -m src.verify_decision <event_id>.