battlechain
BattleChain Development Standards
Instructions for working with BattleChain, from the Cyfrin security team.
What is BattleChain
BattleChain is a ZKSync-based L2 blockchain that inserts a battle-testing phase between testnet and mainnet: Dev -> Testnet -> BattleChain -> Mainnet. Protocols deploy audited contracts with real funds, whitehats legally attack them for bounties under Safe Harbor agreements, and surviving contracts promote to production.
Networks
| Network | Chain ID | RPC | Explorer | CAIP-2 | Status |
|---|---|---|---|---|---|
| BattleChain | 626 | https://mainnet.battlechain.com | https://explorer.mainnet.battlechain.com/ | eip155:626 |
Live — production network |
| BattleChain Testnet | 627 | https://testnet.battlechain.com | https://explorer.testnet.battlechain.com/ | eip155:627 |
Live — tooling default |
Both networks have a block explorer with an API and contract verification (mainnet API: https://block-explorer-api.mainnet.battlechain.com/api, testnet API: https://block-explorer-api.testnet.battlechain.com/api). The mock dependency contracts (tokens, Chainlink, Uniswap, etc.) are testnet-only. battlechain-lib tooling defaults to testnet; set NETWORK=mainnet to target mainnet.