Chain Deployment Pipeline
This page describes how a new chain becomes operational in Concero V2.
Responsibilities matrix
| Workstream | Chain team | Concero team |
|---|---|---|
| Provide gas funding for deployment/ops wallets | Yes | No |
| Submit chain metadata PR | Yes | Review |
| Submit RPC metadata PR | Yes | Review |
Deploy ConceroRouter and supporting contracts | No | Yes |
| Configure relayer/verifier modules | No | Yes |
| Turn on production delivery | No | Yes |
Pipeline steps
1. Gas funding
Chain team funds required operational addresses.
2. Register network metadata
Chain is added in concero/v2-networks.
3. Register RPC metadata
RPC endpoints are added in concero/rpcs.
4. Deploy/upgrade core contracts
Concero deploys ConceroRouter (implementation + proxy) and required dependencies.
5. Configure modules
Concero configures production relayer and verifier modules for the new chain:
- relayer authorization,
- verifier signer/workflow/gas settings,
- destination routing checks.
6. Start off-chain services
Relayer and verifier workflows begin monitoring and processing for enabled routes.
7. Enable delivery path
Concero enables end-to-end route delivery for supported paths.
Important caveats
- Router deployment alone does not guarantee working message delivery.
- Route readiness depends on module authorization and off-chain workflow health.
- Current Concero-run relayer/verifier modules are admin-gated.
- Custom RPC selection via relayer/verifier metadata is planned but not available yet.