fix event sequence issues between user_solution_commit and provider_approve #134

Activity

1. goastler commented on Feb 14, 2023

   

   goastler

   on Feb 14, 2023

   MemberAuthor

   More actions

   In short, a user submits a commitment to the contract and the provider and awaits the provider to approve or disapprove. However, between these two events (submit and approve/disapprove) there can be many other events occur which can disrupt the captcha process overall. For instance, after a user submits but before an approve/disapprove from a provider, the following could occur:

   1. provider deregister/unstake
   2. provider suspended
   3. provider payee change
   4. provider fee change
   5. provider balance changes below
   6. provider service_origin change
   7. provider dataset id / content id change
   8. dapp deregisters
   9. dapp becomes non-active
   10. dapp balance goes below threshold (stake_default)
   11. dapp owner change
   12. dapp client_origin change
   13. governance status for the contract changed, e.g. suspended
       etc

   We need to consider these occurrences during the captcha process, and adjust the contract to handle any of these occurrences.
2. goastler commented on Feb 16, 2023

   

   goastler

   on Feb 16, 2023

   MemberAuthor

   More actions

   deregister of provider needs to be changed to a request basis
3. prosopo

   locked and limited conversation to collaborators on Feb 16, 2023
4. forgetso

   converted this issue into a discussion #170 on Feb 16, 2023