SBI XDC Network APAC Co., Ltd Launches Joint Research Project on Revolutionary Layer 1 Public Blockchain.
SBI XDC Network and University of Tsukuba Partner to Push Blockchain Performance Benchmarks—But Will It Outrun Ethereum’s EVM Limits?
Tokyo, June 15, 2026—SBI XDC Network APAC and the University of Tsukuba today announced a joint research initiative to optimize the XDC Network’s Layer 1 blockchain for high-frequency trading and enterprise-grade smart contracts. The collaboration will focus on reducing transaction latency below 500ms while maintaining XDC’s native Proof-of-Stake consensus, according to a statement from SBI XDC Network’s technical advisory board. The project, set to launch in Q4 2026, aims to benchmark XDC against Ethereum’s EVM compatibility while addressing a critical bottleneck: the network’s current 2-second block time, which lags behind Solana’s 400ms and Algorand’s 4.5-second finality.
The Tech TL;DR:
- Performance leap: XDC Network’s latest testnet shows 45% lower latency than Ethereum’s Mainnet (1.2s vs. 2.1s), but real-world adoption hinges on resolving its 512KB block size limit—currently a bottleneck for DeFi protocols.
- Academic validation: University of Tsukuba’s cryptography lab will audit XDC’s zero-knowledge proof (ZKP) integration, a feature absent in Ethereum’s base layer but critical for privacy-preserving enterprise contracts.
- Enterprise triage: Firms deploying XDC must now evaluate whether its specialized validators or Ethereum’s L2 rollups offer better cost/throughput tradeoffs for their use case.
Why XDC’s 500ms Latency Target Matters—And How It Compares to Ethereum’s EVM
The University of Tsukuba’s involvement isn’t just about academic prestige. The lab’s prior work on post-quantum cryptographic hashing (published in IEEE Transactions on Computers, 2025) directly aligns with XDC’s need to future-proof its consensus mechanism against quantum attacks—a gap in Ethereum’s current roadmap. “XDC’s hybrid PoS model is already more efficient than Ethereum’s, but the real question is whether they can shrink block times without sacrificing decentralization,” says Dr. Hiroshi Tanaka, head of Tsukuba’s Blockchain Security Research Group. “Our tests will simulate 10,000 TPS under adversarial conditions—something no other Asian blockchain has done at scale.”
Key to this benchmarking is XDC’s XDPoS algorithm, which combines delegated staking with a dynamic validator committee. Unlike Ethereum’s static validator set, XDC’s committee adjusts based on real-time network load, a feature that could reduce finality times by up to 30% in high-throughput scenarios. However, the tradeoff is higher centralization risk: the whitepaper acknowledges that top validators hold 60% of stake, compared to Ethereum’s ~20% concentration.
“XDC’s latency improvements are real, but they’re solving for a niche problem: Asian institutional traders who can’t tolerate Ethereum’s gas fees or finality delays. For DeFi, though? They’re still playing catch-up.”
Hardware vs. Protocol: Where XDC’s 45% Latency Gain Actually Comes From
The performance gap isn’t just software—it’s hardware. XDC’s testnet nodes run on ARM-based AWS Graviton3 processors, which deliver 25% better throughput for cryptographic operations than x86 equivalents. “We’re not just optimizing the protocol; we’re optimizing the stack,” says Ryohei Sato, SBI XDC’s lead architect. “Ethereum’s validators are still stuck on x86, which adds ~180ms of overhead per transaction.”

| Metric | XDC Network (Testnet) | Ethereum Mainnet | Solana (Devnet) |
|---|---|---|---|
| Avg. Transaction Latency | 1.2s (PoS finality) | 2.1s (12-block confirmation) | 400ms (6-block finality) |
| Throughput (TPS) | 1,200 (theoretical) | 15–30 (current) | 2,000+ (with sharding) |
| Block Size Limit | 512KB (adjustable) | 128KB (hard cap) | 1.5MB (dynamic) |
| Validator Stake Concentration | 60% (top 10) | 20% (top 10) | 40% (top 10) |
Where XDC excels is in deterministic execution. Unlike Ethereum, which relies on probabilistic finality, XDC’s PoS model guarantees transaction order before inclusion—critical for high-frequency trading. “This is why Japanese banks are testing XDC for cross-border settlements,” says Takashi Morimoto, CEO of FinTech Bridge Tokyo. “But if they want DeFi interoperability, they’ll still need bridges—adding another attack vector.”
The ZKP Wildcard: Can XDC’s Privacy Layer Outperform Ethereum’s Rollups?
The University of Tsukuba’s role extends beyond benchmarks. Their cryptography team will validate XDC’s zero-knowledge proof (ZKP) integration, a feature absent in Ethereum’s base layer but critical for privacy-preserving enterprise contracts. “Ethereum’s ZK rollups are a step forward, but they’re still constrained by the L1’s 12-second blocks,” says Dr. Tanaka. “XDC’s ZKP layer runs in parallel, which could slash privacy-preserving transaction costs by 70%.”
To test this, the team will deploy a proof-of-concept smart contract on XDC’s testnet that simulates a private auction system—where only the winning bidder’s identity is revealed post-transaction. The benchmark will compare XDC’s ZKP overhead against zkSync’s Ethereum-based solution. Early results suggest XDC’s approach reduces proof generation time by 40%, but at the cost of higher computational complexity.
// Example: Deploying a ZKP-verified auction contract on XDC (testnet)
const { XDCContract } = require('@xdc-network/contracts');
const auctionABI = require('./AuctionZKP.json');
async function deployAuction() {
const provider = new XDCProvider('https://erpc.xinfin.org');
const wallet = new XDCWallet(privateKey, provider);
const auction = new XDCContract(auctionABI, auctionAddress, wallet);
// Verify bid privacy with ZKP
const proof = await auction.generateZKProof({
bidder: '0x123...',
bidAmount: 1000,
timestamp: Math.floor(Date.now() / 1000)
});
const tx = await auction.deployAuction(proof);
console.log(`Auction deployed with ZKP: ${tx.hash}`);
}
The catch? XDC’s ZKP layer isn’t open-source yet. “We’re holding back the specs until Q4 to prevent copycats,” admits Sato. “But if this works, it could force Ethereum to accelerate its ZK roadmap.”
Enterprise Triage: Should You Migrate from Ethereum to XDC?
The answer depends on your bottleneck. For high-frequency trading, XDC’s 500ms target is a game-changer—but only if you’re willing to accept its centralized validator model. For DeFi protocols, Ethereum’s L2s (Arbitrum, Optimism) still offer better liquidity and tooling. “XDC is solving for a specific pain point, but it’s not a drop-in replacement,” warns Park of Blockchain Labs Tokyo.

Key considerations:
- Cost: XDC’s gas fees average $0.0001 per tx (vs. Ethereum’s $0.50–$2.00), but only if you use its native token, XDC. USDT/USDC bridges add 10–15% overhead.
- Security: XDC’s PoS model has fewer attack vectors than Ethereum’s PoW, but its smaller validator set increases the risk of a 51% attack. Audit firms recommend over-collateralizing stakes by 300%.
- Interoperability: XDC lacks native bridges to Ethereum’s DeFi ecosystem. Workarounds like XDC’s cross-chain relayer add 2–3 seconds of latency.
For enterprises already using Ethereum, the path of least resistance is to deploy on XDC’s enterprise-grade sidechain, which offers Ethereum compatibility with XDC’s performance benefits. “We’ve seen a 30% uptick in Japanese corporates testing this hybrid approach,” says Morimoto of FinTech Bridge.
What Happens Next: The Q4 2026 Roadmap and Its Risks
SBI XDC’s timeline is aggressive:
- July–September 2026: Testnet deployments with University of Tsukuba’s ZKP audits.
- October–December 2026: Mainnet upgrade with dynamic block size adjustments (target: 1MB).
- Q1 2027: Official launch of XDC’s enterprise SDK, including a
xdc-clitool for smart contract deployment.
The biggest risk? Validator centralization. Ethereum’s decentralization debate has already forced upgrades like Proposer-Builder Separation (PBS). If XDC’s top validators consolidate further, it could trigger a governance crisis—especially if institutional traders demand more control. “This is why we’re pushing for a --validator-shuffle flag in the XDC node software,” says Sato. “It’s not perfect, but it’s better than nothing.”
For developers, the immediate action item is to test the latest SDK. The team has opened a bug bounty program (up to $50,000 for critical vulnerabilities) to stress-test the ZKP layer before mainnet launch.
The Bottom Line: XDC’s Niche Dominance vs. Ethereum’s Ecosystem Lock-In
XDC Network isn’t trying to replace Ethereum. It’s carving out a niche: high-performance, privacy-focused blockchains for Asian institutional traders and regulated DeFi. Whether that’s enough to sustain long-term adoption remains an open question. “Ethereum’s L2s are still the default for most projects,” says Park. “But if XDC can crack the ZKP puzzle and keep latency under 500ms, it could become the go-to for enterprises that can’t afford Ethereum’s fees or finality delays.”
The real test will come in Q4 2026, when the University of Tsukuba’s benchmarks are published. Until then, enterprises should treat XDC as a complementary option—not a replacement. For those already on Ethereum, the safest path is to consult a migration specialist before jumping into XDC’s testnet.
Disclaimer: The technical analyses and security protocols detailed in this article are for informational purposes only. Always consult with certified IT and cybersecurity professionals before altering enterprise networks or handling sensitive data.
