← Moby Trade5 decisions on this page
Audit log
Every state-changing event for Moby Trade: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.
- #1publishby system:backfill2026-05-28 02:27:02ZScore: ? → ? (no score change)anchoranchored
- chain
- ●mainnet-betaslot 422,629,082
- sig
2tAkwKJAyagD…HyZj6saZexplorer ↗- hash
wpTyQpAonPdw…Rn1wmGpPsha256 → base58
verifying row…full verify ↗canonical bytes (5440 B) ▸
{"actor":"system:backfill","investigation_id":"da9d222b-c63f-4a4a-be45-63f5cbdde79c","kind":"publish","page_slug":"moby","published_at":"2026-05-28T02:27:02.629Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Moby Trade","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.halborn.com/blog/post/explained-the-moby-trade-hack-january-2025","type":"other","url":""},{"credibility":3,"name":"https://rekt.news/mobytrade-rekt","type":"other","url":""},{"credibility":3,"name":"https://medium.com/moby-trade/moby-post-mortem-report-growth-plan-504ad5b0dd35","type":"other","url":""},{"credibility":3,"name":"https://revoke.cash/exploits/moby","type":"other","url":""},{"credibility":3,"name":"https://www.merklescience.com/blog/hack-track-moby-flow-of-funds-analysis","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.merklescience.com/blog/hack-track-moby-flow-of-funds-analysis","type":"other","url":""},{"credibility":3,"name":"https://rekt.news/mobytrade-rekt","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://medium.com/moby-trade/moby-post-mortem-report-growth-plan-504ad5b0dd35","type":"other","url":""},{"credibility":3,"name":"https://revoke.cash/exploits/moby","type":"other","url":""},{"credibility":3,"name":"https://www.halborn.com/blog/post/explained-the-moby-trade-hack-january-2025","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.prnewswire.com/news-releases/moby-the-next-on-chain-options-protocol-receives-grant-from-arbitrum-foundation-302042108.html","type":"other","url":""},{"credibility":3,"name":"https://www.prnewswire.com/news-releases/moby-the-next-on-chain-options-protocol-mainnet-launch-302120855.html","type":"other","url":""},{"credibility":3,"name":"https://chainwire.org/2025/02/17/moby-a-leading-options-protocol-expands-to-berachain-mainnet/","type":"other","url":""},{"credibility":3,"name":"https://medium.com/moby-trade/moby-an-on-chain-options-protocol-receives-grant-funding-from-arbitrum-foundation-350f350ff314","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.merklescience.com/blog/hack-track-moby-flow-of-funds-analysis","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://revoke.cash/exploits/moby","type":"other","url":""},{"credibility":3,"name":"https://www.merklescience.com/blog/hack-track-moby-flow-of-funds-analysis","type":"other","url":""},{"credibility":3,"name":"https://www.halborn.com/blog/post/explained-the-moby-trade-hack-january-2025","type":"other","url":""}]}],"sources_used":[],"summary":"Moby Trade (moby.trade) is an on-chain options protocol built on Arbitrum and Berachain, launched in 2024 and backed by an Arbitrum Foundation grant. On January 8, 2025, the protocol suffered a critical security breach when a private key controlling proxy admin contracts was compromised, resulting in approximately $2.5 million in user funds being drained; roughly $1.5 million was subsequently recovered through an intervention by the SEAL911 security team. The protocol resumed operations after the incident and expanded to Berachain mainnet in February 2025, but the unrecovered ~$1 million in ETH and WBTC was routed through privacy mixers including Railgun and Tornado Cash, leaving those funds effectively unrecoverable.","timeline":[{"date":"2024-01-23","event":"Moby receives Arbitrum Foundation grant, becoming the first on-chain options protocol to receive such a grant prior to mainnet launch.","source":""},{"date":"2024-04-08","event":"Moby Trade launches on Arbitrum mainnet.","source":""},{"date":"2024-09-27","event":"Attacker's funding address withdraws 0.9706 ETH from Tornado Cash, later identified as pre-attack infrastructure preparation.","source":""},{"date":"2025-01-08","event":"Private key compromise: attacker tests exploit on Arbitrum Sepolia at 11:56 UTC, executes malicious contract upgrade on mainnet at 12:53 UTC, and drains S_VAULT and M_VAULT between 15:24 and 16:48 UTC, stealing approximately $2.47 million in wETH, wBTC, and USDC.","source":""},{"date":"2025-01-08","event":"SEAL911 and MEV researcher Tony Ke recover approximately $1.47 million USDC by exploiting an unprotected upgrade function in the attacker's own malicious contract, finishing 30 seconds behind the attacker.","source":""},{"date":"2025-01-08","event":"Remaining stolen ETH and WBTC begin dispersal across 35+ wallet addresses; 9.5634 ETH routed through Railgun privacy protocol.","source":""},{"date":"2025-01-10","event":"Moby Trade publishes incident report; users urged to revoke token approvals. Protocol operations suspended.","source":""},{"date":"2025-01-13","event":"Target date for initial compensation payments to affected options holders.","source":""},{"date":"2025-01-15","event":"Protocol operations resume with enhanced security measures including key separation and multi-step verification.","source":""},{"date":"2025-02-17","event":"Moby Trade expands to Berachain mainnet, integrating with Berachain's Proof of Liquidity mechanism. Moby is selected for Berachain's Request for Application program.","source":""}]},"v":1}Verify offline (run on your own machine)python -m src.verify_decision b38377c5-44ff-46b1-a764-b9eba055e8b8 - #2rescoreby systemsystem2026-10-10 18:47:37ZScore: 38 → 55 (+17)Rescored under Scoring v2, the published formula (avoid.net/scoring): 38 → 55. Problems weighed by who is responsible: incidents the subject suffered −6.4, concerns that are not fraud −3.2, problems around the subject, caused by others −2.4; legitimacy credit long-running +2.anchoranchored
- chain
- ●mainnet-betaslot 455,367,483
- sig
4owJNV6hmJha…Rkb4VC52explorer ↗- hash
61vG8bdHryG2…H1HBU7Njsha256 → base58
verifying row…full verify ↗canonical bytes (635 B) ▸
{"actor":"system","decided_at":"2026-10-10T18:47:37.446Z","decision":"rescore","investigation_id":"da9d222b-c63f-4a4a-be45-63f5cbdde79c","new_score":55,"page_slug":"moby","prev_score":38,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 38 → 55. Problems weighed by who is responsible: incidents the subject suffered −6.4, concerns that are not fraud −3.2, problems around the subject, caused by others −2.4; legitimacy credit long-running +2.","score_delta":17,"score_model":"v2","sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision ff0f4fdf-ce5c-476a-b18e-f6237226b7cd - #3reviewby reviewerreviewer2026-11-02 03:25:50ZScore: 55 → 55 (no score change)The core incident (Jan 8, 2025 private-key compromise, ~$2.5M gross loss, ~$1.47M USDC recovered via SEAL911/Tony Ke, ~$1M net loss) holds up against Rekt, Halborn and Merkle Science. Defects found: the section 1 loss total ($2.47M) does not match the listed figures (about $1.0M), the 35+ wallet figure is contradicted by Merkle (more than ten), the summary overstates the Tornado Cash/Railgun routing, and the Solayer/Fuzzland affiliation is unsupported. Incident times, compensation dates and security measures rest on a Medium post-mortem that returned 403. Current status after Feb 2025 is unverified.anchoranchored
- chain
- ●mainnet-betaslot 464,343,422
- sig
FUvg5yuE8x3D…g5tvW4Zaexplorer ↗- hash
4Bb87uNjb3Nc…iwVipqLqsha256 → base58
verifying row…full verify ↗canonical bytes (1482 B) ▸
{"actor":"reviewer","artifact_identity":"187b0f5b6d5fe3e65cec9483639a6c23","blocked_count":3,"decided_at":"2026-11-02T03:25:50.816Z","decision":"review","disputed_pct":0.5,"findings_hash":"A25irVP3SA6VwafuTxmg3XSBBjob9km6ShpUAM8f4jpt","investigation_id":"da9d222b-c63f-4a4a-be45-63f5cbdde79c","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":55,"omissions":{"material":0,"total":1},"page_content_hash":"6ab240274b669197a1e5e1c44b2b18f0fa26d8c01156800d246d60ec50c52cbe","page_slug":"moby","prev_score":55,"reason":"The core incident (Jan 8, 2025 private-key compromise, ~$2.5M gross loss, ~$1.47M USDC recovered via SEAL911/Tony Ke, ~$1M net loss) holds up against Rekt, Halborn and Merkle Science. Defects found: the section 1 loss total ($2.47M) does not match the listed figures (about $1.0M), the 35+ wallet figure is contradicted by Merkle (more than ten), the summary overstates the Tornado Cash/Railgun routing, and the Solayer/Fuzzland affiliation is unsupported. Incident times, compensation dates and security measures rest on a Medium post-mortem that returned 403. Current status after Feb 2025 is unverified.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":10,"sequence_num":3,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 2edc53a3-6057-4ccc-80fe-c514f5b20fb2 - #4review reviseby judgejudge2026-11-02 03:25:51ZScore: 55 → 55 (no score change)Of 13 claim findings, 3 could not be checked because the source blocked the reviewer and were left out; of the remaining 10, 5 were disputed or unverifiable (50%), which falls in the significant-issues band. The core incident (January 2025 private-key compromise, about $2.5M gross loss, about $1.47M recovered) holds up, but the page's loss total does not match its own listed figures (claim_findings[0]), the 35+ wallet count is contradicted by the cited source in two places (claim_findings[3], [4]), and the summary overstates Tornado Cash and Railgun routing (claim_findings[7]). The page also gives no evidence of operating status after February 2025, which is a high-priority coverage gap, and the primary post-mortem could not be read; the penalty is kept in the middle of the band because the central allegation is sound and these are mostly correctable figures.anchoranchored
- chain
- ●mainnet-betaslot 464,343,427
- sig
5aTfqRTiHAYr…sNuZtQmMexplorer ↗- hash
E2FUdTxXo8aE…Pnc3XSDDsha256 → base58
verifying row…full verify ↗canonical bytes (1543 B) ▸
{"actor":"judge","artifact_identity":"187b0f5b6d5fe3e65cec9483639a6c23","band_override":null,"blocked_count":3,"decided_at":"2026-11-02T03:25:50.816Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5,"investigation_id":"da9d222b-c63f-4a4a-be45-63f5cbdde79c","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":55,"page_slug":"moby","prev_score":55,"reason":"Of 13 claim findings, 3 could not be checked because the source blocked the reviewer and were left out; of the remaining 10, 5 were disputed or unverifiable (50%), which falls in the significant-issues band. The core incident (January 2025 private-key compromise, about $2.5M gross loss, about $1.47M recovered) holds up, but the page's loss total does not match its own listed figures (claim_findings[0]), the 35+ wallet count is contradicted by the cited source in two places (claim_findings[3], [4]), and the summary overstates Tornado Cash and Railgun routing (claim_findings[7]). The page also gives no evidence of operating status after February 2025, which is a high-priority coverage gap, and the primary post-mortem could not be read; the penalty is kept in the middle of the band because the central allegation is sound and these are mostly correctable figures.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":10,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 4a28f7b2-8fce-45eb-81d8-37fb9a7f6a99 - #5rescoreby systemsystem2026-11-02 03:25:52ZScore: 55 → 60 (+5)Recalculated after the fact-check of 2026-11-02. Rescored under Scoring v2, the published formula (avoid.net/scoring): 55 → 60. Problems weighed by who is responsible: incidents the subject suffered −3.2, concerns that are not fraud −3.2, problems around the subject, caused by others −0.8; legitimacy credit long-running +2; 3 section(s) set aside until a failed fact-check is resolved.anchoranchored
- chain
- ●mainnet-betaslot 464,343,432
- sig
5GECF4KTy54o…7qw3dqpVexplorer ↗- hash
J1U3JuVjoPze…yFq6EzoCsha256 → base58
verifying row…full verify ↗canonical bytes (745 B) ▸
{"actor":"system","decided_at":"2026-11-02T03:25:50.816Z","decision":"rescore","investigation_id":"da9d222b-c63f-4a4a-be45-63f5cbdde79c","new_score":60,"page_slug":"moby","prev_score":55,"reason":"Recalculated after the fact-check of 2026-11-02. Rescored under Scoring v2, the published formula (avoid.net/scoring): 55 → 60. Problems weighed by who is responsible: incidents the subject suffered −3.2, concerns that are not fraud −3.2, problems around the subject, caused by others −0.8; legitimacy credit long-running +2; 3 section(s) set aside until a failed fact-check is resolved.","score_delta":5,"score_model":"v2","sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 84f2e7cc-6a94-488d-9732-4665bab17137
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine —
python -m src.verify_decision <event_id>.