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

# contract addresses

{% hint style="warning" %}
**There is no verified public GetRekt deployment to use yet.** Do not send assets to a sample address or infer a package ID from a code directory name.
{% endhint %}

| Deployment item                      | Sui testnet                             | Sui mainnet     |
| ------------------------------------ | --------------------------------------- | --------------- |
| Trading package and Vault            | Not published and verified in this book | Not deployed    |
| Governance package and configuration | Not published and verified in this book | Not deployed    |
| Admin multisig                       | Awaiting user-owned setup               | Not established |
| Oracle operator                      | Awaiting configured deployment          | Not established |
| Upgrade capability custody           | Awaiting verified transfer and receipt  | Not established |
| Transferable REKT Coin type          | Not issued                              | Not issued      |
| Referral registry and reserve        | Not implemented                         | Not implemented |

## What a verified release must publish

Publish the chain, package IDs, shared-object IDs, token types, upgrade authority, administrator multisig, fee recipient and oracle authority with their exact source revision. Include publish and initialization transaction digests, object ownership and the deployment manifest digest.

Circle's USDC and CCTP infrastructure addresses are separate from GetRekt's application contracts. Use network-specific official records and the validated integration configuration; an Ethereum address or mainnet Sui object cannot substitute for a testnet object.

Legacy repository paths such as `contracts/21x` and configuration names containing `only21m` are code identifiers, not deployment addresses. [Deployment guide](broken://pages/40327e07cf9941685d9d59b0bdf0eba4a1a55045) and [Wallet setup](broken://pages/55b2e884ebb2f1dd09fdf0e33ed80efbe523555e) describe the setup work that remains.


---

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