# Tezos CCIP DON Onboarding – Prerequisites

Phase 1 prerequisites for onboarding Tezos (Etherlink and Tezos L1) into the CCIP DON and cross-chain architecture.

## 1. Etherlink CCIP Verification

### 1.1 Verification steps

1. Check CCIP supported networks: https://docs.chain.link/ccip/supported-networks. Search for Etherlink or chain ID 42793.
2. If Etherlink is listed: record CCIP chain selector, Router address on Etherlink, supported tokens, fee token. Proceed with CCIP path (receiver bridges, addDestination, LINK).
3. If Etherlink is not listed: document as custom relay only. Receiver interface: relay-compatible (accepts relay-submitted txs that mint/unlock). See smom-dbis-138/docs/relay/ARCHITECTURE.md. Deploy only relay-compatible receiver on Etherlink; run off-chain relay.

### 1.2 Current status

Until verified externally, assume custom relay only for Etherlink and implement Etherlink relay runbook and receiver interface accordingly.

## 2. Jumper API Support

Verify Jumper API/SDK supported chains for 138, 651940, 42793, Tezos. Document in TEZOS_JUMPER_SUPPORT_MATRIX.md. If Jumper does not support those chains, use LiFi plus direct adapter/CCIP only.

## 3. Tezos L1 Relay Interface

Event schema, confirmTransaction, and oracle key handling: see smom-dbis-138/docs/bridge/TEZOS_L1_RELAY_RUNBOOK.md. Tezos-side mint/transfer spec and oracle key handling documented there.

## 4. Config and Env Freeze

Config/env matrix: TEZOS_NETWORK_CONFIG_ENV_MATRIX.md (138, 651940, 42793, Tezos). Approval: Engineering lead (config freeze); Product/ops (CCIP vs custom relay, Jumper vs LiFi scope).