Fact-check findings
What an automated fact-checker found when it re-read ArbiSwap 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
3 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #5[unverifiable][awaiting moderator]in section: Structural Red Flags and Scam Design
“Second, the 'recoverToken' backdoor function was embedded in a contract that was silently swapped approximately 13 hours before the rug was executed, indicating premeditation.”
reviewerThe contract was silently swapped about 13 hours before the rug, to address 0x5e7a... with a hidden recoverToken functionThe cited BeInCrypto page was blocked. CoinDesk and CryptoSlate do not contain this detail. Section 2 calls it the 'project's deployed smart contract' while the timeline calls it a 'router contract', which is inconsistent. - #6[unverifiable][awaiting moderator]in the timeline
“Approximately 13 hours before the rug pull, the developer silently swaps the project's router contract to a new address (0x5e7aBD428e2BE79af3317DbdF2BffC31BF7075cF) containing a hidden 'recoverToken' backdoor function.”
reviewerThe timeline attributes the contract swap to 2023-03 with date_original 2023-03-01Source blocked and no alternative found. The date field is imprecise (month only). - #8[unverifiable][awaiting moderator]in section: ZachXBT Flag and Community Intelligence
“The entity was flagged by blockchain investigator ZachXBT as part of his broader monitoring of Arbitrum ecosystem scams.”
reviewerZachXBT flagged ArbiSwap in his monitoringNo evidence of a ZachXBT flag; the section's own text undercuts it. The Wikipedia source cited is a general biography.citedt.me/investigations
partially supported
2 claimsThe cited evidence supports part of the claim but not all of it.
- #3[partially supported][awaiting moderator]in section: Rug Pull Mechanics
“the overlooked ARBI/WETH pool was subsequently drained by an independent arbitrage bot that captured roughly $112,000 in profit”
reviewerA separate arbitrage bot drained the ARBI/WETH pool and made about $112,000The $112k figure appears to be the deployer's own 68.47 ETH proceeds, not a separate bot's profit, so the page seems to double count. I could not find a fetched source for the ARBI/WETH bot story, so I propose no rewrite. - #7[partially supported][awaiting moderator]in section: Structural Red Flags and Scam Design
“The project is not believed to have any ongoing operations as of the date of this report.”
reviewerAftermath: no developer statement, restitution not offered, project has no ongoing operationsConsistent with DeFiLlama's deprecated listing. The hedged wording is appropriate. A user-generated Steemit post claims a 2025 relaunch; I could not confirm it and it may concern a different project (Arbswap).
confirmed
3 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: Overview and Launch
“ArbiSwap launched on February 24, 2023, positioning itself as a native decentralized exchange on the Arbitrum Layer 2 network.”
reviewerArbiSwap launched on Feb 24, 2023 and reached $1M TVL within 30 minutes, peaking around $4.4M on DeFiLlamaLaunch date and TVL figures are supported by CryptoSlate; CoinDesk corroborates month and $4.4M. - #2[confirmed][no action needed]in section: Rug Pull Mechanics
“The deployer netted approximately 68.47 ETH from the primary exploit”
reviewerThe deployer netted about 68.47 ETH via a 1 trillion token mint-dump (PeckShield)Supported. - #4[confirmed][no action needed]in section: On-Chain Footprint and Tornado Cash Usage
“The stolen ETH was subsequently routed through Tornado Cash, a privacy-mixing protocol, to obscure the destination of funds”
reviewerStolen ETH (about 84 ETH) was routed through Tornado CashSupported by CryptoSlate and a QuillAudits post found in search. CoinFomania and CoinDesk do not mention it, so the section's attribution to CoinFomania is overstated. Page does not state that 68.47 ETH and 84 ETH figures differ by source.