I want to use unified accounts for a Substrate-based EVM chain. I've looked into the mooonbeam implementation, and they are using it with a custom module pallet-author-inherent which is used for block authoring.

Is it possible to implement unified-accounts while using AURA for block authoring?

I've also checked the difference in source codes of both pallets and it turns out that AuthorInherent implements FindAuthor<T::AccountId> while AURA uses FindAuthor<u32>. Can anybody explain the difference and guide me where should I start if I want to use AURA instead of AuthorInherent for block authoring with unified-accounts?

Thank you!

1 Answer 1


Check Darwinia2.0. We are doing this now.


But for the session keys, it's still Sr25519. This is decided by AURA.

Key point: https://github.com/polkadot-js/apps/pull/8396.

  • I get this error the trait "From<sp_core::H160>" is not implemented for "AccountId32" when I set FromH160 as AddressMapping type.
    – Discardo
    Jan 13, 2023 at 5:29
  • I don't know where did you get this. Some code or link would be helpful. Jan 13, 2023 at 7:08
  • I'm getting this error on this line. Appreciate your help regarding this
    – Discardo
    Jan 13, 2023 at 7:21
  • github.com/Ali-Usama/EVM-Node-Template/blob/…. You are still using the AccountId32. You should change it to AccountId20 if you follow Moonbeam's solution. Jan 13, 2023 at 8:50
  • I've updated my genesis accounts to the Darwinia style here, but on the polkadot explorer there are still accounts with H256 addresses, please check here
    – Discardo
    Jan 19, 2023 at 19:17

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.