Skip to main content
AVOID.NET
← SIR.tradingreviewed 2026-11-01 · 8 claims checked

Fact-check findings

What an automated fact-checker found when it re-read SIR.trading 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.

unverifiable 2partially supported 1confirmed 50 corrections pending · 0 applied

unverifiable

2 claims

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

  1. #7[unverifiable][awaiting moderator]in the timeline
    “2025-09”
    reviewerRelaunch happened in September 2025The page itself admits the month is unsourced. The body text (sections[6]) correctly says the date is unverified, so the timeline is stronger than the prose; the precise month should be removed or hedged.
  2. #8[unverifiable][awaiting moderator]in the timeline
    “SIR.trading contacts Railgun directly seeking help to trace or recover the stolen funds.”
    reviewerSIR.trading contacted Railgun directly in April 2025Entry has no source or source_url; I found no source stating the team contacted Railgun, nor the April date. Note the sections[4] text also asserts this with sources I did not confirm.

partially supported

1 claim

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

  1. #5[partially supported][awaiting moderator]in section: Community Reaction
    “community observers noted this as a possible social-engineering precursor, but no causal link to the exploit has been established.”
    reviewerFounder had been contacted by a suspicious job candidate with a North Korean operative story; no causal link establishedThe anecdote exists but is the founder's own account; attribution to 'community observers' was not found in the fetched source.

confirmed

5 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in the timeline
    “On February 20, 2025, SIR.trading launches on Ethereum mainnet, growing organically, without advertising, to approximately $355,000–$400,000 TVL.”
    reviewerSIR.trading launched on Ethereum mainnet on February 20, 2025Launch date and TVL range are supported by Rekt.
  2. #2[confirmed][no action needed]in section: March 2025 Exploit: Transient Storage Vulnerability
    “On March 30, 2025, 39 days after mainnet launch, an attacker drained the protocol's entire TVL of approximately $355,000 in USDC, wBTC and wETH from SIR's Vault contract.”
    reviewerAttacker drained about $355,000 on March 30, 2025 and routed funds through RailgunFeb 20 to Mar 30 is 38 days by simple subtraction (39 counting inclusively); trivial. Core facts confirmed.
  3. #3[confirmed][no action needed]in section: Fund Laundering and Recovery Attempts
    “On March 31, 2025, Xatarrer published an on-chain message to the attacker offering $100,000 (approximately 28% of the stolen amount) as a bounty for discovering the vulnerability, requesting return of the remaining approximately $255,000 and pledging no legal action”
    reviewerFounder offered $100,000 bounty (about 28%) for return of about $255,000 with no legal action, on March 31, 2025Supported. The legal pledge is slightly informal ('No legal games') but fairly characterized.
  4. #4[confirmed][no action needed]in section: Audit History and Security Limitations
    “We raised around $70k from folks in here which allowed us to do 1 audit which unfortunately wasn't enough.”
    reviewerFounder said a single audit funded by about $70k was not enoughRekt confirms. Note that the $70k is described as funding the audit; the page also says it financed four years of development, which is a looser reading.
  5. #6[confirmed][no action needed]in section: Relaunch and Current Status
    “According to the protocol's documentation, the rebuilt version underwent four independent security audits before returning to production”
    reviewerThe relaunch followed four audits and expanded to HyperEVM and MegaETHSelf-reported by the protocol and appropriately attributed. No independent audit-firm confirmation found.
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.