Version history
Every immutable snapshot of Payy Network. A new version is saved each time the page changes, with the reason it changed. Pick two versions to see exactly what changed.
- v13currentTrust score: 322026-11-04 00:49:01Z
Fact-check reviewFact-check review (verdict: approve): the reviewer checked the page's claims against its sources; the trust score did not change.
hash: c785c52ddd6d…changes from v12 - v12Trust score: 322026-11-04 00:47:55Z
Score recalculatedRe-read and rescored after the page was re-researched (2026-11-04). Rescored under Scoring v2, the published formula (avoid.net/scoring): 42 → 32. Problems weighed by who is responsible: incidents the subject suffered −16, problems around the subject, caused by others −1.5; a recent unresolved incident −18.8; accepted community evidence −3.4.
hash: c785c52ddd6d…changes from v11 - v11Trust score: 422026-11-04 00:25:47Z
Re-researchedRe-researched in full by the investigator agent at a reader's request; the text was rewritten from new research.
hash: d153dd02082a…changes from v10 - v10Trust score: 422026-11-04 00:25:47Z
Before rewriteThe page as it stood just before it was rewritten; the next version says why.
hash: b12ff213d54d…changes from v9 - v9Trust score: 422026-11-03 23:14:54Z
Community evidenceA moderator accepted a piece of community-submitted evidence: The Defiant headline and subtitle report a $1.92M USDC drain from Payy and paused deposits, withdrawals and card payments, as the note says. Trust score now 42.
hash: 8zVX6oZQohtZ…changes from v8 - v8Trust score: 442026-11-03 22:35:30Z
Community evidenceA moderator accepted a piece of community-submitted evidence: Unchained confirms Payy's Ethereum bridge lost about $1.92M USDC on 24 Sept 2026, network and wallet paused, and Payy's initial analysis ruled out key compromise, social engineering and off-chain exploit. Trust score now 44.
hash: AujaGbLmTZEc…changes from v7 - v7Trust score: 452026-11-02 14:47:46Z
Fact-check reviewFact-check review (verdict: revise): the reviewer checked the page's claims against its sources; the trust score did not change.
hash: 9bd3d072da0b…changes from v6 - v6Trust score: 452026-11-02 14:46:12Z
Score recalculatedRe-read and rescored after the page was re-researched (2026-11-02). Rescored under Scoring v2, the published formula (avoid.net/scoring): 26 → 45. Problems weighed by who is responsible: incidents the subject suffered −10, concerns that are not fraud −6, problems around the subject, caused by others −1.8; a recent unresolved incident −11.7.
hash: 9bd3d072da0b…changes from v5 - v5Trust score: 262026-11-02 12:33:48Z
Re-researchedRe-researched in full by the investigator agent at a reader's request; the text was rewritten from new research.
hash: 9cc9145d53c4…changes from v4 - v4Trust score: 262026-11-02 12:33:48Z
Before rewriteThe page as it stood just before it was rewritten; the next version says why.
hash: 98e12cc3fd58…changes from v3 - v3Trust score: 262026-11-01 12:37:28Z
Score recalculatedRescored under Scoring v2, the published formula (avoid.net/scoring): 26 → 26. Problems weighed by who is responsible: incidents the subject suffered −20, the subject's own conduct −3; legitimacy credit long-running +2; no established finding that it defrauded anyone, so it stays out of the red band; the penalty for incidents it suffered is capped at 20; a recent unresolved incident −31.7; 1 section(s) set aside until a failed fact-check is resolved; fact-check adjustments (−2) now shown as page reliability, not in the score.
hash: 62155fc9b48b…changes from v2 - v2Trust score: 262026-10-27 07:08:25Z
Fact-check reviewFact-check review (verdict: revise): the reviewer checked the page's claims against its sources; the judge moved the trust score from 28 to 26.
hash: d79da8c2f0a9…changes from v1 - v1Trust score: 222026-09-25 17:06:29Z
No reason was recorded for this version (saved before October 2026).
hash: 2aa0aa0e3cfc…