← Ramzinex17 decisions on this page
Audit log
Every state-changing event for Ramzinex: 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-06-04 17:15:53ZScore: ? → ? (no score change)anchoranchored
- chain
- ●mainnet-betaslot 424,286,896
- sig
5BfwehALSEaG…rc31YGooexplorer ↗- hash
6XiWfZiHFd5y…tBZR5b8rsha256 → base58
verifying row…full verify ↗canonical bytes (15807 B) ▸
{"actor":"system:backfill","investigation_id":"50d0d8ed-d4d0-4f10-a3fc-57c7dab3b37c","kind":"publish","page_slug":"ramzinex","published_at":"2026-06-04T17:15:53.706Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Ramzinex","sections":[{"content":"On June 2, 2026, OFAC added Ramzinex to the Specially Designated Nationals (SDN) list pursuant to Executive Order 13902, which authorizes sanctions against persons operating in the financial sector of the Iranian economy. The designation was announced as part of the 'Economic Fury' campaign, the Trump administration's most sweeping action to date against Iran's digital asset infrastructure. OFAC stated that Ramzinex 'has processed over $2.45 billion in transactions, including for transactions linked to the IRGC and a financial institution backed by the Iranian government, and has been used for sanctions evasion.' The three co-designated exchanges — Nobitex, Wallex, and Bitpin — were designated under both E.O. 13902 and E.O. 13224 (counter-terrorism). Ramzinex was designated solely under E.O. 13902, indicating the primary basis was operation within Iran's financial sector rather than a direct terrorism-financing nexus, though the IRGC connection was cited in the supporting narrative. All property and interests in property of Ramzinex in the United States or in the possession of U.S. persons are blocked. U.S. persons are prohibited from transacting with the entity. Under secondary sanctions provisions, foreign financial institutions conducting significant transactions with Ramzinex face correspondent account restrictions and potential secondary designation exposure.","heading":"OFAC Designation and Regulatory Status","severity":"critical","sources":[{"credibility":1,"name":"Economic Fury Targets Iran's Largest Digital Asset Exchange for Terror Finance and Sanctions Evasion — U.S. Department of the Treasury","type":"regulatory","url":"https://home.treasury.gov/news/press-releases/sb0519"},{"credibility":2,"name":"Three Enforcement Layers in Five Months: OFAC Designates Iran's Domestic Crypto Exchanges — TRM Labs","type":"research","url":"https://www.trmlabs.com/resources/blog/three-enforcement-layers-in-five-months-ofac-designates-irans-domestic-crypto-exchanges"},{"credibility":2,"name":"OFAC Sanctions Nobitex and Major Iranian Cryptocurrency Exchanges in Sweeping Evasion Crackdown — Chainalysis","type":"research","url":"https://www.chainalysis.com/blog/ofac-sanctions-iranian-crypto-exchanges-june-2026/"}]},{"content":"The Treasury Department's press release states that Ramzinex processed transactions linked to the Islamic Revolutionary Guard Corps (IRGC) — a U.S.-designated Foreign Terrorist Organization — and to a financial institution backed by the Iranian government. No specific transaction amounts, wallet addresses, or named counterparties are disclosed in the public record for Ramzinex; detailed on-chain forensics disaggregated by exchange were not published in the Treasury's June 2, 2026 press release. TRM Labs attributed Ramzinex across millions of addresses on Bitcoin, Ethereum, and TRON, consistent with the analytical methodology used for all four designated exchanges. Chainalysis announced it had labeled relevant cryptocurrency addresses associated with Ramzinex in its product suite following the designation. Elliptic's aggregate analysis found the four sanctioned exchanges sent or received cryptoasset transactions totaling at least $40 billion combined, though no per-exchange breakdown was published.","heading":"IRGC and Government-Linked Transactions","severity":"critical","sources":[{"credibility":1,"name":"Economic Fury Targets Iran's Largest Digital Asset Exchange for Terror Finance and Sanctions Evasion — U.S. Department of the Treasury","type":"regulatory","url":"https://home.treasury.gov/news/press-releases/sb0519"},{"credibility":2,"name":"Three Enforcement Layers in Five Months: OFAC Designates Iran's Domestic Crypto Exchanges — TRM Labs","type":"research","url":"https://www.trmlabs.com/resources/blog/three-enforcement-layers-in-five-months-ofac-designates-irans-domestic-crypto-exchanges"},{"credibility":2,"name":"OFAC Sanctions Nobitex and Three Other Iranian Cryptoasset Exchanges — Elliptic","type":"research","url":"https://www.elliptic.co/blog/ofac-sanctions-nobitex-and-three-other-iranian-cryptoasset-exchanges"}]},{"content":"According to TRM Labs, Ramzinex processed approximately $739 million in attributed crypto volume in 2025, making it the fourth-largest of the four sanctioned Iranian exchanges by 2025 volume. For context, Nobitex processed approximately $4.7 billion (over 50% of Iran's attributed inflows), Wallex approximately $1.45 billion, and Bitpin approximately $821 million. The four exchanges together accounted for approximately $7.7 billion — roughly 78% — of Iran's total attributed crypto volume in 2025. Since founding in 2018, Ramzinex's cumulative lifetime transaction volume exceeded $2.45 billion according to the Treasury press release. The exchange reportedly supported over 300 cryptocurrencies and claimed a user base of over 1 million accounts. These user and token figures are drawn from third-party business intelligence profiles (LinkedIn, IranTalent) and should be treated as indicative rather than independently audited.","heading":"Transaction Volume and Market Position","severity":"high","sources":[{"credibility":2,"name":"Three Enforcement Layers in Five Months: OFAC Designates Iran's Domestic Crypto Exchanges — TRM Labs","type":"research","url":"https://www.trmlabs.com/resources/blog/three-enforcement-layers-in-five-months-ofac-designates-irans-domestic-crypto-exchanges"},{"credibility":1,"name":"Economic Fury Targets Iran's Largest Digital Asset Exchange for Terror Finance and Sanctions Evasion — U.S. Department of the Treasury","type":"regulatory","url":"https://home.treasury.gov/news/press-releases/sb0519"},{"credibility":3,"name":"Ramzinex LinkedIn Company Profile","type":"other","url":"https://ir.linkedin.com/company/ramzinex"}]},{"content":"Ramzinex was founded in 2018 in Tehran, Iran. Its registered legal names include Mubadala Ramzinex and Ramzineh Electronic Commerce Innovation Company. According to its LinkedIn profile, the company is headquartered at Salehi Boulevard, Sharif Technology Tower, Tehran (postal code 1458883443) and employed between 51 and 200 staff. The founding team was reportedly drawn from graduates of Sharif University of Technology with backgrounds in finance, security, and business administration. Mohammad Hakimi is identified as CEO through professional networking profiles (LinkedIn, RocketReach); no other named executives appear in the public record. The platform offered spot trading, stop-loss orders, leverage trading, and automated trading bots, and described itself as 'a secure Iranian platform that's simple, fast, and professional.' During periods of geopolitical stress in 2025–2026, including Israeli military strikes that disrupted Iranian internet infrastructure, Ramzinex paused cryptocurrency deposits and withdrawals while stating that client assets were held in cold storage.","heading":"Company Background and Operations","severity":"medium","sources":[{"credibility":3,"name":"Ramzinex LinkedIn Company Profile","type":"other","url":"https://ir.linkedin.com/company/ramzinex"},{"credibility":3,"name":"Mohammad Hakimi — LinkedIn","type":"other","url":"https://www.linkedin.com/in/mohammad-hakimi-b6025241/"},{"credibility":2,"name":"Iran Crypto Market 'In the Dark': Trading Volumes Plunge 80% After Strikes — Finance Magnates via TradingView","type":"news_article","url":"https://www.tradingview.com/news/financemagnates:9acb8e13d094b:0-iran-crypto-market-in-the-dark-trading-volumes-plunge-80-after-strikes/"}]},{"content":"Under the secondary sanctions provisions attached to the June 2, 2026 OFAC designations, foreign financial institutions — including non-U.S. exchanges, banks, and payment processors — that conduct significant transactions with Ramzinex face the risk of correspondent account restrictions and secondary designation by OFAC. This risk extends to any counterparty that knowingly facilitates significant transactions on behalf of Ramzinex after the designation date. Compliance analysts at Global Ledger, TRM Labs, and Elliptic have each issued guidance noting that the explicit inclusion of secondary sanctions language in this action marks a higher degree of extraterritorial enforcement intent compared to some prior Iran-related designations. Global blockchain analytics firms Chainalysis and TRM Labs have labeled Ramzinex's attributed addresses in their respective screening products to enable downstream compliance checks.","heading":"Secondary Sanctions Risk for Third Parties","severity":"high","sources":[{"credibility":2,"name":"OFAC Targets Nobitex and Other Iranian Crypto Exchanges: Compliance Brief — Global Ledger","type":"research","url":"https://blog.globalledger.io/research-investigations/ofac-nobitex-iranian-crypto-exchanges"},{"credibility":2,"name":"Three Enforcement Layers in Five Months: OFAC Designates Iran's Domestic Crypto Exchanges — TRM Labs","type":"research","url":"https://www.trmlabs.com/resources/blog/three-enforcement-layers-in-five-months-ofac-designates-irans-domestic-crypto-exchanges"},{"credibility":2,"name":"Nobitex Sanctions Hit Iran's Largest Crypto Exchange as Compliance Risks Grow — Bitcoin.com News","type":"news_article","url":"https://news.bitcoin.com/nobitex-sanctions-hit-irans-largest-crypto-exchange-as-compliance-risks-grow/"}]},{"content":"The June 2, 2026 action is described by TRM Labs as the third major enforcement layer in five months targeting Iran's crypto infrastructure, following earlier actions in early 2026. The simultaneous designation of Nobitex (Iran's largest exchange by volume), Wallex, Bitpin, and Ramzinex was characterized by Treasury as its most expansive single action against Iran's digital asset economy to date. The designations target exchanges that collectively processed approximately 78% of Iran's attributed crypto volume in 2025, effectively targeting the dominant layer of Iran's domestic crypto on-ramp and off-ramp infrastructure. The action was conducted under the 'Economic Fury' campaign framing, which the Trump administration has used for a series of Iran-related economic pressure measures. The CoinDesk report published June 2, 2026 placed this action within the context of ongoing U.S.-Iran tensions and the use of crypto by sanctioned states to circumvent traditional financial restrictions.","heading":"Broader Enforcement Context","severity":"high","sources":[{"credibility":2,"name":"U.S. Sanctions Iranian Crypto Exchanges in Ongoing War Against the Country — CoinDesk","type":"news_article","url":"https://www.coindesk.com/policy/2026/06/02/u-s-sanctions-iranian-crypto-exchanges-in-ongoing-war-against-country"},{"credibility":2,"name":"Three Enforcement Layers in Five Months: OFAC Designates Iran's Domestic Crypto Exchanges — TRM Labs","type":"research","url":"https://www.trmlabs.com/resources/blog/three-enforcement-layers-in-five-months-ofac-designates-irans-domestic-crypto-exchanges"},{"credibility":2,"name":"OFAC Sanctions Nobitex and Three Other Iranian Cryptoasset Exchanges — Elliptic","type":"research","url":"https://www.elliptic.co/blog/ofac-sanctions-nobitex-and-three-other-iranian-cryptoasset-exchanges"}]}],"sources_used":[{"credibility":1,"name":"Economic Fury Targets Iran's Largest Digital Asset Exchange for Terror Finance and Sanctions Evasion — U.S. Department of the Treasury","type":"regulatory","url":"https://home.treasury.gov/news/press-releases/sb0519"},{"credibility":2,"name":"Three Enforcement Layers in Five Months: OFAC Designates Iran's Domestic Crypto Exchanges — TRM Labs","type":"research","url":"https://www.trmlabs.com/resources/blog/three-enforcement-layers-in-five-months-ofac-designates-irans-domestic-crypto-exchanges"},{"credibility":2,"name":"OFAC Sanctions Nobitex and Major Iranian Cryptocurrency Exchanges in Sweeping Evasion Crackdown — Chainalysis","type":"research","url":"https://www.chainalysis.com/blog/ofac-sanctions-iranian-crypto-exchanges-june-2026/"},{"credibility":2,"name":"OFAC Sanctions Nobitex and Three Other Iranian Cryptoasset Exchanges — Elliptic","type":"research","url":"https://www.elliptic.co/blog/ofac-sanctions-nobitex-and-three-other-iranian-cryptoasset-exchanges"},{"credibility":2,"name":"Nobitex Sanctions Hit Iran's Largest Crypto Exchange as Compliance Risks Grow — Bitcoin.com News","type":"news_article","url":"https://news.bitcoin.com/nobitex-sanctions-hit-irans-largest-crypto-exchange-as-compliance-risks-grow/"},{"credibility":2,"name":"U.S. Sanctions Iranian Crypto Exchanges in Ongoing War Against the Country — CoinDesk","type":"news_article","url":"https://www.coindesk.com/policy/2026/06/02/u-s-sanctions-iranian-crypto-exchanges-in-ongoing-war-against-country"},{"credibility":2,"name":"OFAC Targets Nobitex and Other Iranian Crypto Exchanges: Compliance Brief — Global Ledger","type":"research","url":"https://blog.globalledger.io/research-investigations/ofac-nobitex-iranian-crypto-exchanges"},{"credibility":2,"name":"US Treasury Sanctions Iran's Largest Crypto Exchange Nobitex Along With Three Other Iranian Platforms Under Economic Fury Campaign — Unchained","type":"news_article","url":"https://unchainedcrypto.com/us-treasury-sanctions-irans-largest-crypto-exchange-nobitex-along-with-three-other-iranian-platforms-under-economic-fury-campaign/"},{"credibility":2,"name":"Iran Crypto Market 'In the Dark': Trading Volumes Plunge 80% After Strikes — Finance Magnates via TradingView","type":"news_article","url":"https://www.tradingview.com/news/financemagnates:9acb8e13d094b:0-iran-crypto-market-in-the-dark-trading-volumes-plunge-80-after-strikes/"},{"credibility":2,"name":"US Sanctions Iranian Crypto Exchanges Nobitex, Bitpin, Ramzinex, and Wallex — MEXC News","type":"news_article","url":"https://www.mexc.com/news/1126101"},{"credibility":3,"name":"Ramzinex LinkedIn Company Profile","type":"other","url":"https://ir.linkedin.com/company/ramzinex"},{"credibility":3,"name":"Mohammad Hakimi — LinkedIn (CEO, Ramzinex)","type":"other","url":"https://www.linkedin.com/in/mohammad-hakimi-b6025241/"}],"summary":"Ramzinex (legal name: Mubadala Ramzinex; also registered as Ramzineh Electronic Commerce Innovation Company) is an Iranian cryptocurrency exchange founded in 2018 and headquartered in Tehran. On June 2, 2026, the U.S. Treasury's Office of Foreign Assets Control (OFAC) designated Ramzinex under Executive Order 13902, citing facilitation of transactions linked to the Islamic Revolutionary Guard Corps (IRGC), a government-backed Iranian financial institution, and sanctions evasion. The designation was part of the Trump administration's broader 'Economic Fury' campaign, which simultaneously sanctioned three other major Iranian exchanges: Nobitex, Wallex, and Bitpin.","timeline":[{"date":"2018-01-01","event":"Ramzinex founded in Tehran, Iran by a team reportedly including graduates of Sharif University of Technology.","source":"U.S. Department of the Treasury press release SB0519","source_url":"https://home.treasury.gov/news/press-releases/sb0519"},{"date":"2026-06-02","event":"OFAC designates Ramzinex (legal name: Mubadala Ramzinex / Ramzineh Electronic Commerce Innovation Company) under Executive Order 13902 as part of the Economic Fury campaign, citing $2.45B in lifetime transactions including IRGC-linked activity and sanctions evasion. Simultaneously designated alongside Nobitex, Wallex, and Bitpin.","source":"U.S. Department of the Treasury press release SB0519","source_url":"https://home.treasury.gov/news/press-releases/sb0519"}]},"v":1}Verify offline (run on your own machine)python -m src.verify_decision 854dc46c-ac61-4a2a-a888-1d31173865d8 - #2reviewby reviewerreviewer2026-06-09 23:44:28ZScore: 2 → 2 (no score change)The page is substantively accurate with respect to the core OFAC designation facts, transaction volumes, and enforcement context. The most significant factual error is the claim that Wallex and Bitpin were designated under both EO 13902 and EO 13224 — the Treasury primary source confirms only Nobitex received the dual designation; Wallex, Bitpin, and Ramzinex were all designated solely under EO 13902. Minor issues include a founding-year ambiguity (2017 vs. 2018), an attribution error in the timeline (Sharif University detail cited to Treasury rather than third-party sources), and an overstated characterization of compliance analyst consensus on secondary sanctions language. All primary sources are live and accessible.anchoranchored
- chain
- ●mainnet-betaslot 425,429,924
- sig
2YUiNZKJfnd5…CKh2ikGPexplorer ↗- hash
J7BUam3YEoVS…haouMAK7sha256 → base58
verifying row…full verify ↗canonical bytes (1070 B) ▸
{"actor":"reviewer","decided_at":"2026-06-09T23:44:28.079Z","decision":"review","investigation_id":"50d0d8ed-d4d0-4f10-a3fc-57c7dab3b37c","new_score":2,"page_slug":"ramzinex","prev_score":2,"reason":"The page is substantively accurate with respect to the core OFAC designation facts, transaction volumes, and enforcement context. The most significant factual error is the claim that Wallex and Bitpin were designated under both EO 13902 and EO 13224 — the Treasury primary source confirms only Nobitex received the dual designation; Wallex, Bitpin, and Ramzinex were all designated solely under EO 13902. Minor issues include a founding-year ambiguity (2017 vs. 2018), an attribution error in the timeline (Sharif University detail cited to Treasury rather than third-party sources), and an overstated characterization of compliance analyst consensus on secondary sanctions language. All primary sources are live and accessible.","score_delta":0,"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 667435eb-ae16-44e8-9f55-02fffc29a98a - #3review approveby judgejudge2026-06-09 23:44:28ZScore: 2 → 2 (no score change)The review confirmed 16 of 23 claims from Tier 1 and Tier 2 sources, with zero disputed claims and a reviewer-computed disputed_pct of 9%, placing this in the approve band. All core facts about Ramzinex's OFAC designation — the date, the executive order, the $2.45B figure, the co-designated exchanges, and the sanctions consequences — are confirmed by the Treasury primary source. The most notable factual error (claim_findings[5]) concerns co-designated exchanges Wallex and Bitpin: the page incorrectly states they were designated under both EO 13902 and EO 13224, when the Treasury press release confirms only Nobitex received the dual designation. This error pertains to entities other than Ramzinex and does not undermine Ramzinex's own record. Two high-priority coverage gaps remain (on-chain wallet attribution and named executive verification), which suggest the page would benefit from expansion but do not warrant denial or revision at this time.anchoranchored
- chain
- ●mainnet-betaslot 425,429,929
- sig
3HoB5gKz8oqR…7dF5hjbsexplorer ↗- hash
5dX4FTPJUZnu…9EmfK8Ljsha256 → base58
verifying row…full verify ↗canonical bytes (1304 B) ▸
{"actor":"judge","decided_at":"2026-06-09T23:44:28.079Z","decision":"review_approve","investigation_id":"50d0d8ed-d4d0-4f10-a3fc-57c7dab3b37c","new_score":2,"page_slug":"ramzinex","prev_score":2,"reason":"The review confirmed 16 of 23 claims from Tier 1 and Tier 2 sources, with zero disputed claims and a reviewer-computed disputed_pct of 9%, placing this in the approve band. All core facts about Ramzinex's OFAC designation — the date, the executive order, the $2.45B figure, the co-designated exchanges, and the sanctions consequences — are confirmed by the Treasury primary source. The most notable factual error (claim_findings[5]) concerns co-designated exchanges Wallex and Bitpin: the page incorrectly states they were designated under both EO 13902 and EO 13224, when the Treasury press release confirms only Nobitex received the dual designation. This error pertains to entities other than Ramzinex and does not undermine Ramzinex's own record. Two high-priority coverage gaps remain (on-chain wallet attribution and named executive verification), which suggest the page would benefit from expansion but do not warrant denial or revision at this time.","score_delta":0,"sequence_num":3,"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 7746f185-ab6a-4cff-aba3-7293fff683d5 - #4reviewby reviewerreviewer2026-10-16 13:59:24ZScore: 2 → 2 (no score change)The page's core claims are well supported by primary sources: the OFAC SDN entry and Treasury press release directly confirm the June 2, 2026 designation of Ramzinex under E.O. 13902, the 'Subject to Secondary Sanctions' marking, the company number and address, the $2.45 billion lifetime transaction figure, and the IRGC/government-institution allegation language. Analytics-firm figures (78% collective share, Nobitex/Wallex/Bitpin individual percentages, Ramzinex's $739 million 2025 volume) check out against TRM Labs and Chainalysis reporting. Weaknesses are concentrated in the lower-credibility 'Entity Profile' section: its lead citation (ideaagency.net) is dead and unarchivable, leaving the one-million-user and 200-trading-pair figures unverifiable against a conflicting low-tier source. Two sentences in the Economic Fury section mildly overstate their sourcing: the $1 billion Bessent seizure figure is real but comes from a different public statement than the press release cited, and the 'designated exchanges helped move assets out of Iran' allegation is specific to Nobitex in the cited reporting, not the group as a whole.anchoranchored
- chain
- ●mainnet-betaslot 457,662,933
- sig
2e2Lyjupt9nm…BEZ9Dixrexplorer ↗- hash
9wCdyx9Cox7s…49eyj68Hsha256 → base58
verifying row…full verify ↗canonical bytes (1729 B) ▸
{"actor":"reviewer","artifact_identity":"fe0fe4b8787360567969987db1747242","decided_at":"2026-10-16T13:59:24.648Z","decision":"review","disputed_pct":0.1,"findings_hash":"5Z9ta65h2kFJZLFtc1iMNuyUQE7VoCdLEU7wx8BvDi3N","investigation_id":"50d0d8ed-d4d0-4f10-a3fc-57c7dab3b37c","mode":"findings_only","new_score":2,"page_content_hash":"5f2d67e5e5e80eb7cb7efd26596ffcdf9b1d13ba0bd536fb107d4d1561cb3fcb","page_slug":"ramzinex","prev_score":2,"reason":"The page's core claims are well supported by primary sources: the OFAC SDN entry and Treasury press release directly confirm the June 2, 2026 designation of Ramzinex under E.O. 13902, the 'Subject to Secondary Sanctions' marking, the company number and address, the $2.45 billion lifetime transaction figure, and the IRGC/government-institution allegation language. Analytics-firm figures (78% collective share, Nobitex/Wallex/Bitpin individual percentages, Ramzinex's $739 million 2025 volume) check out against TRM Labs and Chainalysis reporting. Weaknesses are concentrated in the lower-credibility 'Entity Profile' section: its lead citation (ideaagency.net) is dead and unarchivable, leaving the one-million-user and 200-trading-pair figures unverifiable against a conflicting low-tier source. Two sentences in the Economic Fury section mildly overstate their sourcing: the $1 billion Bessent seizure figure is real but comes from a different public statement than the press release cited, and the 'designated exchanges helped move assets out of Iran' allegation is specific to Nobitex in the cited reporting, not the group as a whole.","score_delta":0,"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 b37edf52-9b94-4506-8e7e-ad671341605b - #5reviewby reviewerreviewer2026-10-27 10:37:59ZScore: 2 → 2 (no score change)The core facts hold: the 2 June 2026 designation, the SDN entry details, the IRGC link allegation, the 2.45B lifetime figure and the 739M 2025 volume all match primary sources. Problems are limited to the Economic Fury context section, where the March 2025 seizure date and the 'largest-ever' description are not in the cited sources. The exchange market-share figures for Wallex and Bitpin do not match TRM's volumes, and the 'two authorities' wording overstates. Profile claims rest on low-credibility sources I did not fetch.anchoranchored
- chain
- ●mainnet-betaslot 462,039,483
- sig
37KhjpYk8qhN…mS9nDcvfexplorer ↗- hash
5aE9KnnZ4ow3…Kb1ETgYdsha256 → base58
verifying row…full verify ↗canonical bytes (1373 B) ▸
{"actor":"reviewer","artifact_identity":"989335801bc8231832a6fb3d2dd36fbd","decided_at":"2026-10-27T10:37:58.854Z","decision":"review","disputed_pct":0.25,"findings_hash":"CcGt2qEvB9cv8zzWzr8D1EHvqxTnbPHp8Tbkq1pSo3PQ","investigation_id":"50d0d8ed-d4d0-4f10-a3fc-57c7dab3b37c","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":2,"omissions":{"material":0,"total":1},"page_content_hash":"5f2d67e5e5e80eb7cb7efd26596ffcdf9b1d13ba0bd536fb107d4d1561cb3fcb","page_slug":"ramzinex","prev_score":2,"reason":"The core facts hold: the 2 June 2026 designation, the SDN entry details, the IRGC link allegation, the 2.45B lifetime figure and the 739M 2025 volume all match primary sources. Problems are limited to the Economic Fury context section, where the March 2025 seizure date and the 'largest-ever' description are not in the cited sources. The exchange market-share figures for Wallex and Bitpin do not match TRM's volumes, and the 'two authorities' wording overstates. Profile claims rest on low-credibility sources I did not fetch.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":5,"subject_status":"sanctioned","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 5f1b313c-66d5-414b-a86c-bbd1d3e13f18 - #6review reviseby judgejudge2026-10-27 10:37:59ZScore: 2 → 0 (-10)The core facts hold: the 2 June 2026 OFAC designation, the SDN entry details, the secondary-sanctions marking and the Treasury and TRM figures match primary sources (claim_findings[0-3, 8, 10]). Three of 12 claims (25%) were disputed or unverifiable: the 'March 2025' seizure date and the 'largest-ever' characterization are not in the cited sources (claim_findings[5-6]), and the profile claims rest on unfetched low-credibility sources (claim_findings[9]). Several partially supported items (market-share figures, 'two authorities', executives tied to 'other exchanges') need wording corrections. A high-priority gap on post-designation operating status also argues against a clean approval, but no shutdown or material omission was found.anchoranchored
- chain
- ●mainnet-betaslot 462,039,488
- sig
4zYarQDnSLCY…AqAQEWs8explorer ↗- hash
4bXqYbByxcPw…Fwj7dDNhsha256 → base58
verifying row…full verify ↗canonical bytes (1381 B) ▸
{"actor":"judge","artifact_identity":"989335801bc8231832a6fb3d2dd36fbd","band_override":null,"decided_at":"2026-10-27T10:37:58.854Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.25,"investigation_id":"50d0d8ed-d4d0-4f10-a3fc-57c7dab3b37c","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"ramzinex","prev_score":2,"reason":"The core facts hold: the 2 June 2026 OFAC designation, the SDN entry details, the secondary-sanctions marking and the Treasury and TRM figures match primary sources (claim_findings[0-3, 8, 10]). Three of 12 claims (25%) were disputed or unverifiable: the 'March 2025' seizure date and the 'largest-ever' characterization are not in the cited sources (claim_findings[5-6]), and the profile claims rest on unfetched low-credibility sources (claim_findings[9]). Several partially supported items (market-share figures, 'two authorities', executives tied to 'other exchanges') need wording corrections. A high-priority gap on post-designation operating status also argues against a clean approval, but no shutdown or material omission was found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-10,"sequence_num":6,"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 28f058c0-8faf-4702-8ff0-857187a4ab77 - #7rescoreby systemsystem2026-11-01 12:37:10ZScore: 0 → 26 (+26)Rescored under Scoring v2, the published formula (avoid.net/scoring): 0 → 26. Problems weighed by who is responsible: the subject's own conduct −50, concerns that are not fraud −10, problems around the subject, caused by others −3; legitimacy credit long-running +10; no established finding that it defrauded anyone, so it stays out of the red band; 1 section(s) set aside until a failed fact-check is resolved; fact-check adjustments (−10) now shown as page reliability, not in the score.anchoranchored
- chain
- ●mainnet-betaslot 464,094,847
- sig
67D2o5rEQ1HX…VkUmFVxRexplorer ↗- hash
715NAN1tMHuh…9awEJ9Q3sha256 → base58
verifying row…full verify ↗canonical bytes (851 B) ▸
{"actor":"system","decided_at":"2026-11-01T12:37:10.730Z","decision":"rescore","investigation_id":"50d0d8ed-d4d0-4f10-a3fc-57c7dab3b37c","new_score":26,"page_slug":"ramzinex","prev_score":0,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 0 → 26. Problems weighed by who is responsible: the subject's own conduct −50, concerns that are not fraud −10, problems around the subject, caused by others −3; legitimacy credit long-running +10; no established finding that it defrauded anyone, so it stays out of the red band; 1 section(s) set aside until a failed fact-check is resolved; fact-check adjustments (−10) now shown as page reliability, not in the score.","score_delta":26,"score_model":"v2","sequence_num":7,"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 dc16493e-1fcb-4859-bab4-795999e72806 - #8rescoreby systemsystem2026-11-02 14:43:12ZScore: 26 → 36 (+10)Re-read and rescored after the page was re-researched (2026-11-02). Rescored under Scoring v2, the published formula (avoid.net/scoring): 26 → 36. Problems weighed by who is responsible: the subject's own conduct −40, concerns that are not fraud −6, problems around the subject, caused by others −3; legitimacy credit long-running +10.anchoranchored
- chain
- ●mainnet-betaslot 464,533,100
- sig
9mrqk8x3afmi…5HS77SReexplorer ↗- hash
45kSF5XC4b6f…prRrXHrqsha256 → base58
verifying row…full verify ↗canonical bytes (698 B) ▸
{"actor":"system","decided_at":"2026-11-02T14:43:11.105Z","decision":"rescore","investigation_id":"50d0d8ed-d4d0-4f10-a3fc-57c7dab3b37c","new_score":36,"page_slug":"ramzinex","prev_score":26,"reason":"Re-read and rescored after the page was re-researched (2026-11-02). Rescored under Scoring v2, the published formula (avoid.net/scoring): 26 → 36. Problems weighed by who is responsible: the subject's own conduct −40, concerns that are not fraud −6, problems around the subject, caused by others −3; legitimacy credit long-running +10.","score_delta":10,"score_model":"v2","sequence_num":8,"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 81640c6d-ad7a-4df5-b228-5b9715ba9b1c - #9reviewby reviewerreviewer2026-11-02 14:44:23ZScore: 36 → 36 (no score change)The core claim, the June 2, 2026 OFAC SDN designation with its address, 2018 date and program tags, matches the OFAC record. The $2.45B figure is supported by two outlets. The IRGC and government-backed-institution link to Ramzinex is supported by Unchained but not by Decrypt or Elliptic, which tie IRGC activity to Nobitex. The page hedges honestly on unverified profile claims and on current operating status. The TRM Labs and Coingape claims were not checked.anchoranchored
- chain
- ●mainnet-betaslot 464,533,400
- sig
3Y3ihxFWrzYq…RdDUoypTexplorer ↗- hash
3Qt7KuwnWfui…NxLU6Cu4sha256 → base58
verifying row…full verify ↗canonical bytes (1310 B) ▸
{"actor":"reviewer","artifact_identity":"147f617e7750e2412c4feaae28e1de56","decided_at":"2026-11-02T14:44:23.199Z","decision":"review","disputed_pct":0.25,"findings_hash":"9gjz42gXYGsqdCj3yqfV1XoJUv2mHDwdvpuQnrVJQQLg","investigation_id":"50d0d8ed-d4d0-4f10-a3fc-57c7dab3b37c","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":36,"omissions":{"material":0,"total":1},"page_content_hash":"cef92b87d09c234be61f843f79a599505629ff254a75605b59e1abd598e25fd0","page_slug":"ramzinex","prev_score":36,"reason":"The core claim, the June 2, 2026 OFAC SDN designation with its address, 2018 date and program tags, matches the OFAC record. The $2.45B figure is supported by two outlets. The IRGC and government-backed-institution link to Ramzinex is supported by Unchained but not by Decrypt or Elliptic, which tie IRGC activity to Nobitex. The page hedges honestly on unverified profile claims and on current operating status. The TRM Labs and Coingape claims were not checked.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":9,"subject_status":"sanctioned","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 c49587f1-738e-4b47-b75c-576425e66591 - #10review reviseby judgejudge2026-11-02 14:44:23ZScore: 36 → 36 (no score change)The core claim, the June 2, 2026 OFAC SDN designation with its address, 2018 date and program tags, was confirmed against the OFAC record (claim_findings[0]). Two of eight claims (25%) could not be checked because the TRM Labs and Coingape sources were not read (claim_findings[6], [7]), which places the page in the minor-issues band. The IRGC and government-backed-institution link to Ramzinex rests on one secondary outlet and the Treasury release was not consulted (claim_findings[1], [2]), though the page labels this as secondary reporting. The Bessent venue attribution is slightly uncertain (claim_findings[4]). The only omission is minor and the subject status does not contradict the page.anchoranchored
- chain
- ●mainnet-betaslot 464,533,406
- sig
3kWTgwmjiJhc…KwXTRYvCexplorer ↗- hash
FJot5ZxHhj97…eDQaDnKzsha256 → base58
verifying row…full verify ↗canonical bytes (1340 B) ▸
{"actor":"judge","artifact_identity":"147f617e7750e2412c4feaae28e1de56","band_override":null,"decided_at":"2026-11-02T14:44:23.199Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.25,"investigation_id":"50d0d8ed-d4d0-4f10-a3fc-57c7dab3b37c","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":36,"page_slug":"ramzinex","prev_score":36,"reason":"The core claim, the June 2, 2026 OFAC SDN designation with its address, 2018 date and program tags, was confirmed against the OFAC record (claim_findings[0]). Two of eight claims (25%) could not be checked because the TRM Labs and Coingape sources were not read (claim_findings[6], [7]), which places the page in the minor-issues band. The IRGC and government-backed-institution link to Ramzinex rests on one secondary outlet and the Treasury release was not consulted (claim_findings[1], [2]), though the page labels this as secondary reporting. The Bessent venue attribution is slightly uncertain (claim_findings[4]). The only omission is minor and the subject status does not contradict the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":10,"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 43cf6087-bac5-45da-a19d-1b0e2ca0d365 - #11rescoreby systemsystem2026-11-02 14:44:24ZScore: 36 → 37 (+1)Recalculated after the fact-check of 2026-11-02. Rescored under Scoring v2, the published formula (avoid.net/scoring): 36 → 37. Problems weighed by who is responsible: the subject's own conduct −40, concerns that are not fraud −6, problems around the subject, caused by others −1.9; legitimacy credit long-running +10; 2 section(s) set aside until a failed fact-check is resolved.anchoranchored
- chain
- ●mainnet-betaslot 464,533,411
- sig
Wtp4bXFt2qob…xaoc6RPvexplorer ↗- hash
4iGHz1izzeuX…FJHoUGLqsha256 → base58
verifying row…full verify ↗canonical bytes (743 B) ▸
{"actor":"system","decided_at":"2026-11-02T14:44:23.199Z","decision":"rescore","investigation_id":"50d0d8ed-d4d0-4f10-a3fc-57c7dab3b37c","new_score":37,"page_slug":"ramzinex","prev_score":36,"reason":"Recalculated after the fact-check of 2026-11-02. Rescored under Scoring v2, the published formula (avoid.net/scoring): 36 → 37. Problems weighed by who is responsible: the subject's own conduct −40, concerns that are not fraud −6, problems around the subject, caused by others −1.9; legitimacy credit long-running +10; 2 section(s) set aside until a failed fact-check is resolved.","score_delta":1,"score_model":"v2","sequence_num":11,"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 ebe25497-82ae-46b6-802f-38bc50f31b85 - #12rescoreby systemsystem2026-11-04 02:05:01ZScore: 37 → 41 (+4)Re-read and rescored after the page was re-researched (2026-11-04). Rescored under Scoring v2, the published formula (avoid.net/scoring): 37 → 41. Problems weighed by who is responsible: the subject's own conduct −40, problems around the subject, caused by others −0.8; legitimacy credit long-running +10; serious regulatory wrongdoing with no established harm to customers is held in WARNING (26–50).anchoranchored
- chain
- ●mainnet-betaslot 465,127,438
- sig
5aetSNc82S4K…w9Poc7Eaexplorer ↗- hash
AHXSWH6udsMa…6yG9WUiYsha256 → base58
verifying row…full verify ↗canonical bytes (764 B) ▸
{"actor":"system","decided_at":"2026-11-04T02:04:59.914Z","decision":"rescore","investigation_id":"50d0d8ed-d4d0-4f10-a3fc-57c7dab3b37c","new_score":41,"page_slug":"ramzinex","prev_score":37,"reason":"Re-read and rescored after the page was re-researched (2026-11-04). Rescored under Scoring v2, the published formula (avoid.net/scoring): 37 → 41. Problems weighed by who is responsible: the subject's own conduct −40, problems around the subject, caused by others −0.8; legitimacy credit long-running +10; serious regulatory wrongdoing with no established harm to customers is held in WARNING (26–50).","score_delta":4,"score_model":"v2","sequence_num":12,"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 36c31194-c6d9-43a6-9955-f6f85936b69b - #13reviewby reviewerreviewer2026-11-04 02:06:20ZScore: 41 → 41 (no score change)The page's claims are accurately attributed and hedged, and the core facts (June 2, 2026 OFAC designation, 2018 founding, USD 739M TRM volume, Scorechain-reported IRGC allegation) check out against TRM and Scorechain. One nuance: the dual-EO claim is TRM's but OFAC's own page cites only E.O. 13902. The OFAC primary release and the Defiant and Coingape sources were not fetched by this reviewer.anchoranchored
- chain
- ●mainnet-betaslot 465,127,727
- sig
yDGskMCKm2Bc…RbzyrAisexplorer ↗- hash
Cox4ZgLM2efx…HjDqayCasha256 → base58
verifying row…full verify ↗canonical bytes (1241 B) ▸
{"actor":"reviewer","artifact_identity":"afe038d4f1ed4abfea1d1d733f0441d0","decided_at":"2026-11-04T02:06:20.860Z","decision":"review","disputed_pct":0,"findings_hash":"9Aq9rrt33vBcw35HXPRwFW5oM7JR3gsGau143ioEEyR3","investigation_id":"50d0d8ed-d4d0-4f10-a3fc-57c7dab3b37c","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":41,"omissions":{"material":0,"total":1},"page_content_hash":"b32918f69860ecc4caa9b077ebdb33e5a3b4a99ec4bfb9c4eb262b67ef704f2f","page_slug":"ramzinex","prev_score":41,"reason":"The page's claims are accurately attributed and hedged, and the core facts (June 2, 2026 OFAC designation, 2018 founding, USD 739M TRM volume, Scorechain-reported IRGC allegation) check out against TRM and Scorechain. One nuance: the dual-EO claim is TRM's but OFAC's own page cites only E.O. 13902. The OFAC primary release and the Defiant and Coingape sources were not fetched by this reviewer.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":13,"subject_status":"sanctioned","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 9e794cd6-8fdc-4bd6-9727-5988fa7dce2f - #14review reviseby judgejudge2026-11-04 02:06:21ZScore: 41 → 41 (no score change)Six of seven claims were confirmed and none were disputed or unverifiable, so the claim-based dispute rate is 0%. The page is moved from approve to a light revision because claim_findings[1] was only partially supported (the dual E.O. 13224 and 13902 designation is TRM's account, while OFAC's own page cites only E.O. 13902), and because the review lists a high-priority coverage gap: the OFAC release and SDN entry were never cited directly. The sanction is stated on the page and the omission about SDN entry details is minor, so the penalty is small.anchoranchored
- chain
- ●mainnet-betaslot 465,127,732
- sig
3jsqMvs3X5f5…CKh3hPodexplorer ↗- hash
5SGt4HLzbnKD…DzzppN62sha256 → base58
verifying row…full verify ↗canonical bytes (1891 B) ▸
{"actor":"judge","artifact_identity":"afe038d4f1ed4abfea1d1d733f0441d0","band_override":{"actual_delta":-5,"actual_verdict":"review_revise","disputed_pct":0,"expected_delta_range":[0,0],"expected_verdict":"review_approve","rationale":"Six of seven claims were confirmed and none were disputed or unverifiable, so the claim-based dispute rate is 0%. The page is moved from approve to a light revision because claim_findings[1] was only partially supported (the dual E.O. 13224 and 13902 designation is TRM's account, while OFAC's own page cites only E.O. 13902), and because the review lists a high-priority coverage gap: the OFAC release and SDN entry were never cited directly. The sanction is stated on the page and the omission about SDN entry details is minor, so the penalty is small."},"decided_at":"2026-11-04T02:06:20.860Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"50d0d8ed-d4d0-4f10-a3fc-57c7dab3b37c","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":41,"page_slug":"ramzinex","prev_score":41,"reason":"Six of seven claims were confirmed and none were disputed or unverifiable, so the claim-based dispute rate is 0%. The page is moved from approve to a light revision because claim_findings[1] was only partially supported (the dual E.O. 13224 and 13902 designation is TRM's account, while OFAC's own page cites only E.O. 13902), and because the review lists a high-priority coverage gap: the OFAC release and SDN entry were never cited directly. The sanction is stated on the page and the omission about SDN entry details is minor, so the penalty is small.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":14,"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 82ede517-8f22-423a-b09c-c5ac4e1e1c9b - #15rescoreby systemsystem2026-11-17 18:24:01ZScore: 41 → 44 (+3)Re-read and rescored after the page was re-researched (2026-11-17). Rescored under Scoring v2, the published formula (avoid.net/scoring): 41 → 44. Problems weighed by who is responsible: the subject's own conduct −40, problems around the subject, caused by others −0.8; legitimacy credit long-running +10; serious regulatory wrongdoing with no established harm to customers is held in WARNING (26–50).anchoranchored
- chain
- ●mainnet-betaslot 470,633,122
- sig
4JyNmojQYDr3…rBbppVGqexplorer ↗- hash
8SjKRrgDriUd…tQhYf3jasha256 → base58
verifying row…full verify ↗canonical bytes (764 B) ▸
{"actor":"system","decided_at":"2026-11-17T18:24:00.952Z","decision":"rescore","investigation_id":"50d0d8ed-d4d0-4f10-a3fc-57c7dab3b37c","new_score":44,"page_slug":"ramzinex","prev_score":41,"reason":"Re-read and rescored after the page was re-researched (2026-11-17). Rescored under Scoring v2, the published formula (avoid.net/scoring): 41 → 44. Problems weighed by who is responsible: the subject's own conduct −40, problems around the subject, caused by others −0.8; legitimacy credit long-running +10; serious regulatory wrongdoing with no established harm to customers is held in WARNING (26–50).","score_delta":3,"score_model":"v2","sequence_num":15,"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 472ec183-6c48-49ea-8a0c-16ff0db11918 - #16reviewby reviewerreviewer2026-11-17 18:25:51ZScore: 44 → 44 (no score change)The core claims (designation date, co-designated exchanges, E.O. 13902, 2018 founding, USD 2.45B lifetime volume, IRGC allegations, TRM USD 739M volume and 78% share) match the Treasury press release, TRM and Scorechain. The page attributes allegations to their sources and notes source discrepancies on the E.O. Not independently checked: the SDN entry details and FAQ 1257 text. Current operating status is not covered.anchoranchored
- chain
- ●mainnet-betaslot 470,633,645
- sig
3LfuCSn12bmh…MCc68oRYexplorer ↗- hash
8hhBNWjtcBVq…3PMhAqUUsha256 → base58
verifying row…full verify ↗canonical bytes (1228 B) ▸
{"actor":"reviewer","artifact_identity":"ba5a7c6afdbf6a9cdc3746d5cb3444bb","decided_at":"2026-11-17T18:25:51.007Z","decision":"review","disputed_pct":0,"findings_hash":"hhgeDZyhH4HT2Kt5YdirboxGMVhzHzc3ezXqSCi2yTp","investigation_id":"50d0d8ed-d4d0-4f10-a3fc-57c7dab3b37c","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":44,"page_content_hash":"dc42203b933fecf5b3381caa86923b97ae5c2634aad5ff8b237e2c02601ae979","page_slug":"ramzinex","prev_score":44,"reason":"The core claims (designation date, co-designated exchanges, E.O. 13902, 2018 founding, USD 2.45B lifetime volume, IRGC allegations, TRM USD 739M volume and 78% share) match the Treasury press release, TRM and Scorechain. The page attributes allegations to their sources and notes source discrepancies on the E.O. Not independently checked: the SDN entry details and FAQ 1257 text. Current operating status is not covered.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":16,"subject_status":"sanctioned","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 0b7b05ef-01db-461d-aaf6-e65a4439ec86 - #17review approveby judgejudge2026-11-17 18:25:51ZScore: 44 → 44 (no score change)All four checked claims (claim_findings[0] to [3]) were confirmed against the Treasury press release and the TRM Labs and Scorechain reports, so none are disputed or unverifiable. The review found no omissions, and the page correctly states the sanctioned status (subject_status.contradicts_page is false). Open coverage gaps (operating status after designation, SDN entry details, on-chain data) are medium or low priority and suggest expansion rather than a defect.anchoranchored
- chain
- ●mainnet-betaslot 470,633,651
- sig
47cqPF11mis9…8EJ9Uk4texplorer ↗- hash
DEa3BWcussVM…jDC3Asmksha256 → base58
verifying row…full verify ↗canonical bytes (1106 B) ▸
{"actor":"judge","artifact_identity":"ba5a7c6afdbf6a9cdc3746d5cb3444bb","band_override":null,"decided_at":"2026-11-17T18:25:51.007Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"50d0d8ed-d4d0-4f10-a3fc-57c7dab3b37c","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":44,"page_slug":"ramzinex","prev_score":44,"reason":"All four checked claims (claim_findings[0] to [3]) were confirmed against the Treasury press release and the TRM Labs and Scorechain reports, so none are disputed or unverifiable. The review found no omissions, and the page correctly states the sanctioned status (subject_status.contradicts_page is false). Open coverage gaps (operating status after designation, SDN entry details, on-chain data) are medium or low priority and suggest expansion rather than a defect.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":17,"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 12e87238-4325-4334-8cc5-041f9ecdd8ab
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>.