Teleporter Addresses

Deployed Addresses

1. Using Nick's method, TeleporterMessenger deploys at a universal address across all chains, varying with each teleporter Major release. Compatibility exists only between same versions of TeleporterMessenger instances. See Teleporter Contract Deployment and Deploy Teleporter to a Subnet for more details.

2. TeleporterRegistry can be deployed to any address. See Deploy TeleporterRegistry to a Subnet for details. The table above enumerates the canonical registry addresses on the Mainnet and Fuji C-Chains.

A Note on Versioning

Release versions follow the semver convention of incompatible Major releases. A new Major version is released whenever the TeleporterMessenger bytecode is changed, and a new version of TeleporterMessenger is meant to be deployed.

Due to the use of Nick's method to deploy the contract to the same address on all chains (see Teleporter Contract Deployment for details), this also means that new release versions would result in different Teleporter contract addresses. Minor and Patch versions may pertain to contract changes that do not change the TeleporterMessenger bytecode, or to changes in the test frameworks, and will only be included in tags.