Sherpa Mode

[ASN-BitHyve]

What a Sherpa invitation will have:

1) An invitation code and a message. And then separately a 2FA. Same as gift or F&F request. 2) This invitation code can be derived from the short link we generate when sending a gift or a F&F request. The seed can be derived from the BIP 85 of the Sherpa’s Wallet. 3) The relevant data will be kept on the channel for the receiver to pick up. A seed, gift, dependent policies, other contact info, node details. 4) When the receiver puts in the code (before creating a new wallet), they will use the seed which is kept in the channel to create the wallet. Same as a new wallet creation but without generating a new seed. A Parent can have multiple Children, so it use BIP 85 to generate further seeds and knows which index the particular seed is used with. So their is an additional CTA on the F&F in the Parent app. “Show seed words”. This will be needed when the Child loses the wallet and wants to recover their wallet with the help of the parent. 5) The options for the Sherpa are: Backup - always yes. The parent can always help the child recover. View account - ability to see everything the child does in an account Sending restriction with a threshold (which can be 0). The default here should be that when the child wants to send a transaction, the Sherpa receives a notification that they have to approve, for the transaction to be processed.
Gift - add a gift to the invitation. Detaching policy. When can the child/ receiver detach. By default it will be only by the receiver but this can be changed?

Node - does the user connect to the Parent Node?

6) On the sender side, they will see the child as any other contact with the type “Dependent” (UI terms can vary but this will be the type in the code). Do we need to show them any differently? 7) They will also see an account for the contact with all stuff like a typical account but with the name of the other contact 8) On the child side when the put in the invitation they will see a clear description of the “Invitation conditions” which they have to agree to. 9) They will see the parent as a contact of the type “Sherpa” and they will have only one account. No LN or test account etc. Only 1 Checking Account. Their profile or the message will say that they are on a dependent wallet. 10) They can backup like normal. But have an additional option in the settings to go “independent”. Choosing this gives them a clear instruction of what this means and the steps they need to take. 11) This allows them to go completely on their own/ detach. This means a new wallet (user does not know but there is a transaction fee they have to agree to). And new backup (e.g. writing down the seed words again). 12) When in dependent mode, the child knows obviously that they have a dependent wallet and are shown this message at important times like when they are receiving or backing up.

Also, one of the policy items will be "Use my Node" - available only if you have your own node connected.

Adding User Flows to this

Sherpa Adobe XD link https://xd.adobe.com/view/3c65958a-a4a3-44d6-9112-3185c3024d6f-6936/

Tasks

• [ ] #5965
• [ ] Setup enc channel with relevant data and policies, create invite code
• [ ] Sherpa receiver: decrypt channel, accept policies, init wallet, tx flows
• [ ] #5944
• [ ] Node connect

[Deveshshankar]

Sherpa adobe Xd Link https://xd.adobe.com/view/3c65958a-a4a3-44d6-9112-3185c3024d6f-6936/ Note :- Few Things to be updated CC @mide66

[mide66]

Updated link- https://xd.adobe.com/view/81d78db1-c1a6-4f7d-974f-eb56167a821d-d484/