web3privacy / web3privacy/explorer-data
Develop and deploy a separate trust score
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 35
- Forks
- 63
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 7
Description
- When was info last updated
- Who updated the info
- Have others verified this info is correct
- How many times/how often has this info been updated
- How can we make sure trust score isn't manipulated
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
Start by turning the five listed questions into agreed requirements and locating the repository area that stores the relevant information. Done should include a defined separate trust-score approach and deployment plan, but the issue names no files, tests, entry points, or acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100