Introduction

Developing blockchain Apps with IoTeX has never been more easy. If you are a familiar with Solidity and Web3js then you can start building on IoTeX straight away: grab your favorite Ethereum Tool, point it to a Babel Service (the Ethereum-Compatible IoTeX endpoint) and deploy your app in seconds.

IoTeX Address format

As IoTeX is not Ethereum though, you must pay a little attention to some small differences when using Web3 tools as a user or as a developer. One difference is in the wallet address representation: even though IoTeX and Ethereum use the exact same elliptic curve, called secp256k1 for wallets cryptography, given one private/public key pair IoTeX defines its own wallet address representation format, which is different from the Ethereum representation.

Let's look at an example, consider the following private key: 7fda34c8319534253619f69604ffbd43e315e319b84c03ea4f19e1a0e439a4b1

given the private key, using elliptic curve cryptography we cat derive the corresponding public key, which is valid both for Ethereum and IoTeX: 04ba460edf45c8855cccdec55583972dc9aaaee24513db5b4a1dc110b4a7af095a055a38ae679d178ec8cb3ed855aa2d6d23791b1c51eefc19a6da6ae4191cca80

Now, since blockchain addresses are basically just a compact representation of the public key, derived from it by applying a few transformations, the public key above becomes the following 0x.. address in Ethereum format:

0x95E20FD5FDd9A8D9D174C7fAE7c3F9eC51BBbF36

and the following io1.. address in the IoTeX format:

io1jh3ql40amx5dn5t5claw0slea3gmh0ek8flwlp

Both these addresses are nothing more than a different way of representing the same public key, and ultimately they correspond to the same private key.

Depending on which tool you are using for interacting with the IoTeX blockchain, you may have to convert between the IoTeX representation and the ethereum representation of the same account: Ethereum tools like Metamask or Truffle and libraries like Web3js as well as Solidity compilers expect addresses written the 0x.. Ethereum format. On the other hand, IoTeX tools like the ioPay wallet, or the iotex-antenna native SDK expect addresses written in the io1.. IoTeX format.

Address conversion and tools

Whenever it's required, you can convert between the two address representations at any time: you have many options to do that, let's see some:

Command line

On macOs and Linux you can install the IoTeX official command line client ioctl and use the ioctl account ethaddr command to convert any address in Ethereum or IoTeX address representation.

Web tools

You can use the official IoTeX web tools page to convert your address: just input your address in whatever format and you will get the other representation:

Other similar tools have been developed by the community that provide the same functionality, like the following one:

NodeJS package

If you are a javascript developer, you can easily integrate the address conversion functionality into your application by installing the following nodejs package:

# If using npm package manager
$ npm i @iotexproject/iotex-address-ts
# If using yarn package manager
$ yarn add @iotexproject/iotex-address-ts

then importing it in your code with:

import { from } from "@iotexproject/iotex-address-ts";
​
const addr = from("0xb8744ae4032be5e5ef9fab94ee9c3bf38d5d2ae0");
console.log(addr.string());
// io1hp6y4eqr90j7tmul4w2wa8pm7wx462hq0mg4tw
console.log(addr.stringEth());
// 0xb8744ae4032be5e5ef9fab94ee9c3bf38d5d2ae0
​
const addr2 = from("io1hp6y4eqr90j7tmul4w2wa8pm7wx462hq0mg4tw");
console.log(addr2.string());
// io1hp6y4eqr90j7tmul4w2wa8pm7wx462hq0mg4tw
console.log(addr2.stringEth());
// 0xb8744ae4032be5e5ef9fab94ee9c3bf38d5d2ae0

check out the GitHub repository here:

​