← XDC Network3 decisions on this page
Audit log
Every state-changing event for XDC Network: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions carry three independent witnesses — the original source, an Internet Archive snapshot taken at submission time, and a Solana memo signed by our publicly-disclosed publisher key.
- #1publishby system:backfill2026-05-14 06:02:58ZScore: ? → ? (no score change)anchoranchored
- chain
- ●mainnet-betaslot 419,629,038
- sig
5mLhRcTN4mGV…TvzD3dcYexplorer ↗- hash
eBJuB49rw4rv…9p7rNRXTsha256 → base58
verifying row…full verify ↗canonical bytes (5220 B) ▸
{"actor":"system:backfill","investigation_id":"fc145b64-1335-4b3c-aafe-fffa9096e641","kind":"publish","page_slug":"xdc-network","published_at":"2026-05-14T06:02:58.696Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"XDC Network","sections":[{"content":"XDC Network was co-founded in 2017 by Atul Khekade, Ritesh Kakkad, and Karan Bhardwaj through XinFin. Atul Khekade has 14+ years in technology and played a key role in demonstrating the first permissioned blockchain system for a consortium of top Asian banks. Ritesh Kakkad has 20+ years of experience in cloud hosting and internet infrastructure. The co-founders also operate XVC Tech, a $125M fund focused on NextGen technology investments.","heading":"Founders and Background","severity":"low","sources":[{"credibility":2,"name":"Bitrue: Get to Know XDC Founder","type":"news_article","url":"https://www.bitrue.com/blog/get-to-know-xdc-network-founder"},{"credibility":2,"name":"XinFin: About XDC Network","type":"official","url":"https://xinfin.org/about"}]},{"content":"XDC Network is specifically designed for enterprise use cases in trade finance, payments, and RWA tokenization. The network is ISO 20022-aligned for institutional interoperability, features low transaction fees, and fast settlement times. It operates as a delegated proof-of-stake (XDPoS) consensus with carbon-neutral operations. Notable integrations include native USDC deployment and partnerships in the payments and trade finance sectors.","heading":"Trade Finance and RWA Focus","severity":"low","sources":[{"credibility":2,"name":"XDC Network: U.S. Regulatory Progress 2025","type":"official","url":"https://xdc.org/articles/u.s.-regulatory-progress-and-native-usdc-headline-xdc-network-growth-in-2025"}]},{"content":"As of the 6th mainnet anniversary (June 2025), XDC Network has processed over 801 million transactions and deployed 178,000+ smart contracts. The XDC 2.0 upgrade (Q4 2024) incorporated maximum Byzantine fault tolerance security and a forensics monitoring system. A Cancun Hard Fork v2.6.8 (January 2026) aligned XDC with Ethereum's latest protocol changes. Utila integration provides MPC-driven institutional custody, and Elliptic support adds enterprise-grade AML/KYC monitoring.","heading":"Network Metrics and Technical Upgrades","severity":"low","sources":[{"credibility":2,"name":"XDC Network: Growth Accelerates in North America","type":"official","url":"https://xdc.org/articles/xdc-network-growth-accelerates-in-north-america"}]},{"content":"XDC Network has relatively limited independent media coverage and public scrutiny compared to its market cap. No major security incidents, exploits, or regulatory actions were found during this investigation. The absence of controversy may reflect the project's enterprise-focused positioning and lower retail profile, but it also means less independent verification of claims. The project's reliance on official sources for key metrics warrants additional third-party verification.","heading":"Limited Independent Coverage","severity":"medium","sources":[{"credibility":2,"name":"CoinMarketCap: XDC Network","type":"other","url":"https://coinmarketcap.com/currencies/xdc-network/"}]}],"sources_used":[{"credibility":2,"name":"Bitrue: XDC Founder","type":"news_article","url":"https://www.bitrue.com/blog/get-to-know-xdc-network-founder"},{"credibility":2,"name":"XinFin: About","type":"official","url":"https://xinfin.org/about"},{"credibility":2,"name":"XDC: U.S. Regulatory Progress","type":"official","url":"https://xdc.org/articles/u.s.-regulatory-progress-and-native-usdc-headline-xdc-network-growth-in-2025"},{"credibility":2,"name":"XDC: North America Growth","type":"official","url":"https://xdc.org/articles/xdc-network-growth-accelerates-in-north-america"}],"summary":"XDC Network is an enterprise-grade, EVM-compatible Layer-1 blockchain co-founded in 2017 by Atul Khekade and Ritesh Kakkad through XinFin, focused on trade finance, payments, and RWA tokenization. The mainnet has been operational since 2019 with 801M+ transactions processed and 178K+ smart contracts deployed. XDC 2.0 upgrade (Q4 2024) introduced Byzantine fault tolerance security. ISO 20022-aligned for institutional interoperability. Co-founders operate a $125M XVC Tech investment fund. No major security incidents or regulatory actions found. Limited independent media coverage and relatively low public scrutiny for its market cap.","timeline":[{"date":"2017-01-01","event":"XDC Network co-founded by Atul Khekade and Ritesh Kakkad through XinFin","source":"xinfin.org","source_url":"https://xinfin.org/about"},{"date":"2019-06-01","event":"XDC mainnet launches, operational since","source":"xdc.org","source_url":"https://xdc.org/"},{"date":"2024-10-01","event":"XDC 2.0 upgrade introduces Byzantine fault tolerance and forensics monitoring","source":"xdc.org","source_url":"https://xdc.org/articles/u.s.-regulatory-progress-and-native-usdc-headline-xdc-network-growth-in-2025"},{"date":"2026-01-01","event":"Cancun Hard Fork v2.6.8 aligns XDC with Ethereum's latest protocol changes","source":"xdc.org","source_url":"https://xdc.org/articles/xdc-network-growth-accelerates-in-north-america"}]},"v":1}Verify offline (run on your own machine)python -m src.verify_decision 9c83e446-ef86-43d5-a8bd-96b4c58781c0 - #2reviewby reviewerreviewer2026-06-05 15:00:33ZScore: 62 → 62 (no score change)The XDC Network investigation page is largely accurate and supported by independent sources, with one factual error: the XDC 2.0 upgrade occurred on September 30, 2024 (Q3), not 'Q4 2024' as stated. The co-founder listing is partially misleading, as Karan Bhardwaj departed the company in 2018 and is no longer listed on official channels. The page's heavy reliance on official XDC/XinFin sources limits independent verification, and coverage gaps around token distribution, validator centralization, and audit history are notable given the enterprise-focused positioning.anchoranchored
- chain
- ●mainnet-betaslot 424,483,235
- sig
5aho6DGJRGqT…GudAwrvUexplorer ↗- hash
3SoKRZrCMWMX…kmR2Ai1csha256 → base58
verifying row…full verify ↗canonical bytes (919 B) ▸
{"actor":"reviewer","decided_at":"2026-06-05T15:00:33.605Z","decision":"review","investigation_id":"fc145b64-1335-4b3c-aafe-fffa9096e641","new_score":62,"page_slug":"xdc-network","prev_score":62,"reason":"The XDC Network investigation page is largely accurate and supported by independent sources, with one factual error: the XDC 2.0 upgrade occurred on September 30, 2024 (Q3), not 'Q4 2024' as stated. The co-founder listing is partially misleading, as Karan Bhardwaj departed the company in 2018 and is no longer listed on official channels. The page's heavy reliance on official XDC/XinFin sources limits independent verification, and coverage gaps around token distribution, validator centralization, and audit history are notable given the enterprise-focused positioning.","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 d5c279be-cc06-401e-866f-ae2cef77edc6 - #3review approveby judgejudge2026-06-05 15:00:33ZScore: 62 → 62 (no score change)The review found 10 of 14 claims confirmed, 2 partially supported, and 1 disputed, yielding a disputed_pct of 7% — within the 0-10% approval band. The sole disputed claim (claim_findings[6]) is a minor date classification error: the XDC 2.0 upgrade occurred on September 30, 2024 (Q3), not Q4 as stated on the page. The two partially supported claims (claim_findings[0] and claim_findings[11]) reflect a co-founder who departed in 2018 being listed without qualification, and a slightly imprecise characterization of Elliptic's scope — neither rises to a material factual dispute. Three high-priority coverage gaps around token distribution, validator concentration, and source independence are noted and warrant future expansion, but open coverage gaps do not require denial or revision under current policy.anchoranchored
- chain
- ●mainnet-betaslot 424,483,237
- sig
xiZ9bZ9CqrBq…z8ehPxTXexplorer ↗- hash
Ea83hCucZDGR…D3dGJUAksha256 → base58
verifying row…full verify ↗canonical bytes (1161 B) ▸
{"actor":"judge","decided_at":"2026-06-05T15:00:33.605Z","decision":"review_approve","investigation_id":"fc145b64-1335-4b3c-aafe-fffa9096e641","new_score":62,"page_slug":"xdc-network","prev_score":62,"reason":"The review found 10 of 14 claims confirmed, 2 partially supported, and 1 disputed, yielding a disputed_pct of 7% — within the 0-10% approval band. The sole disputed claim (claim_findings[6]) is a minor date classification error: the XDC 2.0 upgrade occurred on September 30, 2024 (Q3), not Q4 as stated on the page. The two partially supported claims (claim_findings[0] and claim_findings[11]) reflect a co-founder who departed in 2018 being listed without qualification, and a slightly imprecise characterization of Elliptic's scope — neither rises to a material factual dispute. Three high-priority coverage gaps around token distribution, validator concentration, and source independence are noted and warrant future expansion, but open coverage gaps do not require denial or revision under current policy.","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 357462f3-95bd-4059-a960-919cb642b9a6
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>.