error get torus key when 1 node Die ( only on Ios, android work well )
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- android, ios, react-native
- Domain
- mobile
Research direction
Start from the issue report and the linked Web3Auth discussion, then reproduce the Torus Key retrieval flow on iOS with nine nodes and one node unavailable. Compare the result with Android; done means the key is retrieved when five of nine nodes remain available.
Written by the indexing model from the issue text.
Description
It should 5 out of 9 nodes are enough to retrieve Torus Key, but when 1 node die I can not get torus key
Same Problem on this discussion :
https://github.com/orgs/Web3Auth/discussions/1129#discussioncomment-4502644
- Dominant language
- Java
- Stars
- 9
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MetaMask/customauth-react-native-sdk
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Typescript support? Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
MetaMask/customauth-react-native-sdk#29 · 1 comment ·
All issues in MetaMask/customauth-react-native-sdk
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100