dbd517b279
- Update dbis_core, cross-chain-pmm-lps, explorer-monorepo, metamask-integration, pr-workspace/chains - Omit embedded publish git dirs and empty placeholders from index Made-with: Cursor
1.9 KiB
1.9 KiB
OP Stack L2 ↔ Besu Chain 138 — integration notes
Last updated: 2026-04-01
Purpose: Optional follow-on after a Standard Rollup L2 is live on Ethereum. Not part of superchain-registry listing. Does not extend XDC-Zero unless you design a separate pairing.
Architecture reminder
| Network | Stack | Role in DBIS landscape |
|---|---|---|
| Besu Chain 138 (EIP-155:138) | Besu + contracts + XDC-Zero | Core DBIS chain; XDC parent ↔ 138 via XDC-Relayer pattern |
| New OP Stack L2 | op-node / op-geth + L1 Ethereum |
Superchain-aligned rollup; separate chain ID from 138 |
If you need asset or message flow L2 ↔ 138
-
Treat as a new bridge program — pick one or combine:
- CCIP (patterns in
smom-dbis-138/ ALL_MAINNETS_DEPLOYMENT_RUNBOOK.md) once router/onramps exist for your L2 chain id. - Custom lock/mint or canonical bridge contracts audited for your token policy.
- CCIP (patterns in
-
Update machine-readable config after addresses exist
config/token-mapping-multichain.json— add the L2 chain id and pairs.docs/11-references/CONTRACT_ADDRESSES_REFERENCE.md/ADDRESS_MATRIX_AND_STATUS.mdas your process requires.
-
Keep XDC-Zero scope clear
- XDC-Zero runbooks address XDC Network ↔ Chain 138.
- Do not repoint the 138↔XDC relayer to serve the OP L2 without a dedicated design review.
Ordering
Complete OP_STACK_STANDARD_ROLLUP_SUPERCHAIN_RUNBOOK.md through Phase 4 (registry) before investing in L2↔138 bridging.