How threshold / requiredShares works based on different use cases

Help - Core-Kit tKey JS SDK
1
  • SDK Version: 12.0.0

Hello, I have a few questions about the tKey SDK, for both JS and React Native version (implementing the SDK on React website and React Native application).

These questions are based on the threshold system and the requiredShares.

  1. When the user logs in with the Service Provider (Share A), the requiredShares goes from 2 to 0. Is this the desired behaviour? If so, can you tell me why? I thought that regardless of the type of share (A, B, C), resolving 1 share would only reduce the requiredShares by 1, not more.
  2. Is there a different logic about the threshold / requiredShares between the user logging out and the user logging out + killing the mobile application? It seems that it doesn’t give the same result of requiredShares at the next login (sometimes it’s 1, sometimes 0).

To conclude, these 2 questions could be answered with a lifecycle diagram of threshold / requiredShares in different use cases (with shares A + B + C, only shares A + C, multiple shares C without A / B, when a user logs in, logs out, kills the application, clears the cache…) so we can understand the logic and adapt the login flow accordingly.

Thanks for your time, I hope it will help many of us!

1 Like
2

@quentin Welcome Aboard!

Your request has been forwarded to our Dev team and we will get back with an update on Monday.

1 Like