Fact-check findings
What an automated fact-checker found when it re-read Syscoin against the sources the page cites. Only the most recent review is shown.
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
4 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #10[unverifiable][awaiting moderator]in the timeline
“London High Court orders Moopay (Moolah parent) to return 750 BTC to Syscoin developers by 16:00 GMT.”
reviewerCourt ordered Moopay to return 750 BTC on 2014-10-28Source returned 403, so the date and deadline could not be checked. - #11[unverifiable][awaiting moderator]in section: 2014 ICO Fund Theft (Ryan Kennedy / Moolah)
“Kennedy was subsequently convicted and incarcerated in the United Kingdom.”
reviewerKennedy convicted and incarcerated in the UKThe cited articles describe the arrest; I did not retrieve a source for conviction or incarceration. Not rechecked beyond the cited arrest article. - #12[unverifiable][awaiting moderator]in section: 2024 Governance Allegations and Dutch Criminal Investigation
“A criminal complaint was lodged with the Functional Public Prosecutor's Office in the Netherlands on July 26, 2024.”
reviewerDutch complaint filed July 26, 2024; hearing Sept 26, 2024Not fetched within this review's time budget; 2024 governance claims are neither confirmed nor contradicted. The page appropriately labels them allegations. - #13[unverifiable][awaiting moderator]in section: Exchange Listings and Delistings
“Binance announced the delisting of SYS and nine other tokens from all margin trading products, effective January 30, 2026.”
reviewerBinance delisted SYS from margin products effective 2026-01-30Not checked against a Binance announcement.
partially supported
6 claimsThe cited evidence supports part of the claim but not all of it.
- #3[partially supported][awaiting moderator]in section: June 2026 Bridge Exploit
“SYS experienced a price decline of approximately 40% from $0.0022 in the days following public disclosure.”
reviewerSYS fell ~40% from $0.0022 in the days following public disclosureRekt places a ~43% weekly decline before the attack. The page attributes the drop to post-disclosure. The CryptoTimes article was not fetched, so the correct framing is not established. - #4[partially supported][awaiting moderator]in the timeline
“Public disclosure of exploit widely reported; SYS price drops approximately 40% from $0.0022; exchanges contacted to freeze tainted deposits.”
reviewerTimeline June 8: price drops ~40% after disclosureSame issue as the section claim; a single-day timing is not supported by sources I read. - #5[partially supported][awaiting moderator]in section: June 2026 Bridge Exploit
“The attacker returned all 5 billion SYS tokens to a designated recovery address via two on-chain transactions on June 10–11, 2026.”
reviewerAttacker returned all 5B SYS in two transactions on June 10-11Return and two transactions are confirmed; the specific June 10-11 dates were not found in the sources I read (may be on-chain). - #6[partially supported][awaiting moderator]in the timeline
“Syscoin publicly announces completion of recovered token burn via OP_RETURN transaction, restoring pre-exploit circulating supply. Bridge remains offline pending final security audit.”
reviewerRecovery/burn publicly announced June 18, 2026Burn was documented in the official postmortem dated June 15 and reported June 17, so a June 18 announcement date looks wrong. Also the sources say the bridge awaits 'final review/validation', not specifically a 'security audit'. No correction proposed because the exact announcement date was not pinned down. - #7[partially supported][awaiting moderator]in section: June 2026 Bridge Exploit
“Security firm Rekt News noted that no public third-party audit record exists for the bridge relay path itself, despite other Syscoin ecosystem components having been audited.”
reviewerNo public third-party audit record exists for the bridge relay pathSubstance confirmed; the 'Security firm' label is an overstatement. - #9[partially supported][awaiting moderator]in section: June 2026 Bridge Exploit
“The bridge remained offline as of late June 2026 pending final security audit.”
reviewerBridge remained offline pending security auditBridge paused is confirmed; 'security audit' is a slightly stronger description than 'final review'.
confirmed
3 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: June 2026 Bridge Exploit
“At the time of the exploit, the tokens were valued at approximately $8.56 million based on a SYS closing price of roughly $0.00171.”
reviewerExploit on June 7, 2026 minted ~5 billion SYS, valued ~$8.56M at a closing price of ~$0.00171Matches Rekt News. - #2[confirmed][no action needed]in section: June 2026 Bridge Exploit
“The attacker's initial address was identified as sys1qgaelv690g7wwp2xchfdh0enf5uewzq5sm9wvcw, with proceeds subsequently split approximately 4 billion SYS to one wallet and 1 billion SYS to a second.”
reviewerAttacker address and 4B/1B splitConfirmed. - #8[confirmed][no action needed]in the timeline
“Syscoin releases full technical breakdown of the bridge vulnerability.”
reviewerTechnical breakdown released June 15, 2026Confirmed by the official postmortem (Halborn separately published an explainer around June 8).