Equivalent for removed `legacyKeyLookup`
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- backend-api-design
Research direction
Start by reading the dropped legacyKeyLookup implementation and the related PR 132 comment, then trace the current GetPubKeyOrKeyAssign behavior. Done means providing an equivalent presence check that does not create a key when none exists, so callers can detect prior verifier key creation for migration logic.
Written by the indexing model from the issue text.
Description
Hi, as pointed out in this PR/comment we are looking for some equivalent of the dropped legacyKeyLookup method, i.e. a method that allows to check for the presence of a key in a verifierId without the call resulting in a creation of the key if it doesn't exist (which is currently the side effect of GetPubKeyOrKeyAssign call). Is there any such method, and if not, could you please introduce it?
Our usecase is detection of whether a user has ever created a key on a verifier or not and based on that we have some custom migration logic
Related comment/PR: https://github.com/torusresearch/torus.js/pull/132#issuecomment-2222242439
- Dominant language
- TypeScript
- Stars
- 23
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
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/torus.js
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in MetaMask/torus.js
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
openzim/mwoffliner#2933 ·
Maintainers usually reply within 1 day
-
Use the README category name for website links and submissionsPossibly taken @dajiaohuang claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
birobirobiro/awesome-shadcn-ui#647 ·
Maintainers usually reply within 2 days
-
check:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Urigo/accounter-fullstack#4604 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day