Inheritance Key: Dotting the i's and crossing the t's.

[ASN-BitHyve]

Inheritance Key setup (By benefactor):

While setting up the inheritance key the user is given the option to share their email with us.

When an inheritance key is used (By attacker or heir): (1) UAI should notify benefactor’s app that inheritance key is being accessed with the option to decline. (2) If benefactor has given an email, they should receive an email letting them know that access to inheritance key is being requested with an option to decline use.

Owners: UAI Implementation - Pratyaksh Email Implementation - Parsh Content - Abhilash

On the heir’s phone: When the heir tries to recreate the vault, one of the keys being inheritance key, the heir is told that they’ll have to wait 30 days for the vault to get created. At the end of the 30th day, the UAI should indicate that the Inheritance Key has been used and the vault has been recreated successfully.

Owners: UX - Summi. Implementation - Parsh Content - Abhilash UAI Implementation - Pratyaksh

Heir's phone: Signing a transaction using Inheritance Key - Each time the heir wants to use the Inheritance Key to sign a transaction, they will have to wait 30 days before they can. The incomplete transaction is visible in the Transactions screen in the vault. We also need to give the user the ability to delete the transaction itself.

Scenario of decline of use of the key:

On the heir or attacker’s phone: In case the use of Inheritance Key is declined, the UAI shows the message saying that the benefactor has declined the use of the Inheritance Key.

Owners: UAI -Pratyaksh Backend - Parsh Content - Abhilash

BAU - Manage Keys (Benefactor’s phone since the time they set IK up. Heir’s phone after 14 days):

1. User should be able to rotate out the Inheritance Key just like any other key.
2. User should be able to hide Inheritance Key
3. One time backup : This is a new CTA that will be available within the settings. When the user clicks on this button, they would be shown a modal talking about what IK+ is, what the user can and can’t do, what the user must and mustn’t do, and necessary cautions. CTA: “Proceed” and “Back”. On clicking proceed, the user is shown the seed words and taken through confirmation flow.

Owners: Backend - Parsh UX -Summi Content - Abhilash

[Parsh]

@ASN-BitHyve We'll probably need a flow, and the corresponding UX, for issue https://github.com/bithyve/bitcoin-keeper/issues/4127#issuecomment-2116612499 as well

[antuz123]

@Parsh - can you create what exactly you need UX for? My guess:

1. A temp transaction (for all keys, not just IK)
2. The signing screen (with IK waiting - this is already there, I think)
3. Not sure anything is needed in Health Check from UX stand point (email conf needed and server availability)

[Parsh]

As the UAI part for this issue is still pending, we're rolling it into the next release.

[pratyakxx]

@cakesoft-utkarsh can you confirm if the UAI decline flow is working or not.

[ASN-BitHyve]

Don't think I'm required here. Removing my assignment.

[Deveshshankar]

Closing this looks like an umbrella issue