Deploy Teleporter Registry
Deploy the TeleporterRegistry contract on your L1.
The TeleporterRegistry manages protocol versions for TeleporterMessenger. Since the messenger contract is non-upgradable, the registry provides a way to track and switch between different versions as the protocol evolves.
Why It's Needed
- Version management: As new versions of TeleporterMessenger are deployed, the registry keeps track of all versions and their addresses
- Required by ICTT: Interchain Token Transfer (ICTT) contracts reference the registry to find the correct TeleporterMessenger
- Future-proofing: dApps that use the registry can automatically benefit from protocol upgrades without redeployment
The registry takes the TeleporterMessenger address as a constructor argument and registers it as version 1.
Deploy on Your L1
Use the tool below to deploy TeleporterRegistry on your L1:
Builder Console
Checking requirements...
Save the Teleporter Registry address — you'll need it if you build dApps on top of ICM or set up token bridges.
Is this guide helpful?
