safient / safient-core Goto Github PK

Description:

• Fix minor issues of #7
• Abstract safe related functionalities using separate functions maintained in libs

Current workflow :

The Inheritor has to click on the safe after the claim has passed to manually update the claim stage to RECOVERING

Intended workflow :

Should automatically update the safe claim stage when the claim passes the arbitration.

Expected workflow:

1. Check if the a guardian sends a different secret and handle the exception on the contract verification
2. Allow the threshold guardian to excute the proof verification thereby making it a fair distribution of the funds among all the guardians who have recovered the secret. The guardian who excutes it get's his fee back

Current workflow:
Any guardian can submit the proof for incentivization.

Expected Workflow:
Delete the safe entry from the threadDB if the onchain transaction fails / Give the user an option to store the safe without having to do an onchain transaction.

Current Workflow:
The Safe data is written to threadDB even after the onChain transaction fails.