Minerva
  • Minerva Wallet
  • Roadmap
  • Positions - Join our Team
    • Sen. Android Developer
    • Jr. Android Developer
    • Growth & Community Manager
    • Community Moderator
    • Project Manager
    • PR & Marketing Lead
    • Sen. iOS Developer
    • Jr. iOS Developer
    • Security Researcher
    • Product Manager
    • Business Developer
  • Official Tester Program
  • FAQ
  • Comparisons
    • AlphaWallet
  • MIVA & Gnosis Chain
    • MIVA SuperToken
    • How to get xDai
      • (1) Move DAI from Binance Smart Chain (BSC)
      • (2) Ramp Network
      • (3) AscendEX (Bitmax)
      • (4) Move DAI from Ethereum Mainnet
      • (5) Move DAI from Polygon
      • (6) xDai Faucets
      • (7) Friendship
  • Legal
    • Terms of Service
    • Privacy Policy
  • Technical
    • HD Key-Derivation
Powered by GitBook
On this page

Was this helpful?

  1. Technical

HD Key-Derivation

The derivation paths used for HD Key-Derivation are important in case someone needs to recover from a seed phrase only and if particular private keys should be imported to other wallets, e.g. Metamask.

Minerva uses three derivation paths:

Identities (DIDs) -> m/73'/0'/0'/index Main Networks -> m/44'/60'/0'/0/index Test Networks -> m/44'/1'/0'/0/index

This clear distinction allows Minerva to avoid any mixing of indexes for identities (DIDs), main networks (e.g. Ethereum, ARTIS ∑1 or xDai Chain) and test networks (e.g. Kovan, Rinkeby or Görli).

If the Minerva seed phrase (12-words) is imported to Metamask, it will generate the same keys and consequently the same addresses for main networks.

Metamask won't be able to access your tokens and coins you handled in Minerva on the test networks like Kovan, Rinkeby, Görli, etc. unless you use another tool to get a private key for the account at a specific path and import that into Metamask.

PreviousPrivacy Policy

Last updated 4 years ago

Was this helpful?