web3privacy / web3privacy/explorer-data
Update/Simplify W3PN score
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 35
- Forks
- 63
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 7
Description
- Add decaying score (score should decay differently depending on the stage of dev lifecycle they're in(research- score decays quicker here, development, pre-release/testnet, mainnet score decays slower here)
- Put more weight on easily verifiable information (e.g. location of documentation, communication channels)
- Put less weight on difficult to verify information (e.g. function of protocol, software assumptions, privacy assumptions)
- Remove certain scoring parameters that hold less value/more difficult to verify
- update the anonymous team contributor score (make it so it doesn't hurt a project if their team is anon)
- rethink regulatory compliance category scoring
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 names no files, tests, or entry points. Start by locating the W3PN scoring implementation, then define the revised lifecycle decay, verification weights, anonymous-team handling, and regulatory-compliance rules before implementing and validating the updated score.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100