Skip to main content
AVOID.NET
← A7A5 Stablecoin / Old Vectorreviewed 2026-10-27 · 9 claims checked

Fact-check findings

What an automated fact-checker found when it re-read A7A5 Stablecoin / Old Vector against the sources the page cites. Only the most recent review is shown.

Read this first

These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.

“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.

Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.

disputed

1 claim

The reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.

  1. #1[disputed][awaiting moderator]in section: Sanctions Designations
    “The United Kingdom designated A7 and Old Vector on May 26, 2025 as part of a broader package targeting 18 entities including HTX/Huobi, citing A7A5's role in Russian sanctions evasion.”
    reviewerThe UK designated A7 and Old Vector in a package of 18 including HTX/Huobi on May 26, 2025The 18-target HTX package is dated May 26, 2026, not 2025. The page elsewhere uses 2026 (sections[3]). Old Vector is not named in the CoinGeek article; the page's own section 3 lists it from other reporting.
    Proposed correction (not yet applied)
    The United Kingdom designated A7 and Old Vector on May 26, 2026 as part of a broader package targeting 18 entities including HTX/Huobi, citing A7A5's role in Russian sanctions evasion.

unverifiable

1 claim

No source the reviewer could reach confirms or contradicts the claim.

  1. #9[unverifiable][awaiting moderator]in section: Sanctions Designations
    “The European Union included A7A5, its developer, Old Vector, and primary trading venue Grinex in its 19th Russia sanctions package adopted October 23, 2025”
    reviewerEU 19th package adopted October 23, 2025 including A7A5, Old Vector and GrinexCouncil page blocked. The adoption date is consistent with the page's own date_evidence and secondary sources, but I did not independently read it. Not scored.

partially supported

3 claims

The cited evidence supports part of the claim but not all of it.

  1. #2[partially supported][awaiting moderator]in section: Compliance Risk for Exchanges and Financial Institutions
    “Under OFAC's August 2025 designation, A7A5 tokens are treated as blocked property and any US-person transaction involving them is prohibited.”
    reviewerOFAC's August 2025 designation makes A7A5 tokens blocked propertySections[2] hedges this as 'according to one account'; this sentence states it flatly. The Treasury release only supports blocking of the designated entities' property.
  2. #3[partially supported][awaiting moderator]in section: UK Sanctions Package of May 2026 and HTX Dispute
    “Foreign Secretary Yvette Cooper was quoted: "The UK is adapting and strengthening our approach to target the evolving tactics Russia is using to evade restrictions."”
    reviewerYvette Cooper quote about the UK adapting its approachQuote not confirmed at the cited GOV.UK page. The $90 billion quote and 26 May 2026 date on the same page are confirmed. No correction proposed because the quote may come from a different official release.
  3. #4[partially supported][awaiting moderator]in section: Regulatory and Industry Response; Counter-Sanctioning of Critics
    “On June 4, 2026, Russia's Foreign Ministry announced sanctions against Alexander Browder, a 17-year-old British researcher and founder of the Global Cryptocurrency Laundering Database, along with four other British nationals, banning them from entering Russia.”
    reviewerRussia sanctioned Browder and four other British nationals; dated June 3 in one place and June 4 in anotherThe same section gives June 3 in its first paragraph and June 4 in its second. The exact date and the count of other nationals are not settled by the fetched source, so no edit is proposed.

confirmed

4 claims

The cited evidence supports the claim as written.

  1. #5[confirmed][no action needed]in the timeline
    “OFAC designates Old Vector, A7 LLC, A71, A7 Agent, Grinex, Sergey Mendeleev, Aleksandr Mira Serda, Pavel Karavatsky, InDeFi Bank and Exved under E.O. 13694; Garantex re-designated under cyber authorities.”
    reviewerOFAC designated Old Vector, A7, A71, A7 Agent, Grinex, Mendeleev, Mira Serda, Karavatsky, InDeFi Bank and Exved on August 14, 2025 under E.O. 13694Matches the Treasury release.
  2. #6[confirmed][no action needed]in section: Connection to Garantex and Grinex
    “OFAC first designated Garantex in April 2022 for processing over $100 million in illicit transactions linked to ransomware actors”
    reviewerOFAC first designated Garantex in April 2022; over $26 million frozen in March 2025Date confirmed. The $100 million and ransomware details were not independently checked.
  3. #7[confirmed][no action needed]in section: Post-Sanctions Collapse in Usage
    “According to Elliptic, A7A5 transaction volumes fell approximately 96% from their July 2025 peak, dropping to roughly $24.3 million by June 2026, and no new tokens were minted after July 23, 2025, indicating collapsing demand.”
    reviewerA7A5 volumes fell about 96% from the July 2025 peak to about $24.3 million by June 2026; no new tokens minted after July 23, 2025Elliptic frames $24.3 million as an average daily volume low; the page's wording is compatible.
  4. #8[confirmed][no action needed]in section: Post-Sanctions Collapse in Usage
    “on April 16, 2026, Grinex disclosed a security breach in which more than 1 billion rubles were reportedly stolen”
    reviewerGrinex disclosed a breach on April 16, 2026 with more than 1 billion rubles stolen; Uniswap removed A7A5 in November 2025Confirmed.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.