web3privacy / web3privacy/explorer-data
How can users verify themselves for the reviewer portal
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 35
- Forks
- 63
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 7
Description
- Github account
- SSO
- Eth Wallet
- Other solution that is privacy preserving
- ZK-identity thats sybil resistant
- Codeberg account - will this maintain sybil resistance?
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.
Research direction
The issue does not name files, tests, or an entry point. Start by locating the reviewer portal's verification flow and documenting how GitHub accounts, SSO, Ethereum wallets, Codeberg, and privacy-preserving identity options would affect sybil resistance; done requires an agreed verification approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100