Version history
Every immutable snapshot of NEAR Intents. A new version is saved each time the page changes, with the reason it changed. Pick two versions to see exactly what changed.
- v7currentTrust score: 342026-11-03 22:35:29Z
Community evidenceA moderator accepted a piece of community-submitted evidence: Crypto Briefing confirms about $3.865M USDT lost on BSC around 30 Sep/1 Oct 2026 via an Omni bug, 11 networks paused, and full return within 24 hours. Mixed evidence, neutral label fits. Trust score now 34.
hash: 5rV3BmxsdyU9…changes from v6 - v6Trust score: 352026-10-30 23:43:41Z
Community evidenceA moderator accepted a piece of community-submitted evidence: Crypto Briefing states the root cause was a bug in how Omni deposit/withdrawal infrastructure interacted with smart contracts, funds traced to KuCoin and converted to Bitcoin, and a 48-hour return window was set. Matches the note. Trust score now 35.
hash: 6kXnKyRzYAfu…changes from v5 - v5Trust score: 382026-10-30 23:43:40Z
Community evidenceA moderator accepted a piece of community-submitted evidence: CoinDesk, Oct 1, 2026, reports the $3.8M NEAR Intents exploit from a bug in Omni deposit/withdrawal interaction with its smart contract, and ZachXBT tracing BNB Chain hot wallet funds to KuCoin then Bitcoin. Matches the note. Trust score now 38.
hash: GqDQzMyMtnFF…changes from v4 - v4Trust score: 402026-10-30 19:44:17Z
Community evidenceA moderator accepted a piece of community-submitted evidence: Protos (Oct 1, 2026) reports the ~$3.8M NEAR Intents Omni exploit with outflows from the BNB Chain hot wallet, days after it froze Bitget-linked funds. Matches the note. Trust score now 40.
hash: 6RMYjFo8w3p4…changes from v3 - v3Trust score: 412026-10-27 11:20:19Z
Fact-check reviewFact-check review (verdict: revise): the reviewer checked the page's claims against its sources; the trust score did not change.
hash: b9dbd04b7044…changes from v2 - v2Trust score: 412026-10-27 06:05:55Z
Score recalculatedRescored under Scoring v2, the published formula (avoid.net/scoring): 38 → 41. Problems weighed by who is responsible: incidents the subject suffered −19.2, concerns that are not fraud −6, problems around the subject, caused by others −1.9; legitimacy credit long-running +6; a recent unresolved incident −12.9.
hash: b9dbd04b7044…changes from v1 - v1Trust score: 382026-10-27 06:05:55Z
Before rewriteThe page as it stood just before its Scoring v2 rescore; the next version says why.
hash: 6bbf93bc518b…