TokenManager and CrossChainToken contracts are deployed per token. To
discover their addresses for a given tokenId, call
resolveTokenManager and
resolveTokenAddress on
the CrossChainTokenService for the local domain. For contract interfaces and
method signatures, see
CrossChainTokenService Interface.
Token approvals
Each token has its ownTokenManager on each domain, and that TokenManager
moves the token during a transfer. CrossChainTokenService instructs the
TokenManager to pull tokens from the sender. A TokenManager that uses the
BURN_MINT configuration is granted the minter role on the token, so it can
pull and burn tokens on behalf of the protocol.
For every transfer, you must still approve the TokenManager to spend your
tokens. Call approve on the token with the TokenManager address returned by
resolveTokenManager(tokenId) as the spender, not the CrossChainTokenService
address. Mainnet TokenManager addresses for supported tokens are listed in
TokenManager. For the full flow, see
Transfer EURC between Base and Arc.
Mainnet contract addresses
CrossChainTokenService
Mainnet CrossChainTokenService is deployed via CREATE3 at the same address on
each listed chain.
TokenManager
Each token’s mainnet TokenManager is deployed at the same address on every EVM
blockchain where the token is supported. Approve this address as the spender
before you call crossChainTransfer.
Testnet contract addresses
CrossChainTokenService
Sandbox CrossChainTokenService is deployed via CREATE3 at the same address on
each listed testnet.
Underlying CCTP contracts
CCTP for non-USDC routes messages through the existing CCTPMessageTransmitterV2 contract on each domain. The CCTP for non-USDC domain ID
matches the
CCTP domain ID
for the same blockchain. For MessageTransmitterV2 addresses, see
CCTP Contract Addresses.