PolygonScan (Polygon)
Contract creator record
MessageTransmitterV2 on Polygon — check the creator field yourself.
0x81D40F21F1…4c464B64Proof
We don’t ask you to trust our claim.Follow the deployment trail yourself.
This is the most important page on the site. The strength of RETURN is not that we say an address belongs to Circle — it is that Circle publishes its own contract addresses, and anyone can trace those contracts back to a single deployer without asking us anything.
Destination address
0xadB384F7…b9E5A9D10xadB384F7fa7486422051D2a896417EAAb9E5A9D18
Sources checked
2
Circle contracts traced
Last re-checked 2026-08-27
The trail
Five steps, none of which start with us.
- 01
Circle publishes the addresses
Circle’s own developer documentation lists the production contract addresses for Cross-Chain Transfer Protocol V2. This is Circle’s publication, not ours.
Circle CCTP contract docs → - 02
Open the contract in a public explorer
Take TokenMessengerV2 at 0x28b5…cf5d, or MessageTransmitterV2 at 0x81D4…4B64, and look it up on any independent block explorer.
TokenMessengerV2 on Etherscan → - 03
Read the Contract Creator field
The explorer records which externally-owned account deployed that contract. This field is derived from chain history, not from a label anyone typed.
MessageTransmitterV2 on Etherscan → - 04
The creator resolves to one address
Both contracts resolve to 0xadB384F7fa7486422051D2a896417EAAb9E5A9D1. Two independent official Circle deployments, one deployer.
The deployer on Etherscan → - 05
Etherscan labels it independently
Etherscan attaches the public label “Circle: Deployer 2” to that address — a separate signal from the deployment history, pointing the same way.
View the label →
Proof 01
The public Etherscan label
Etherscan attaches a public label to this address: “Circle: Deployer 2”, categorised as a contract deployer associated with Circle. Labels are a useful signal, but they are one source and we do not rest the case on them — the rest of this page is what makes the label redundant.
0xadB384F7…b9E5A9D10xadB384F7fa7486422051D2a896417EAAb9E5A9D1Proof 02
Circle publishes the contract addresses itself
Circle’s developer documentation lists the production contract addresses for Cross-Chain Transfer Protocol V2. These are not addresses we selected — they are the ones Circle tells developers to integrate against. Everything downstream starts from Circle’s own publication.
TokenMessengerV2
0x28b5a0e9…8168cf5d0x28b5a0e9C621a5BadaA536219b3a228C8168cf5dMessageTransmitterV2
0x81D40F21…4c464B640x81D40F21F12A8F0E3252Bccb954D722d4c464B64Proof 03
TokenMessengerV2 → its creator
Look up TokenMessengerV2 in a public block explorer and read the Contract Creator field. That field is derived from the transaction that deployed the contract — it is chain history, not a label anyone can edit.
Official Circle contract
0x28b5a0e9C621a5BadaA536219b3a228C8168cf5dcreated by
0xadB384F7fa7486422051D2a896417EAAb9E5A9D1publicly identified as
Circle: Deployer 2
Proof 04
MessageTransmitterV2 → the same creator
One deployment could be a coincidence of tooling. A second, separate official Circle contract resolving to the same creator is what turns it into a pattern. The evidence does not depend on any single deployment.
Official Circle contract
0x81D40F21F12A8F0E3252Bccb954D722d4c464B64created by
0xadB384F7fa7486422051D2a896417EAAb9E5A9D1Proof 05
The same pattern across networks
Circle deploys CCTP to many EVM networks, largely at identical addresses. Where we have opened the explorer and read the creator field ourselves, the card below is marked Checked. Where we have not, it is marked Unchecked — the link is still there for you, but we are not going to present it as something we confirmed. We do not claim every network uses an identical deployment path.
Unchecked
Optimistic Etherscan (OP Mainnet)
Contract creator record
MessageTransmitterV2 on OP Mainnet — check the creator field yourself.
0x81D40F21F1…4c464B64WorldScan (World Chain)
Contract creator record
TokenMessengerV2 on World Chain — check the creator field yourself.
0x28b5a0e9C6…8168cf5dSonicScan (Sonic)
Contract creator record
MessageTransmitterV2 on Sonic — check the creator field yourself.
0x81D40F21F1…4c464B64SonicScan (Sonic)
Contract creator record
TokenMessengerV2 on Sonic — check the creator field yourself.
0x28b5a0e9C6…8168cf5dLineaScan (Linea)
Contract label
The same CCTP V2 addresses appear labelled as Circle CCTP contracts on Linea.
0x28b5a0e9C6…8168cf5dProof 06
Circle’s open-source repositories
Circle maintains public repositories under the circlefin GitHub organisation. evm-cctp-contracts is the official repository for EVM CCTP contracts and documents dedicated deployer keys and CREATE2 deployment. evm-gateway-contracts is the official Gateway repository and covers deployer accounts, owner addresses, fee-recipient addresses, offline signing and multisig signing.
This matters for a reason that cuts against overclaiming: Circle’s own configuration treats these as separate roles.
What this evidence does not show
DEPLOYER
Deploys the contract
OWNER
Holds the owner role
FEE RECIPIENT
Receives protocol fees
Circle’s Gateway .env.example defines GATEWAYWALLET_DEPLOYER_ADDRESS, GATEWAYWALLET_OWNER_ADDRESS and GATEWAYWALLET_FEERECIPIENT_ADDRESS as three distinct values. So: the address we send to is a contract deployer. It is not Circle’s treasury, not a donation wallet, not a fund, and not a revenue or fee-recipient wallet. We will not describe it as any of those things.
Circle Gateway mainnet contracts, for reference
Gateway Wallet
0x77777777…f11000eE0x77777777Dcc4d5A8B6E418Fd04D8997ef11000eEGateway Minter
0x2222222d…2C04C2050x2222222d7164433c4C09B0b0D809a9b52C04C205Sources
Every claim, with its receipt.
Each card names who publishes the fact, what kind of source it is, and exactly which claim it supports. Cards marked Checked were opened and read directly on the date shown.
Etherscan
Public address label
The destination address carries the public label “Circle: Deployer 2”.
0xadB384F7fa…b9E5A9D1Verify on EtherscanRead 2026-08-27
Circle Developers
Official documentation
Circle publishes TokenMessengerV2 and MessageTransmitterV2 as production CCTP V2 contract addresses.
Open Circle docsRead 2026-08-27
Etherscan (Ethereum)
Contract creator record
TokenMessengerV2 was created by 0xadB384F7fa7486422051D2a896417EAAb9E5A9D1.
0x28b5a0e9C6…8168cf5dCheck the creatorRead 2026-08-27
Etherscan (Ethereum)
Contract creator record
MessageTransmitterV2 was created by 0xadB384F7fa7486422051D2a896417EAAb9E5A9D1. A second, independent deployment pointing to the same address.
0x81D40F21F1…4c464B64Check the creatorRead 2026-08-27
BaseScan (Base)
Contract creator record
The same deployer created TokenMessengerV2 on Base — the pattern is not confined to one network.
0x28b5a0e9C6…8168cf5dCheck on BaseRead 2026-08-27
Circle (GitHub · circlefin)
Official source repository
evm-cctp-contracts is Circle’s official repository for EVM CCTP contracts, and documents dedicated deployer keys and CREATE2 deployment.
Open the repositoryRead 2026-08-27
Circle (GitHub · circlefin)
Official source repository
evm-gateway-contracts is Circle’s official Gateway repository, describing deployer, owner, fee-recipient, multisig and offline-signing roles.
Open the repositoryRead 2026-08-27
Circle (GitHub · circlefin)
Official role configuration
Gateway’s .env.example defines GATEWAYWALLET_DEPLOYER_ADDRESS, GATEWAYWALLET_OWNER_ADDRESS and GATEWAYWALLET_FEERECIPIENT_ADDRESS as separate values — deployer, owner and fee recipient are distinct roles.
Read the configurationRead 2026-08-27
Independence notice
RETURN is an independent, community-created token. It is not affiliated with, sponsored by, endorsed by, operated by or connected to Circle Internet Group, Inc., Arc, RadarDEX or any of their affiliates.
RETURN voluntarily and unilaterally sends a portion of its creator fees to 0xadB384F7fa7486422051D2a896417EAAb9E5A9D1 — a public address identified by Etherscan as “Circle: Deployer 2” and independently resolvable on-chain as the contract creator of official Circle CCTP contracts.
Circle has not requested, approved or acknowledged these transfers. Sending funds to an address does not create a relationship with whoever controls it, and no partnership, sponsorship, endorsement, benefit or expectation of benefit is implied by doing so.
A deployer address is not a treasury and is not a fee-recipient address. Circle’s own open-source configuration defines deployer, owner and fee-recipient as separate roles. We describe this address only as what the public record supports: a contract deployer.
Nothing here is financial advice, an offer, or a solicitation. Crypto assets are volatile and you can lose everything you put in. RETURN has no roadmap obligation, no guaranteed continuation of the Daily Return, and no expectation of profit is created by this page. Do your own research.