> ## Documentation Index
> Fetch the complete documentation index at: https://developers.circle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure an ownerless token

> Set up a crosschain bridge for an existing ERC-20 using CCTP for non-USDC's ownerless token model.

After configuration, anyone can bridge the token between the home blockchain and
any destination you deploy to, without bridge governance or ownership.

## Prerequisites

Before you begin, ensure that you've:

* Deployed the ERC-20 on the home blockchain with the same number of decimals
  you intend to use on every destination
* Noted the
  [`CrossChainTokenService` address](/cctp/expanded-assets/references/contract-addresses)
  for the home blockchain and each destination blockchain
* Obtained access to the Iris fee-quote endpoint
  (`POST /v2/quote/cctpx/{tokenId}/{sourceDomain}/{destinationDomain}`)

<Warning>
  Configure the token as ownerless on exactly one blockchain—the home blockchain
  where the token's supply originates. On every other blockchain, CCTP for
  non-USDC deploys a wrapped `CrossChainToken` automatically. Configuring the same
  token as ownerless on more than one blockchain will lock supply on each with no
  mechanism to release it.
</Warning>

## Step 1. Configure the token on the home blockchain

Call
[`registerOwnerlessToken`](/cctp/expanded-assets/references/contract-reference)
on the local service with the token's address. Submit the transaction and wait
for confirmation, then read the deterministic `tokenId` from the service.

```typescript TypeScript theme={null}
const txHash = await walletClient.writeContract({
  address: serviceAddress,
  abi: serviceAbi,
  functionName: "registerOwnerlessToken",
  args: [tokenAddress],
});

await publicClient.waitForTransactionReceipt({ hash: txHash });

const tokenId = await publicClient.readContract({
  address: serviceAddress,
  abi: serviceAbi,
  functionName: "getOwnerlessTokenId",
  args: [tokenAddress],
});
```

Save the returned `tokenId`. You will use it in every subsequent step and in
every crosschain transfer. Quote remote deploys with this `tokenId`; using a
placeholder or sentinel in the Iris path causes `QuoteArgsMismatch`.

## Step 2. Quote and deploy the wrapped token on each destination

For each destination, fetch a fee quote from Iris, then call
[`deployRemoteOwnerlessToken`](/cctp/expanded-assets/references/contract-reference)
on the home service. Pass the original token address, the destination domain ID,
and the fee `claim`.

Include a `FORWARD` request with `msgType: "DeployTokenMessage"` so the quote
covers destination deploy gas and Circle can deliver the message. Iris still
expects a positive `amount` string even for deploys.

```typescript TypeScript theme={null}
const quoteRes = await fetch(
  `${IRIS_BASE}/v2/quote/cctpx/${tokenId}/${sourceDomain}/${destinationDomain}`,
  {
    method: "POST",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({
      amount: "1",
      feeToken: zeroAddress,
      requests: [
        {
          type: "FORWARD",
          params: {
            msgType: "DeployTokenMessage",
            autoExecuteHookData: false,
          },
        },
      ],
    }),
  },
);
if (!quoteRes.ok) throw new Error(await quoteRes.text());
const { signedQuote, feeTotalAmount } = await quoteRes.json();

const claim = {
  signedQuote,
  refundAddress: zeroAddress, // or your refund address
};

await walletClient.writeContract({
  address: serviceAddress,
  abi: serviceAbi,
  functionName: "deployRemoteOwnerlessToken",
  args: [tokenAddress, destinationDomain, claim],
  value: BigInt(feeTotalAmount),
});
```

This call sends a CCTP message that, when delivered, creates a remote
`CrossChainToken` wrapper and `TokenManager`. That wrapper is a new protocol
deployment; it is not the same contract as a native copy of your token that may
already exist on the destination.

Omit `FORWARD` only if you will self-relay in the next step.

## Step 3. Complete delivery (forwarded or self-relay)

How the deploy lands depends on the quote:

* **With `FORWARD`:** Circle typically submits `receiveMessage` on the
  destination. Poll until
  [`resolveTokenAddress`](/cctp/expanded-assets/references/contract-reference)
  returns a non-zero address on the destination service.
* **Without `FORWARD`:** Poll Iris
  `/v2/messages/{sourceDomain}?transactionHash=…` until the attestation is
  complete, then call `receiveMessage` on the destination `MessageTransmitterV2`
  yourself. See
  [Attestation Verification](/cctp/references/attestation-verification).

## Step 4. Verify the remote contracts

Once the destination has processed the message, look up the wrapped token and
its `TokenManager` on the destination service:

```typescript TypeScript theme={null}
const remoteTokenManager: `0x${string}` =
  await destinationPublicClient.readContract({
    address: destinationServiceAddress,
    abi: serviceAbi,
    functionName: "resolveTokenManager",
    args: [tokenId],
  });

const remoteToken: `0x${string}` = await destinationPublicClient.readContract({
  address: destinationServiceAddress,
  abi: serviceAbi,
  functionName: "resolveTokenAddress",
  args: [tokenId],
});
```

## Step 5. Rederive the `tokenId` from the token address

You can rederive the ownerless `tokenId` from a token address on the home
blockchain at any time:

```typescript TypeScript theme={null}
const tokenId: `0x${string}` = await publicClient.readContract({
  address: serviceAddress,
  abi: serviceAbi,
  functionName: "getOwnerlessTokenId",
  args: [tokenAddress],
});
```

Before the first outbound transfer, confirm the remote `TokenManager` rate limit
is non-zero; `rateLimit: 0` blocks all outbound transfers. See
[Configure rate limits and transfer caps](/cctp/expanded-assets/howtos/configure-rate-limits-and-caps).