# Native \[migration to SUI]

## Links

* **Web**: <https://www.gonative.cc/>
* **Discord**: <https://discord.gg/MNZ4wnN3XM>
* **Github**: <https://github.com/gonative-cc/gonative/releases>

## **Details**

* **Network Chain ID**: native-t1
* **Binary**: gonatived
* **Denom**: untiv
* **Working directory**: .gonative

## Public services

* **Guide (RU)**: <https://teletype.in/@lesnik13utsa/Vj7SznlmE6n>
* **RPC**: <https://t-native.rpc.utsa.tech/>
* **API**: <https://t-native.api.utsa.tech/>
* **Explorer**: <https://testnet.native.explorers.guru/>

## Peering

You can use peer **lesnik | UTSA** for fast connection or state sync

```shell
peers="f82c497af58874eac7c862c362df9659d95f5332@5.9.87.231:60756"
sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \"$peers\"/" $HOME/.gonative/config/config.toml
```

The address book is updated once an hour. You can use it for quick launch

```shell
wget -O $HOME/.gonative/config/addrbook.json "https://share102.utsa.tech/native/addrbook.json"
```


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://utsa.gitbook.io/services/archive/native-migration-to-sui.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.