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

Audit log

Every state-changing event for Unibot: 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-30 11:48:06Z
    Score: ? → ? (no score change)
    anchoranchored
    chain
    ●mainnet-betaslot 423,150,316
    sig
    4fuNFvLSVqhN…c6sWqUXgexplorer ↗
    hash
    KxBUCRpZpaid…et8Cp43Msha256 → base58
    verifying row…full verify ↗
    canonical bytes (7805 B) ▸
    {"actor":"system:backfill","investigation_id":"5908d54b-dd44-42e9-b102-da2fe84998b1","kind":"publish","page_slug":"unibot","published_at":"2026-05-30T11:48:06.786Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Unibot","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.iconomi.com/blog/what-is-unibot","type":"other","url":""},{"credibility":3,"name":"https://crypto.com/us/university/what-is-unibot","type":"other","url":""},{"credibility":3,"name":"https://learn.unibot.app/faq/revenue-sharing","type":"other","url":""},{"credibility":3,"name":"https://beincrypto.com/learn/unibot-guide/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.coindesk.com/markets/2023/10/31/unibot-token-hurtles-25-as-telegram-bot-exploited-for-630k","type":"other","url":""},{"credibility":3,"name":"https://cointelegraph.com/news/unibot-contract-560-k-exploit-crashes-token-price-40","type":"other","url":""},{"credibility":3,"name":"https://thecryptobasic.com/2023/10/31/unibot-suffers-560k-exploit-users-endure-more-pain-as-token-dumps-33/","type":"other","url":""},{"credibility":3,"name":"https://revoke.cash/exploits/unibot","type":"other","url":""},{"credibility":3,"name":"https://www.certik.com/resources/blog/1Zh5XbaDstXKteFcRSmOcp-maestro-and-unibot","type":"other","url":""},{"credibility":3,"name":"https://rivanorth.com/blog/unibot-hack","type":"other","url":""},{"credibility":3,"name":"https://finance.yahoo.com/news/unibot-token-price-crashes-30-073233496.html","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.cryptotimes.io/2023/11/04/unibot-reimburses-users-following-recent-security-hack/","type":"other","url":""},{"credibility":3,"name":"https://chainbulletin.com/unibot-to-compensate-users-affected-by-exploit","type":"other","url":""},{"credibility":3,"name":"https://cryptopotato.com/unibot-fully-compensates-users-following-hacking-incident/","type":"other","url":""},{"credibility":3,"name":"https://www.coindesk.com/markets/2023/10/31/unibot-token-hurtles-25-as-telegram-bot-exploited-for-630k","type":"other","url":""},{"credibility":3,"name":"https://revoke.cash/exploits/unibot","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.dlnews.com/articles/defi/unibot-telegram-bot-unveils-cloud-service-for-private-keys/","type":"other","url":""},{"credibility":3,"name":"https://cointelegraph.com/news/should-telegram-trading-bots-be-trusted","type":"other","url":""},{"credibility":3,"name":"https://www.certik.com/resources/blog/1Zh5XbaDstXKteFcRSmOcp-maestro-and-unibot","type":"other","url":""},{"credibility":3,"name":"https://www.iconomi.com/blog/what-is-unibot","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.dlnews.com/articles/defi/unibot-devs-tussle-as-ethereum-team-splits-from-solana-group/","type":"other","url":""},{"credibility":3,"name":"https://www.coindesk.com/markets/2024/03/11/unibot-tanks-33-after-ending-collaboration-with-solana-group","type":"other","url":""},{"credibility":3,"name":"https://crypto.news/unibot-collapse-solana-termination/","type":"other","url":""},{"credibility":3,"name":"https://www.odaily.news/en/post/5188638","type":"other","url":""},{"credibility":3,"name":"https://fullycrypto.com/unibot-dumps-solana-over-unauthorized-bot-launch","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.coingecko.com/en/coins/unibot","type":"other","url":""},{"credibility":3,"name":"https://coinmarketcap.com/currencies/unibot-eth/","type":"other","url":""},{"credibility":3,"name":"https://coinpedia.org/guest-post/unibot-dives-as-bitbot-gears-up-to-become-next-big-crypto-of-2024/","type":"other","url":""},{"credibility":3,"name":"https://medium.com/@DeMan01/unibot-alternative-can-banana-gun-sustain-its-recent-impressive-data-performance-in-the-near-term-211dadc3112b","type":"other","url":""},{"credibility":3,"name":"https://www.linkedin.com/pulse/banana-guns-users-surpass-both-unibot-maestro-theblockcrypto","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.odaily.news/en/post/5188638","type":"other","url":""},{"credibility":3,"name":"https://www.dlnews.com/articles/defi/unibot-devs-tussle-as-ethereum-team-splits-from-solana-group/","type":"other","url":""},{"credibility":3,"name":"https://learn.unibot.app/faq/revenue-sharing","type":"other","url":""},{"credibility":3,"name":"https://medium.com/coinmonks/things-to-consider-before-venturing-into-unibot-3d878819d547","type":"other","url":""}]}],"sources_used":[],"summary":"Unibot is a Telegram-based trading bot launched in May 2023 that enabled users to execute Uniswap trades directly within Telegram. On October 31, 2023, a newly deployed router contract containing a call injection vulnerability was exploited, draining approximately $560,000–$640,000 in user funds that were subsequently laundered through Tornado Cash; the team ultimately reimbursed affected users at a reported cost of $1.78 million. A second crisis followed in March 2024 when the Ethereum and Solana development teams publicly split amid mutual accusations of unauthorized deployments and revenue misappropriation, causing the token to shed an additional 40% of its value and reducing the project to a fraction of its former user base.","timeline":[{"date":"2023-05-17","event":"Unibot launches on Ethereum mainnet with 1,000,000 UNIBOT tokens in a claimed fair launch with no presale or team allocation.","source":""},{"date":"2023-08-16","event":"UNIBOT token reaches its all-time high of approximately $236–$238, with the project reporting a growing user base and significant trading volume.","source":""},{"date":"2023-10-28","event":"Unibot deploys a new router contract on Ethereum. The contract is not verified on Etherscan at the time of deployment.","source":""},{"date":"2023-10-31","event":"A call injection vulnerability in the new router contract is exploited. Approximately $560,000–$640,000 in user funds is drained. Scopescan publicly discloses the ongoing attack. The team pauses the router. UNIBOT token falls 25–42% within hours. Stolen ETH (approximately 355.5 ETH) is subsequently laundered through Tornado Cash.","source":""},{"date":"2023-11-02","event":"Unibot resumes trading operations after pausing the compromised router contract.","source":""},{"date":"2023-11-04","event":"Unibot reports full reimbursement of approximately 600 affected users, disclosing the compensation effort cost approximately $1.78 million. Zero trading fees and increased revenue share announced as additional remediation.","source":""},{"date":"2024-03-11","event":"Unibot's Ethereum and Solana development teams publicly announce the end of their collaboration. Ethereum team accuses Solana team of unauthorized Blast deployment, KYC refusal, and fee violations. Solana team (Reethmos) counter-accuses Ethereum developers of tax farming extraction and engineering the split. UNIBOT token falls over 40%, losing approximately $40 million in market cap.","source":""},{"date":"2024-03-11","event":"Ethereum team launches 'Unisol X' as an alternative Solana frontend; Solana team continues operating under the original 'Unibot on Solana' branding.","source":""},{"date":"2025-01-01","event":"UNIBOT token trading at approximately $1–$4, down approximately 98–99% from its August 2023 all-time high. Daily active users reported at approximately 600, down from a peak of 32,000.","source":""}]},"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision c3cfd390-3ced-45d2-8d39-3b500c55a3d3
  2. #2reviewby reviewerreviewer
    2026-08-18 21:01:32Z
    Score: 42 → 42 (no score change)
    The page's core narrative -- a May 2023 Telegram trading bot that suffered a ~$560-640K router-contract exploit on Oct 31, 2023 (fully reimbursed at $1.78M cost to the team), followed by a March 2024 acrimonious split between its Ethereum and Solana dev factions -- is well-corroborated by multiple independent, credible sources and no link rot was found in spot checks. The one material defect found is the timeline's '32,000 peak daily active users' figure, which is contradicted by every source located (independent reporting places Unibot's DAU all-time high at 3,151-4,730, an order of magnitude lower); this inflates the apparent scale of the project's subsequent collapse and should be corrected or sourced. No unhedged criminal allegations were found: the exploit is consistently and correctly framed as something Unibot suffered (a victim of an external attacker), not something Unibot's team perpetrated, and the March 2024 dev-team dispute is presented as competing, unadjudicated accusations between two factions rather than as established fact.
    anchoranchored
    chain
    ●mainnet-betaslot 443,508,868
    sig
    34vddGEBGUXT…pYYGuSuGexplorer ↗
    hash
    Gubtz88BSug6…JgWSiHPGsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1399 B) ▸
    {"actor":"reviewer","decided_at":"2026-08-18T21:01:31.896Z","decision":"review","investigation_id":"5908d54b-dd44-42e9-b102-da2fe84998b1","new_score":42,"page_slug":"unibot","prev_score":42,"reason":"The page's core narrative -- a May 2023 Telegram trading bot that suffered a ~$560-640K router-contract exploit on Oct 31, 2023 (fully reimbursed at $1.78M cost to the team), followed by a March 2024 acrimonious split between its Ethereum and Solana dev factions -- is well-corroborated by multiple independent, credible sources and no link rot was found in spot checks. The one material defect found is the timeline's '32,000 peak daily active users' figure, which is contradicted by every source located (independent reporting places Unibot's DAU all-time high at 3,151-4,730, an order of magnitude lower); this inflates the apparent scale of the project's subsequent collapse and should be corrected or sourced. No unhedged criminal allegations were found: the exploit is consistently and correctly framed as something Unibot suffered (a victim of an external attacker), not something Unibot's team perpetrated, and the March 2024 dev-team dispute is presented as competing, unadjudicated accusations between two factions rather than as established fact.","score_delta":0,"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 e3db1122-fef0-401a-9b5f-ca473fde47f1
  3. #3review reviseby judgejudge
    2026-08-18 21:01:32Z
    Score: 42 → 58 (+16)
    Content accuracy holds up well -- 7 of 10 claims confirmed outright, disputed_pct is only 0.1, and no unhedged criminal allegations were found (claim_findings[7] correctly frames the March 2024 dev split as a mutual, unresolved dispute rather than adjudicated fraud). The score is the problem: the page's own rubric (calibration.scoring_instruction) states that 'suffered' incidents cap an entity at CAUTIONARY (50-69), yet the current score of 42 sits in WARNING, which per that same rubric implies own-conduct fraud or negligence. Both major incidents -- the October 2023 router exploit (calibration_assessment.incident_attributions[0], attribution 'b': external attacker, fully reimbursed at $1.78M) and the March 2024 dev-team split (incident_attributions[1], attribution 'c': mutual unresolved accusations between two pseudonymous factions) -- are suffered/third-party events, not own-fraud. The current WARNING score conflates being hacked and having an internal governance dispute with entity misconduct, which the evidence does not support; 58 (upper-CAUTIONARY) better reflects a project that responded responsibly to victimization but still carries real, unresolved governance and staleness risk. Notes: (Correct or source the timeline[8] '32,000 peak daily active users' figure -- no source located supports it, and independent reporting places Unibot's DAU all-time high at 3,151-4,730, roughly an order of magnitude lower (claim_findings[9]).) (Adjust timeline[7] to reflect that Unisol X launched March 14, 2024, three days after the March 11 split announcement, rather than compressing both into the same date (claim_findings[8]).)
    anchoranchored
    chain
    ●mainnet-betaslot 443,508,870
    sig
    5yyC1j6k5nbq…V3hpvaWYexplorer ↗
    hash
    BheeKn5cGhTS…nNj4iqsesha256 → base58
    verifying row…full verify ↗
    canonical bytes (1993 B) ▸
    {"actor":"judge","decided_at":"2026-08-18T21:01:31.896Z","decision":"review_revise","investigation_id":"5908d54b-dd44-42e9-b102-da2fe84998b1","new_score":58,"page_slug":"unibot","prev_score":42,"reason":"Content accuracy holds up well -- 7 of 10 claims confirmed outright, disputed_pct is only 0.1, and no unhedged criminal allegations were found (claim_findings[7] correctly frames the March 2024 dev split as a mutual, unresolved dispute rather than adjudicated fraud). The score is the problem: the page's own rubric (calibration.scoring_instruction) states that 'suffered' incidents cap an entity at CAUTIONARY (50-69), yet the current score of 42 sits in WARNING, which per that same rubric implies own-conduct fraud or negligence. Both major incidents -- the October 2023 router exploit (calibration_assessment.incident_attributions[0], attribution 'b': external attacker, fully reimbursed at $1.78M) and the March 2024 dev-team split (incident_attributions[1], attribution 'c': mutual unresolved accusations between two pseudonymous factions) -- are suffered/third-party events, not own-fraud. The current WARNING score conflates being hacked and having an internal governance dispute with entity misconduct, which the evidence does not support; 58 (upper-CAUTIONARY) better reflects a project that responded responsibly to victimization but still carries real, unresolved governance and staleness risk. Notes: (Correct or source the timeline[8] '32,000 peak daily active users' figure -- no source located supports it, and independent reporting places Unibot's DAU all-time high at 3,151-4,730, roughly an order of magnitude lower (claim_findings[9]).) (Adjust timeline[7] to reflect that Unisol X launched March 14, 2024, three days after the March 11 split announcement, rather than compressing both into the same date (claim_findings[8]).)","score_delta":16,"sequence_num":3,"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 ee507895-1aeb-4161-a675-1d525e13d647
  4. #4reviewby reviewerreviewer
    2026-09-09 03:05:33Z
    Score: 48 → 48 (no score change)
    Findings-only fact-check (retroactive anchor of stored findings)
    anchoranchored
    chain
    ●mainnet-betaslot 445,508,509
    sig
    S13vJXZEmCcw…bUsGQ68rexplorer ↗
    hash
    8T7WVS4qMz39…NbPXyaXosha256 → base58
    verifying row…full verify ↗
    canonical bytes (699 B) ▸
    {"actor":"reviewer","artifact_identity":"ed67db9e7a989422343e72f22bf8abc1","decided_at":"2026-09-07T05:45:37.582831+00:00","decision":"review","findings_count":22,"findings_rows_hash":"771f87f5caf54df57eea52b6a8bedb1860b976b56cb7a8848ef749f6a19de8d9","investigation_id":"5908d54b-dd44-42e9-b102-da2fe84998b1","mode":"findings_only_retroactive","new_score":48,"page_content_hash":"83bc428633f2353b4c284380996aa5e721c37ffff393977e8a9be7d5e34f8699","page_slug":"unibot","prev_score":48,"reason":"Findings-only fact-check (retroactive anchor of stored findings)","score_delta":0,"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 0dcdb162-da94-4e70-87c8-fa4228b1e8df
  5. #5reviewby reviewerreviewer
    2026-10-27 11:03:38Z
    Score: 48 → 48 (no score change)
    The core claims I checked are supported by Decrypt and CoinDesk: exploit date and amount, the price drop, the peak price and the Solana termination. The 355.5 ETH figure, the Oct 28 router deployment, the 86% and $370k reimbursement figures and the August 2026 market data could not be confirmed. I found no omitted shutdown, sanction or second exploit. Only a small sample of claims was checked.
    anchoranchored
    chain
    ●mainnet-betaslot 462,046,659
    sig
    2ufwiK1xVXSH…v44rjEoAexplorer ↗
    hash
    5VQFtEPbXUbL…4a7zDSEhsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1241 B) ▸
    {"actor":"reviewer","artifact_identity":"1d8ba56b16bd7edfe4459732c3aaa977","blocked_count":1,"decided_at":"2026-10-27T11:03:38.039Z","decision":"review","disputed_pct":0.1667,"findings_hash":"FFgrkoHaqNdfTLcngjNuKLsrA4qJHDZMKJeXN8QqehNp","investigation_id":"5908d54b-dd44-42e9-b102-da2fe84998b1","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":48,"page_content_hash":"83bc428633f2353b4c284380996aa5e721c37ffff393977e8a9be7d5e34f8699","page_slug":"unibot","prev_score":48,"reason":"The core claims I checked are supported by Decrypt and CoinDesk: exploit date and amount, the price drop, the peak price and the Solana termination. The 355.5 ETH figure, the Oct 28 router deployment, the 86% and $370k reimbursement figures and the August 2026 market data could not be confirmed. I found no omitted shutdown, sanction or second exploit. Only a small sample of claims was checked.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"sequence_num":5,"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 33d63f43-6d11-4f20-8692-fcb9253aa623
  6. #6review reviseby judgejudge
    2026-10-27 11:03:38Z
    Score: 48 → 43 (-5)
    The core claims hold up: the October 31, 2023 exploit date and amount, the price drop, the 2023 peak and the March 2024 Solana termination were confirmed by Decrypt and CoinDesk (claim_findings[0], [1], [4], [5]). One of six scored claims could not be confirmed, the 355.5 ETH figure and October 28 router deployment date (claim_findings[2]), and the August 2026 market figures were only partly supported (claim_findings[6]), giving about 17% unverified. The 86% and $370,000 reimbursement claim was excluded because its source blocked the reviewer (claim_findings[3]); that limits coverage but does not count against the page. No shutdown, sanction or omission was found, and the reviewer's confidence was low (0.5), so the penalty is kept at the bottom of the minor band.
    anchoranchored
    chain
    ●mainnet-betaslot 462,046,664
    sig
    2nTuAuYSDsWJ…X7qLQmxNexplorer ↗
    hash
    bN9N28g6GgKx…QLiArNjvsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1450 B) ▸
    {"actor":"judge","artifact_identity":"1d8ba56b16bd7edfe4459732c3aaa977","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T11:03:38.039Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1667,"investigation_id":"5908d54b-dd44-42e9-b102-da2fe84998b1","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":43,"page_slug":"unibot","prev_score":48,"reason":"The core claims hold up: the October 31, 2023 exploit date and amount, the price drop, the 2023 peak and the March 2024 Solana termination were confirmed by Decrypt and CoinDesk (claim_findings[0], [1], [4], [5]). One of six scored claims could not be confirmed, the 355.5 ETH figure and October 28 router deployment date (claim_findings[2]), and the August 2026 market figures were only partly supported (claim_findings[6]), giving about 17% unverified. The 86% and $370,000 reimbursement claim was excluded because its source blocked the reviewer (claim_findings[3]); that limits coverage but does not count against the page. No shutdown, sanction or omission was found, and the reviewer's confidence was low (0.5), so the penalty is kept at the bottom of the minor band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-5,"scored_claims":6,"sequence_num":6,"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 f71e98b1-0cd3-4e15-8b73-a9a0bbca699d
  7. #7rescoreby systemsystem
    2026-11-01 12:37:12Z
    Score: 43 → 73 (+30)
    Rescored under Scoring v2, the published formula (avoid.net/scoring): 43 → 73. Problems weighed by who is responsible: concerns that are not fraud −6.4, problems around the subject, caused by others −1.7; legitimacy credit long-running +6; 1 section(s) set aside until a failed fact-check is resolved; fact-check adjustments (+11) now shown as page reliability, not in the score.
    anchoranchored
    chain
    ●mainnet-betaslot 464,094,863
    sig
    4DSLg8L6LXJ3…4bvgDx9Fexplorer ↗
    hash
    5VAENEvQFAyo…fyQ5U3Q8sha256 → base58
    verifying row…full verify ↗
    canonical bytes (740 B) ▸
    {"actor":"system","decided_at":"2026-11-01T12:37:12.740Z","decision":"rescore","investigation_id":"5908d54b-dd44-42e9-b102-da2fe84998b1","new_score":73,"page_slug":"unibot","prev_score":43,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 43 → 73. Problems weighed by who is responsible: concerns that are not fraud −6.4, problems around the subject, caused by others −1.7; legitimacy credit long-running +6; 1 section(s) set aside until a failed fact-check is resolved; fact-check adjustments (+11) now shown as page reliability, not in the score.","score_delta":30,"score_model":"v2","sequence_num":7,"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 ebb65f3b-ad87-4b29-8bbc-dd6240dd7a8d
  8. #8rescoreby systemsystem
    2026-11-03 18:00:20Z
    Score: 73 → 65 (-8)
    Re-read and rescored after the page was re-researched (2026-11-03). Rescored under Scoring v2, the published formula (avoid.net/scoring): 73 → 65. Problems weighed by who is responsible: incidents the subject suffered −6, concerns that are not fraud −3.2, problems around the subject, caused by others −1.1.
    anchoranchored
    chain
    ●mainnet-betaslot 464,991,763
    sig
    Zc9rs2mzSYiC…HosVQr5Vexplorer ↗
    hash
    ATvvAZcpU9YV…6cQd8ZqUsha256 → base58
    verifying row…full verify ↗
    canonical bytes (668 B) ▸
    {"actor":"system","decided_at":"2026-11-03T18:00:19.870Z","decision":"rescore","investigation_id":"5908d54b-dd44-42e9-b102-da2fe84998b1","new_score":65,"page_slug":"unibot","prev_score":73,"reason":"Re-read and rescored after the page was re-researched (2026-11-03). Rescored under Scoring v2, the published formula (avoid.net/scoring): 73 → 65. Problems weighed by who is responsible: incidents the subject suffered −6, concerns that are not fraud −3.2, problems around the subject, caused by others −1.1.","score_delta":-8,"score_model":"v2","sequence_num":8,"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 1c7a1a25-86ab-49e2-b330-620c4ac09ea8
  9. #9reviewby reviewerreviewer
    2026-11-03 18:01:25Z
    Score: 65 → 65 (no score change)
    Core exploit facts (Oct 31, 2023 date, about $560K-$640K loss, compensation pledge) and the cryptonews reimbursement figures check out. The reimbursement section wrongly attributes Cointelegraph's 334 ETH and 610 ETH figures, and the 'funded from Maestro's revenue' framing, to Unibot. Those figures belong to Maestrobots, a separate bot. Unibot's own reported cost was about $1.78M. The 25-32% price drop range omits the 40%+ figure in the cited Cointelegraph article. The March 2024 and token price sections were only partly checked because of time and a fetch failure. No current-status contradiction was found.
    anchoranchored
    chain
    ●mainnet-betaslot 464,992,053
    sig
    2bm39tY1ZtYu…Wrr5uq3Pexplorer ↗
    hash
    4QyKMZqvfru1…KULTWFT3sha256 → base58
    verifying row…full verify ↗
    canonical bytes (1459 B) ▸
    {"actor":"reviewer","artifact_identity":"ac5d8a98402c799efe54f024c3298892","blocked_count":2,"decided_at":"2026-11-03T18:01:25.175Z","decision":"review","disputed_pct":0.1429,"findings_hash":"9RfhmFbopvRoFWh3pgZVLkdrXXucAcH94diwu15cCATN","investigation_id":"5908d54b-dd44-42e9-b102-da2fe84998b1","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":65,"page_content_hash":"85174713e04d825e8182fda1db58a0731cc68c29d535affe029fecb3ff2a606e","page_slug":"unibot","prev_score":65,"reason":"Core exploit facts (Oct 31, 2023 date, about $560K-$640K loss, compensation pledge) and the cryptonews reimbursement figures check out. The reimbursement section wrongly attributes Cointelegraph's 334 ETH and 610 ETH figures, and the 'funded from Maestro's revenue' framing, to Unibot. Those figures belong to Maestrobots, a separate bot. Unibot's own reported cost was about $1.78M. The 25-32% price drop range omits the 40%+ figure in the cited Cointelegraph article. The March 2024 and token price sections were only partly checked because of time and a fetch failure. No current-status contradiction was found.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"scored_claims":7,"sequence_num":9,"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 5fe4a30c-7d85-4064-b560-83fd7be69866
  10. #10review reviseby judgejudge
    2026-11-03 18:01:25Z
    Score: 65 → 65 (no score change)
    Of 7 checkable claims, 1 was disputed (about 14%), which falls in the minor-issues band. claim_findings[0] shows the page attributes the 334 ETH, 20% boost and 610 ETH compensation figures, and the 'funded from Maestro's revenue' framing, to Unibot, when the cited Cointelegraph article attributes them to a separate bot, Maestrobots; Unibot's own reported payout cost was about $1.78M. Two further claims were only partly supported (the 25-32% price drop omits the 42.7% in the cited Cointelegraph article, and the router deployment date conflicts between outlets). The core exploit facts, the loss range and the reimbursement figures were confirmed, and no omission or status contradiction was found. Two of nine findings (about 22%) could not be checked because sources were blocked or not fetched, which limits coverage and is not a defect of the page.
    anchoranchored
    chain
    ●mainnet-betaslot 464,992,059
    sig
    5ZcxWrKYozo4…57qQHctRexplorer ↗
    hash
    4MH6cnFparDu…u7Us8fxSsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1533 B) ▸
    {"actor":"judge","artifact_identity":"ac5d8a98402c799efe54f024c3298892","band_override":null,"blocked_count":2,"decided_at":"2026-11-03T18:01:25.175Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1429,"investigation_id":"5908d54b-dd44-42e9-b102-da2fe84998b1","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":65,"page_slug":"unibot","prev_score":65,"reason":"Of 7 checkable claims, 1 was disputed (about 14%), which falls in the minor-issues band. claim_findings[0] shows the page attributes the 334 ETH, 20% boost and 610 ETH compensation figures, and the 'funded from Maestro's revenue' framing, to Unibot, when the cited Cointelegraph article attributes them to a separate bot, Maestrobots; Unibot's own reported payout cost was about $1.78M. Two further claims were only partly supported (the 25-32% price drop omits the 42.7% in the cited Cointelegraph article, and the router deployment date conflicts between outlets). The core exploit facts, the loss range and the reimbursement figures were confirmed, and no omission or status contradiction was found. Two of nine findings (about 22%) could not be checked because sources were blocked or not fetched, which limits coverage and is not a defect of the page.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"scored_claims":7,"sequence_num":10,"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 898d0edb-fc06-4f20-9c43-94f758675834
  11. #11rescoreby systemsystem
    2026-11-03 18:01:26Z
    Score: 65 → 66 (+1)
    Recalculated after the fact-check of 2026-11-03. Rescored under Scoring v2, the published formula (avoid.net/scoring): 65 → 66. Problems weighed by who is responsible: incidents the subject suffered −6, concerns that are not fraud −3.2, problems around the subject, caused by others −0.3; 1 section(s) set aside until a failed fact-check is resolved.
    anchoranchored
    chain
    ●mainnet-betaslot 464,992,064
    sig
    usdwyga6cWLR…3AHEHdwtexplorer ↗
    hash
    74gPSWFhoAwg…3pvXBgYBsha256 → base58
    verifying row…full verify ↗
    canonical bytes (711 B) ▸
    {"actor":"system","decided_at":"2026-11-03T18:01:25.175Z","decision":"rescore","investigation_id":"5908d54b-dd44-42e9-b102-da2fe84998b1","new_score":66,"page_slug":"unibot","prev_score":65,"reason":"Recalculated after the fact-check of 2026-11-03. Rescored under Scoring v2, the published formula (avoid.net/scoring): 65 → 66. Problems weighed by who is responsible: incidents the subject suffered −6, concerns that are not fraud −3.2, problems around the subject, caused by others −0.3; 1 section(s) set aside until a failed fact-check is resolved.","score_delta":1,"score_model":"v2","sequence_num":11,"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 0fa57222-39c3-49bb-824e-1ccb9de45715
  12. #12rescoreby systemsystem
    2026-11-17 21:35:12Z
    Score: 66 → 65 (-1)
    Re-read and rescored after the page was re-researched (2026-11-17). Rescored under Scoring v2, the published formula (avoid.net/scoring): 66 → 65. Problems weighed by who is responsible: incidents the subject suffered −6, concerns that are not fraud −3.2, problems around the subject, caused by others −1.1.
    anchoranchored
    chain
    ●mainnet-betaslot 470,686,225
    sig
    5GZmoZGHy6sq…nrq1xZdFexplorer ↗
    hash
    Cik9St7LUxAE…k8paFYDpsha256 → base58
    verifying row…full verify ↗
    canonical bytes (669 B) ▸
    {"actor":"system","decided_at":"2026-11-17T21:35:11.636Z","decision":"rescore","investigation_id":"5908d54b-dd44-42e9-b102-da2fe84998b1","new_score":65,"page_slug":"unibot","prev_score":66,"reason":"Re-read and rescored after the page was re-researched (2026-11-17). Rescored under Scoring v2, the published formula (avoid.net/scoring): 66 → 65. Problems weighed by who is responsible: incidents the subject suffered −6, concerns that are not fraud −3.2, problems around the subject, caused by others −1.1.","score_delta":-1,"score_model":"v2","sequence_num":12,"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 e7f273e2-4e64-4237-a707-7223b6d3e73d
  13. #13reviewby reviewerreviewer
    2026-11-17 21:36:13Z
    Score: 65 → 65 (no score change)
    The claims I checked against Revoke.cash, Cointelegraph, cryptonews.net, ChainCatcher and CoinGecko were accurately reported, and the page appropriately hedges discrepant loss figures and low-confidence reimbursement data. No errors found. The CoinDesk, The Block, Blockworks and the two Solana-split articles (blockchain.news, crypto.news) were not opened, so claims resting only on them are unchecked. No shutdown or other status change was found.
    anchoranchored
    chain
    ●mainnet-betaslot 470,686,530
    sig
    2gFwT9ixjqPi…sntR8jZkexplorer ↗
    hash
    J8ZpnVKYgFYM…H6w7CGA4sha256 → base58
    verifying row…full verify ↗
    canonical bytes (1254 B) ▸
    {"actor":"reviewer","artifact_identity":"29ae663d7db59a7387355e066faecaba","decided_at":"2026-11-17T21:36:13.491Z","decision":"review","disputed_pct":0,"findings_hash":"5JupF1FD5nuhPYNzpujtUAKy8s1ykTyo2THpayZngAJV","investigation_id":"5908d54b-dd44-42e9-b102-da2fe84998b1","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":65,"page_content_hash":"2da1653c473c5b01f21a3428573550833a9fc9243bf7b0aaf5a4a90e912d4523","page_slug":"unibot","prev_score":65,"reason":"The claims I checked against Revoke.cash, Cointelegraph, cryptonews.net, ChainCatcher and CoinGecko were accurately reported, and the page appropriately hedges discrepant loss figures and low-confidence reimbursement data. No errors found. The CoinDesk, The Block, Blockworks and the two Solana-split articles (blockchain.news, crypto.news) were not opened, so claims resting only on them are unchecked. No shutdown or other status change was found.","reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":0,"sequence_num":13,"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 af28b3e7-04f3-45b5-be5b-5001355f2cea
  14. #14review approveby judgejudge
    2026-11-17 21:36:13Z
    Score: 65 → 65 (no score change)
    All six checked claims (claim_findings[0] to [5]) were confirmed against Revoke.cash, Cointelegraph, cryptonews.net, ChainCatcher and CoinGecko, giving a disputed share of 0% with no unverifiable findings. The review found no omissions and no shutdown, exploit or sanction the page fails to mention (subject_status.contradicts_page is false). Open coverage gaps are medium or low priority: reimbursement figures rest on a single tier-3 outlet, and several CoinDesk, Blockworks, The Block and Solana-split sources were not opened. These suggest expansion rather than a penalty.
    anchoranchored
    chain
    ●mainnet-betaslot 470,686,537
    sig
    64T4WtoT9oWp…njhKmC7Vexplorer ↗
    hash
    CTcxhZu3b6mK…rxgHLkRvsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1213 B) ▸
    {"actor":"judge","artifact_identity":"29ae663d7db59a7387355e066faecaba","band_override":null,"decided_at":"2026-11-17T21:36:13.491Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"5908d54b-dd44-42e9-b102-da2fe84998b1","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":65,"page_slug":"unibot","prev_score":65,"reason":"All six checked claims (claim_findings[0] to [5]) were confirmed against Revoke.cash, Cointelegraph, cryptonews.net, ChainCatcher and CoinGecko, giving a disputed share of 0% with no unverifiable findings. The review found no omissions and no shutdown, exploit or sanction the page fails to mention (subject_status.contradicts_page is false). Open coverage gaps are medium or low priority: reimbursement figures rest on a single tier-3 outlet, and several CoinDesk, Blockworks, The Block and Solana-split sources were not opened. These suggest expansion rather than a penalty.","reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":0,"sequence_num":14,"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 cc3d9c1e-0602-4c18-bd9b-e1434dbdec2a
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>.