> 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/deposits.md).

# deposits

GetRekt accepts **canonical native USDC only**. USDT, USDC.e, wrapped assets, and tokens with the same display name are not accepted as native USDC. The Sui coin's complete type identifies the asset.

No GetRekt contract is currently available for public deposits, and neither cross-chain route has a completed end-to-end deployment record. The intended website, [getrekt.trade](https://getrekt.trade/), is not a deposit address. See [implementation status](broken://pages/c7eabe8af8c3f2ae7c1c1dce69dad717e5d1ac7a).

## Your Sui wallet

USDC stays in your wallet until you sign a position transaction. Cash positions consume a real `Coin<USDC>`; multiple Coins can be merged in the same transaction. The current implementation requires at least 1 USDC of margin per position, subject to price-quality and risk checks.

There is no separate custodial “platform balance.” Immediately payable settlements and funded FIFO claims return native USDC to the original user's wallet. Queued profits and $REKT rewards are separate balances and cannot be shown as withdrawable USDC.

## Ethereum and Base to Sui

The initial routes are Ethereum → Sui and Base → Sui. Tests use Ethereum Sepolia, Base Sepolia, and Sui Testnet. Support for another CCTP chain does not automatically enable a GetRekt route.

{% stepper %}
{% step %}

## Connect wallets and select bridge settings

Connect the EVM source wallet and Sui recipient wallet, then select an amount and maximum bridge fee.
{% endstep %}

{% step %}

## Check source details

Check the source chain, native USDC contract, balance, allowance, destination domain, and recipient. Approve only the required USDC amount.
{% endstep %}

{% step %}

## Refresh the quote and approve the burn

Refresh the bridge quote and approve the burn in the source wallet. Save the deposit intent before submitting it.
{% endstep %}

{% step %}

## Match the receipt and wait for attestation

Match the source receipt to the intended message and wait for a Circle Iris attestation.
{% endstep %}

{% step %}

## Validate and receive USDC

Validate the message, source evidence, and attestation, then receive through Circle's official Sui contracts.
{% endstep %}

{% step %}

## Verify the destination receipt

Verify the destination receipt, mint events, Coin owner, asset type, and received amount.
{% endstep %}

{% step %}

## Open a position

Once USDC is in the Sui wallet, sign a separate transaction to open a position.
{% endstep %}
{% endstepper %}

Sui's CCTP domain is 8. The adapter checks official packages, state objects, versions, network genesis, native USDC types, and remote messengers. Deployment references are listed in [Circle's Sui package documentation](https://developers.circle.com/cctp/references/sui-packages).

Circle's Sui handler delivers the minted Coin to the recipient. A completed bridge transfer does not automatically open a GetRekt position. See [Circle's Sui transfer flow](https://developers.circle.com/cctp/quickstarts/transfer-usdc-sui-arc).

## Gas and sponsored receiving

The source wallet pays Ethereum or Base gas. Sui receiving and trading require SUI unless an appropriate sponsor is active.

The repository contains a restricted receiving sponsor that accepts only the official Circle receive flow. It checks routes, quotas, duplicate requests, simulation, and persistent transaction records. It defaults to dry-run. No sponsor is currently operating, and position transactions do not have gas sponsorship.

A sponsor's response alone is not a deposit receipt. The client still checks the destination chain. A confirmed failure retains the message and transaction digest for recovery rather than repeatedly spending gas.

## Recovery

The interface can save and export the intent, source transaction hash, and bridge progress. Imported JSON is a recovery hint, not proof of payment; both chains must be checked again.

If a burn response is lost, inspect the source transaction before attempting another burn. If the Sui message nonce has already been consumed, recover the original receipt. The wallet controller also saves a Sui transaction digest before submission so that an unknown result can be reconciled before any new transaction is built.

Bridge fees, minimum received amounts, and transaction status must be shown before signing. Waiting for attestation or FIFO payment does not mean that cash is available.

## Withdrawals and other payment methods

Payable position settlements, fee claims, and FIFO payments return USDC on Sui. A reverse bridge to Ethereum or Base is not yet integrated into the interface.

CCTP moves USDC between chains; it does not convert bank balances or card payments into USDC. Fiat onboarding requires a separate provider and integration. See the [launch checklist](broken://pages/778926bacf8bfd7e0a0cce9f9bc284dec32ce34b).


---

# 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/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.