Address convention in UI

For EVM compatibility layer we use addresses that was inherited from Ethereum, this mean that internally its 20bytes, EVM Jsonrpc are compatible with Ethereum, and use hex encoding for Velas EVM addresses.

But for historical reasons, to avoid users mistakes in most of UI we use Base58 encoding with checksum, with prefix 'V'.

Examples:

Address in EVMAddress in UI
0x32Be343B94f860124dC4fEe278FDCBD38C102D88V5dJeCa7bmkqmZF53TqjRbnB4fG6hxuu4f
0x000000000000000000000000000000000000000fV111111111111111111111111112jSS6vy

In order to support this encoding, we have library on various languages, that one can used as reference implementation: https://github.com/velas/velas-address-lib .

Both addresses has no conflicts, and can be supported simultaniously.

All tools that receive user inputs should support this convention.