Introduction
During the first Solana Community Validator Call of 2025, Chainflow hosted the team behind the DoubleZero protocol. Malbec Labs co-founders Mateo Ward and Andrew McConnell, along with Austin Federa, President of the DoubleZero Foundation, joined to demonstrate how DoubleZero works and answer questions from attendees.
What Is DoubleZero Network
The DoubleZero (DZ) protocol represents a decentralized, high-performance network framework designed to optimize communication in distributed systems, particularly blockchains. It enhances bandwidth, cuts latency, and removes jitter by combining unused private fiber links into a global, permissionless network.
The software package includes a CLI resembling the Solana CLI and a lightweight daemon connecting the host OS to the physical DoubleZero network. The team is actively working to open source their repository.
Current Status
DoubleZero operates in testnet across seven cities with concentrated Solana stake: Singapore, Tokyo, Los Angeles, New York, London, Amsterdam, and Frankfurt. Each location has a DoubleZero device providing connectivity through private bandwidth between city pairs.
The devices employ FPGA technology capable of handling transaction deduplication and signature verification before data reaches validator network interfaces. This hardware-level optimization reduces the computational burden on validators.
Connecting to DoubleZero
The connection architecture involves a bare metal server hosting validator software, switching infrastructure composing the physical network, and two AWS-hosted components the team plans to decentralize.
The connection process works as follows:
- Installation of the DZ daemon and CLI initiates connection to DoubleZero.
- Users call a smart contract via CLI, providing their public IP address.
- After signing the transaction from a devnet wallet, the system attempts connection.
- An activator service listens for activation events and assigns logical network resources.
- The controller orchestrates configuration delivery to devices.
- Agents on DZ devices request configuration updates and push them to network switches, creating new host OS interfaces and internet tunnels to the nearest device.
Q&A Highlights
Device Requirements
Operating a DZ device requires connecting Arista devices built to protocol specifications to point-to-point circuits (wavelength, L2, or L3), using existing capacity or lighting up dark fiber.
Transaction Safety
The DZ team ensures transaction integrity through publicly published statistics and code verification of deduplication logic, allowing independent assessment of duplicate identification and signature verification.
Network Contributors
The protocol aims to invite numerous operators contributing unused or over-provisioned network assets. Connectivity occurs through GRE tunneling, establishing link-local IP subnets between hosts and nearest DZ devices, with routing protocols announcing IP reachability.
Fallback & Censorship Prevention
A built-in fallback to the public internet exists from day one. For censorship prevention, the team plans to stream data and present dropped transaction information to the community, backed by economic security from links holding economic value.
Coverage Expansion
Network reliability depends on proximity to DZ nodes, incentivizing contributors to operate nodes where stake concentrates. Jumbo frames prevent fragmentation on the DZ network, and even though payloads target 1232 bytes, total packets reach 1500 bytes, avoiding fragmentation on the public internet.
Conclusion
DoubleZero represents a significant infrastructure innovation for Solana and distributed systems more broadly. By combining unused private fiber capacity with FPGA-based transaction processing, it offers validators a path to reduced latency, improved bandwidth, and hardware-accelerated deduplication. As the testnet expands and the team works toward decentralizing its remaining centralized components, DoubleZero's impact on Solana's validator economics and network performance will be an important development to monitor.
Governance that remembers. Institutional Memory as a Service.
Have thoughts or feedback on this research?
Othman@occresearch.org