How to add Etherlink (42793) and Tezos L1 to token list and UniversalAssetRegistry for cross-chain bridging.
## Allowed destinations (BridgeRegistry)
- **Etherlink**: chainId **42793**. Already in default destinations in VaultBridgeIntegration, eMoneyBridgeIntegration, WTokenBridgeIntegration. When registering tokens with BridgeRegistry or integration contracts, include **42793** in allowedDestinations (or use default).
- **Tezos L1**: chainId **1** in BridgeRegistry (non-EVM slot). Include **1** in allowedDestinations for tokens that may bridge to Tezos L1.
- **Etherlink (42793)**: Add a token list or extend existing list with tokens that have `chainId: 42793`. Same structure as other chains: chainId, address, name, symbol, decimals. File location: follow project [TASK5_TOKEN_LIST_HOSTING](../deployment/TASK5_TOKEN_LIST_HOSTING.md) and [ADDING_NEW_ASSET_TYPE](../guides/ADDING_NEW_ASSET_TYPE.md) and token-lists layout; add or reference a list that includes 42793.
- **Tezos L1**: Uniswap token list is EVM-only (chainId + address). For Tezos-origin or wrapped-on-Tezos assets, document in registry/metadata; BridgeRegistry destination 1 does not require a token list entry for Tezos-native assets. For EVM-side wrapped representations of Tezos assets (if any), use the chainId of the EVM chain where the wrapped token lives.
## UniversalAssetRegistry
- Register new tokens (Etherlink/Tezos wrapped or origin) in UniversalAssetRegistry with appropriate AssetType and ComplianceLevel.
- Use governance (submitTokenlistVersion + timelock via TokenlistGovernanceSync) to add tokens; or register directly with REGISTRAR_ROLE if policy allows.
- Ensure BridgeRegistry and integration contracts (VaultBridgeIntegration, eMoneyBridgeIntegration, WTokenBridgeIntegration) allow **42793** and **1** in allowedDestinations. Defaults already include 42793; for Tezos L1 include 1 when registering tokens.
## TokenlistGovernanceSync
- If token list schema is extended (e.g. new chainIds 42793 or metadata for Tezos), extend TokenlistGovernanceSync or submission process to support new chainIds/metadata. Current flow: submitTokenlistVersion(major, minor, patch, ipfsHash, newTokens, metadata). Ensure metadata includes chainId/destination info where needed.
