w3f / polkadot-wiki

The source of truth for Polkadot.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Add derivation path standards

laboon opened this issue · comments

This information belongs on the https://wiki.polkadot.network/docs/learn-account-advanced#derivation-paths page

You can get the text from Gav's Hackmd here: https://hackmd.io/@polkadot/rJ5nxXAHn

Isn't this just how Polkadot Vault handles Derivation? I would not add a section "standard derivation", but rather add a section about how vault/signer handles derivation. Would this be ok?

Isn't this just how Polkadot Vault handles Derivation? I would not add a section "standard derivation", but rather add a section about how vault/signer handles derivation. Would this be ok?

I think that it's actually how subkey and "polkadot-js apps" handle derivation. It's possible that Vault handles it the same way, but I'm not certain.

As someone who has been trying to learn about these things, I couldn't agree more with @laboon: this information definitely belongs into that section 💯

EDIT

The document starts with the following sentence:

All paths as per subkey standard.

🙂