The Problem
Web3 has a fundamental gap in its development lifecycle. Traditional software has well-established staging environments where code is tested with production-like conditions. Web3 lacks this:
The consequences:
- Projects go from $0 to $5M TVL overnight after audit
- Bug bounties don’t attract serious testing (report vulnerabilities, don’t exploit them)
- The industry loses billions to preventable exploits
The Solution
BattleChain is a pre-mainnet, post-testnet environment with real funds. It’s an incentivized testnet where:- Protocols deploy audited contracts with real liquidity
- Whitehats legally attack contracts and earn bounties
- The DAO moderates to prevent abuse
How It Works
Every contract on BattleChain exists in one of two modes:Attack Mode
Open season for ethical hacking:- Whitehats can legally exploit vulnerabilities
- Safe Harbor agreement protects attackers
- Bounties paid for successful exploits
- Protocol learns about vulnerabilities before mainnet
Production Mode
Protected like mainnet:- No Safe Harbor protection for attacks
- Same security expectations as mainnet
- Regular bug bounty rules apply
The Flow
- Protocol deploys via
BattleChainDeployer - Protocol creates Safe Harbor agreement with bounty terms
- Protocol requests attack mode
- DAO reviews and approves (ensures not a mainnet copycat)
- Whitehats attack during the stress test period
- Protocol promotes to production when confident
Why an L2?
BattleChain runs as a ZKSync-based L2:- Isolation: Attacks don’t affect mainnet liquidity
- Branding: Clear distinction as experimental environment
- Protocol-level tracking: Contract states tracked at chain level
- Efficiency: Lower costs for deployment and testing
Who Should Use BattleChain?
Everyone. Whether you’re:- Launching a new protocol
- Adding features to an existing protocol
- Testing experimental DeFi mechanisms
- Stress testing AI trading bots