- Add CHAIN138_XDC_ZERO_BRIDGE_RUNBOOK and 07-ccip pointer doc - Add config/xdc-zero templates, parent register fragment, README - Add merge-endpointconfig-chain138.sh (jq merge, XDC_ZERO_ENDPOINT_DIR) - Add xdc-zero-chain138-preflight.sh; trim XDC URL vars in load-project-env - Wire AGENTS.md, MASTER_INDEX, verify README, .env.master.example Made-with: Cursor
XDC Zero + Chain 138 — config templates
Templates for pairing DBIS Chain 138 with XDC Network mainnet JSON-RPC (https://rpc.xinfin.network, chain id 50) or Apothem/devnet, using the XDC-Zero Endpoint pattern, without replacing your existing subnet↔parent XDC-Relayer deployment.
| File | Purpose |
|---|---|
xdc-zero-chain138-pair.example.env |
Env vars for the second relayer pair (parent ↔ 138). Copy to a secure path; wire into XinFin relayer/docker or your own CSC updater. |
network.config.xdc-mainnet.example.json |
Example network.config.json for XDC-Zero endpoint/: XDC mainnet https://rpc.xinfin.network + LAN Chain 138. Merge or copy keys into your clone. |
endpointconfig.fragment.chain138.example.json |
Top-level chain138 block to merge into XDC-Zero endpointconfig.json. Also append one object to existing xdcparentnet.registers[] for peer chain id 138 (see runbook). |
xdcparentnet-register-chain138.fragment.json |
Single registers[] entry (chain id 138) consumed by the merge helper for xdcparentnet. Replace zero addresses after CSC/Endpoint deploy. |
Merge helper (repo): bash scripts/xdc-zero/merge-endpointconfig-chain138.sh (requires jq).
Canonical procedure: docs/03-deployment/CHAIN138_XDC_ZERO_BRIDGE_RUNBOOK.md
Preflight: bash scripts/verify/xdc-zero-chain138-preflight.sh
Upstream repos (clone separately): XDC-Zero, XDC-CSC, XDC-Relayer.