Do we have a standard derivation path that a wallet should use to create an Ark wallet? I checked the Spark docs and they have one defined for Spark
Correct me if I’m wrong, but both Second and Ark Labs seem to be using a single private key (not derived from mnemonic) to create the wallets? That makes it difficult when considering adding Ark support (even as an experimental feature) to an existing wallet
Our current API is designed to make it easy to integrate your own onchain wallet into bark. You can implement the traits in bark::onchain to achieve a strong integration.
The onchain wallet can you whatever derivation path you would like. It’s not fully clear to me why you would like to have a standard derivation path.
What problems would you like to solve?
I’m thinking about how to easily add Ark support to an existing wallet. For example, users already use a wallet with liquid and onchain balance, they have a single seed phrase that they have backed up, if we want to add Ark to it as well, how do we do it?
I’m familiar with Ark Labs’ Go and Typescript implementations, so I am assuming bark does something similar as well, where there is a single private key for all Ark related stuff
If yes, then how do we generate that private key from the seed phrase in a standard way
Also, the reason I want a standard derivation path is because I want the users to be able to access their Ark balance later if they want to move to some other wallet
I feel like I’m missing something here though
You can use the Wallet::create-function and provide your mnemonic.