Hierarchical Deterministic TSS

[aboozaid]

I'm trying to implement a feature where I need to have a parent hd wallet (base address) and many child addresses from it. I think the difference between the normal HTSS and my use case is that I will have to generate different shares for every child address instead of using the one's of the base address which means when I need to sign a transaction of child address, I will have to use that child-address shares in order to get private key and then sign it which will not be scalable for the use case. Here is the image below which demonstrate what I want to implement

I checked the current bip32 but I have doubts to support that use case with supporting to ECDSA (BTC, ETH, ...) /EDDSA (Solana, ...). Any help or guidance is really appreciated.

Thank you for the awesome library!

[cychuang0924]

Hi aboozaid, @aboozaid
Currently, it is possible to support the derivation from a seed to child private keys.

First, it's important to understand the BIP32 process.

BIP32 defines the generation of a master key and the derivation of child private keys. Child private keys are classified into two types: hardened keys and non-hardened keys, depending on the index value. If the index >=2^31
, it is referred to as a hardened key; otherwise, if the index <2^31, it is called a non-hardened key.

With this basic concept in mind, consider a specific derivation path: m/44/60/0/0/0. This means that after generating the master key, you need to repeatedly apply child key derivation using index 44, index 60, and three iterations of index 0 to obtain the specified address. Therefore, in practice, you must iteratively apply the child derivation protocol. ref: https://github.com/getamis/alice/tree/master/crypto/bip32/child
or this new PR
#245

Here is our paper. More details maybe found here .

Currently, BIP32 only supports the 2-out-of-2 situation. As a result, you will end up with two shares corresponding to the derivation path. With these two shares, you can manage the assets specified by the path m/44/60/0/0/0.

Sincerely,
Chih Yun