EVM Account

Q: Why my Polkadot account will be bound with a default EVM address after a claim on dApp？

In Acala, once you receive an ERC20 asset, your Polkadot account will be bound with a default EVM address if it is not bound to any EVM address yet. Since Taiga reward distributor is deployed as the smart contract in Acala EVM+, and you will receive reward assets after claiming, your Polkadot account will be bound with a default EVM address unless you have already bound it with another EVM address.

Q: How is the default EVM address generated?

It’s generated as hash of ‘evm:<your Polkadot address>’.

Q: Can I use the generated default EVM address in MetaMask?

Unfortunately no. This is because your default EVM address is generated from your Polkadot address. The seed phrase of the default EVM address is unknown to anyone, so you can’t add it to your MetaMask. However, it can be still used in Polkadot.js applications.

Q: Can I bind my Polkadot address if it’s already bound to the default EVM address?

Unfortunately no. Once your Polkadot address is bound to an EVM address, it could not be bound to another address. If you want your Polkadot address to bind to your existing EVM address, you can do it before your first claim, or create a separate Polkadot address. It’s easy to switch between multiple Polkadot addresses.

Q: How is the security to bind EVM address with Polkadot account?

The security of neither your EVM address nor your Polkadot account is compromised. Binding them together allows you to manage your assets in either MetaMask or Polkadot.js, but they have their own seed phrase and they don’t introduce security risks to each other.