ZeroXBridge is a decentralized protocol that unlocks cross-chain liquidity from ETH (or any other L2 chain) to Starknet.
The protocol utilizes zk-STARKs proofs to verify asset deposits on the parent chain, removing the need for any centralized source of truth, as states can be reconstructed and verified by anyone on the blockchain. This has proven to be a major failure point in many previous bridge protocols.
Our V1 uses Stone, the prover, to generate proofs.
Weβre currently focused on iterating through technical phases that bring us closer to a fully functional, secure, and scalable launch.
π§ Technical focus on zk proof generation and sequencing logic
-
Develop and test deposit flow logic
- Generate proof for deposits on L1
- Publish proof to the registry
- Mint xZB on Starknet
-
Develop and test withdrawal flow logic
- Burn xZB on Starknet
- Generate withdrawal proof
- Redeem locked ETH on L1
-
Close sequencer and contract issues (11+ merged so far)
-
Resolve remaining technical blockers
-
Complete initial integration with Stone Prover
π Target: End of July 2025
π― Minimal working product: trustless L1 β L2 & L2 β L1 asset movement
- Public testnet release of deposit and withdrawal flow
- Enable token minting using zk proofs
- Gather feedback and iterate
- Initial developer documentation
π Target: Early August 2025
π° Ensure xZB maintains a strong peg and real utility
- Implement dynamic peg logic (targeting $1)
- Design redemption mechanisms
- Research risk mitigation to avoid depeg
- Begin economic simulation testing
π Target: Mid-August 2025
π§ββοΈ DAO-based management for protocol upgrades & xZB control
- DAO Initialization
- Voting mechanisms
- Treasury & multisig structure
- DAO tooling and testnet deployment
π Target: Late August 2025
π Ensure robustness of contracts and zero-knowledge flows
- Internal code review
- External smart contract audit
- Bug bounty program planning
π Target: September 2025
πΈοΈ Expand beyond Ethereum to support more parent chains
-
Integrate STwo prover
-
Implement bridging flows from:
- Optimism
- Base
- Arbitrum
-
Add L2-specific UI flows
π Target: After mainnet Phase 1 release
π’ Community-driven testnet with bug hunting, integrations, and marketing
- Public testing of all core features
- Begin integration with DeFi protocols
- Collect feedback from early users & devs
- Start grant & ecosystem outreach
π Ongoing after Phase 6
πΌ Secure long-term contributors and protocol sustainability
- Secure grants, strategic partners, or contributors
- Finalize mainnet deployment plan
- Prepare documentation & launch materials
π Post-audit & testnet stabilization