# Legacy Address convention

## Legacy Address convention

In EtherealNetwork chain 2.0 generation, we used to have Legacy Addresses (that always start with `V`). Those addresses essentially are 20 bytes Ethereum-like addresses but encoded differently on UI. The difference is that instead of a hex string prefixed with `0x`, the Legacy address is extended with checksum (4 extra bytes), encoded with Base58, and prefixed with 'V'.

'V' + base58(20-bytes-address + 4-bytes-checksum)

#### Examples:

| EVM Address                                | Legacy Address                     |
| ------------------------------------------ | ---------------------------------- |
| 0x32Be343B94f860124dC4fEe278FDCBD38C102D88 | V5dJeCa7bmkqmZF53TqjRbnB4fG6hxuu4f |
| 0x000000000000000000000000000000000000000f | V111111111111111111111111112jSS6vy |

Refer to this repository to get more details and snippets in some programming languages: <https://github.com/Ethereal/Ethereal-legacy-address-lib>


---

# 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://ethereals-blockchain.gitbook.io/ethereal-chain-documentation/evm-integration/legacy-address-convention.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.