> For the complete documentation index, see [llms.txt](https://docs.getrekt.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getrekt.trade/docs/cross-chain-deposits.md).

# cross chain deposits

GetRekt's deposit asset is native USDC on Sui. Ethereum and Base are intended source networks for CCTP V2 transfers. A cross-chain transfer changes where native USDC is held; it does not directly open a trading position.

## Burn, attest, receive

{% stepper %}
{% step %}

## Confirm transfer details

Confirm the source network, native USDC contract, receiving Sui address and route limits.
{% endstep %}

{% step %}

## Authorize and burn USDC

Authorize the permitted CCTP spender and burn the chosen source-chain USDC amount with the correct destination domain and recipient encoding.
{% endstep %}

{% step %}

## Wait for attestation

Wait for Circle's attestation for that burn message.
{% endstep %}

{% step %}

## Submit the attested message

Submit the attested message to the configured Sui CCTP receive path.
{% endstep %}

{% step %}

## Verify USDC and open separately

Verify the resulting native Sui USDC and its owner, then separately sign the GetRekt open transaction.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Circle's attestation service and the source and destination chains are external dependencies. A submitted burn is not proof that the recipient has spendable Sui USDC. The receiver must validate the message, destination, recipient, token, amount and replay status. [Circle CCTP documentation](https://developers.circle.com/cctp).
{% endhint %}

## Source and destination gas

Ethereum or Base transactions need gas on their respective source network. Receiving and trading on Sui need SUI gas unless a verified sponsor explicitly pays it. CCTP transfer fees, finality and available modes must come from the current route configuration, not a hardcoded promise of instant or free transfers.

{% hint style="info" %}
Testnet routes use Sepolia and Base Sepolia to Sui testnet. The repository's limited zero-fee Standard test mode is an explicit development mode, not evidence of production fee support or a successful end-to-end transfer.
{% endhint %}

## Why there is no CREATE2 deposit address

The Sui flow receives a native Coin at the intended Sui recipient. It does not clone Papertrade's EVM per-user CREATE2 deposit proxies. A wallet address, deployment object ID and CCTP recipient field are different identifiers; the UI must not interchange them.

## Tracking and recovery

Preserve the source transaction hash, message identifier, attestation state and destination transaction digest. After an interrupted session, resume from verified chain state. Reusing an already consumed message must not mint another payment; blindly burning again can create a second transfer.

The complete user-owned burn → Sui receive → GetRekt open flow still requires testnet evidence. [Deposits and withdrawals](broken://pages/de1a2eeca92448704c708abcce1333975b188af9) explains the supported asset and current release gates.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.getrekt.trade/docs/cross-chain-deposits.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.