# Supported Accounts

Entangle supports two type of accounts EVM and Bech32. To navigate with the Bech32 address (with **ent** prefix) you can interact with the CLI commands outlined below.&#x20;

#### Converting Formats

You can convert between the HEX and Bech32 format like so:&#x20;

```bash
entangled debug addr <address>
```

#### Adding Keys

<pre class="language-bash"><code class="lang-bash"><strong>entangled keys add &#x3C;key_name> --keyring-backend file
</strong></code></pre>

#### Importing Keys

<pre class="language-bash"><code class="lang-bash"><strong>entangled keys add &#x3C;key_name> --keyring-backend file --recover
</strong></code></pre>

#### Exporting Private Keys

```bash
entangled keys unsafe-export-eth-key <key_name> --keyring-backend file
```

#### Querying Account Details

```bash
entangled q account <address> 
```

## Address Navigation

To navigate with HEX addresses you can use Metamask or other EVM wallets, with following parameters.

#### Entangle Mainnet

<table><thead><tr><th width="260">Category</th><th>Value</th></tr></thead><tbody><tr><td>Network Name</td><td>Entangle Mainnet</td></tr><tr><td>Default RPC URL</td><td>https://json-rpc.entangle.fi/</td></tr><tr><td>Chain ID</td><td>33033</td></tr><tr><td>Currency Symbol</td><td>NTGL</td></tr></tbody></table>

#### Entangle Testnet

<table><thead><tr><th width="260">Category</th><th>Value</th></tr></thead><tbody><tr><td>Network Name</td><td>Entangle Testnet</td></tr><tr><td>Default RPC URL</td><td>https://34.174.174.102:8545/</td></tr><tr><td>Chain ID</td><td>33133</td></tr><tr><td>Currency Symbol</td><td>NTGL</td></tr></tbody></table>


---

# 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://docs.entangle.fi/entangle-interoperable-blockchain/developer-guides/supported-accounts.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.
