Fact-check findings
What an automated fact-checker found when it re-read Syscoin Bridge 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.
disputed
1 claimThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #1[disputed][awaiting moderator]in section: Market Impact
“Cryptopolitan reported that, months after the incident, SYS was trading near $0.0026”
reviewerCryptopolitan's report on SYS price and market cap was made months after the incident.The figures are accurate, but the article dates from about ten days after the exploit, not months after.Proposed correction (not yet applied)Cryptopolitan reported that, shortly after the incident (June 17, 2026), SYS was trading near $0.0026
unverifiable
1 claimNo source the reviewer could reach confirms or contradicts the claim.
- #8[unverifiable][awaiting moderator]in section: Historical Background: 2014 Crowdsale Escrow Dispute
“Binance Futures and Margin pairs were closed on May 19, 2026, and spot trading ended on May 27, 2026.”
reviewerBinance closed Futures and Margin pairs on May 19, 2026, ended spot on May 27, and SYS fell as much as 33.77%.The BeInCrypto source was blocked. Rekt's timing is consistent with the May 27 date, but the May 19 date and the 33.77% figure could not be checked.
partially supported
2 claimsThe cited evidence supports part of the claim but not all of it.
- #2[partially supported][awaiting moderator]in the summary
“a May 2026 Binance delisting that preceded the bridge incident by about two weeks”
reviewerThe Binance delisting preceded the bridge incident by about two weeks.The summary says two weeks while section 7 and Rekt say eleven days. The page is internally inconsistent. - #9[partially supported][awaiting moderator]in section: Bridge Status and Remediation
“A UK High Court injunction ordered Moopay Ltd and Green/Kennedy to return the 750 BTC to Syscoin's developers”
reviewerA UK High Court injunction ordered Moopay/Green-Kennedy to return the 750 BTC to Syscoin's developers.The substance holds. The CoinDesk URL did not fetch directly, and the source name 'Reach Agreement' does not match the injunction content. The sources_used entry typed 'court_filing' is a news article.
confirmed
5 claimsThe cited evidence supports the claim as written.
- #3[confirmed][no action needed]in section: Incident Overview: June 2026 Bridge Exploit
“Estimates of the minted tokens' value at the time of the exploit range from about $8.5 million to $10 million across sources.”
reviewerRoughly 5 billion unauthorized SYS were minted, worth about $8.5-10 million.The range matches Rekt ($8.56M) and Halborn ($10M). Syscoin's postmortem describes the 5 billion SYS as 'released' from the vault, while the other outlets say 'minted'. This is a wording difference only. - #4[confirmed][no action needed]in section: Technical Root Cause
“a malicious UTXO burn transaction included two conflicting asset commitments targeting the same output index”
reviewerThe root cause was two conflicting asset commitments (assetGuid 123456 and 4/TEST2) interpreted differently by Syscoin Core and the NEVM relay.The postmortem matches. Halborn's parsing-error framing also matches. - #5[confirmed][no action needed]in section: Incident Response and Recovery
“Syscoin published a fuller technical postmortem on June 15, 2026, detailing the root cause and remediation steps.”
reviewerThe exploit occurred on June 7, 2026 and the fuller postmortem was published June 15, 2026.Both dates match the official postmortem. - #6[confirmed][no action needed]in section: Attack Execution and Fund Movement
“with approximately 4 billion SYS in one address and approximately 1 billion SYS in the other”
reviewerFunds were split about 4 billion and 1 billion SYS across two wallets, and a recovery address was posted June 9.Matches Rekt. - #7[confirmed][no action needed]in section: Incident Response and Recovery
“On or around June 10, 2026, Syscoin told exchanges it was safe to reopen native SYS deposits and withdrawals”
reviewerSyscoin told exchanges on June 10 that native SYS deposits and withdrawals were safe to reopen, and the bridge remains paused.Matches. The bridge-paused statement matches the postmortem, and I found no later reopening report.