🎃 Hacktoberfest Project Hub: DID DHT #292
Description
📦 Project Hub
🚀 Goal
We've created this hub of tasks for the community to get involved with DID DHT. This set of issues focuses specifically on items to help streamline & future-proof did-dht.
🤝 Pick ONE of the following issues to contribute to this project
❗You must only assign yourself one task at a time to give everyone a chance to participate.❗
You may assign yourself your next task after your current task is reviewed & accepted.
🚫 You must not steal an issue assigned to another person. If you submit a PR for an issue not assigned to you, you will not receive points. 🚫
We've broken down the developer website into smaller tasks. Feel free to take on any task that interests you. Every contribution counts!
Each subtask is detailed in its own issue. Please refer to the individual issues for specific requirements and acceptance criteria.
👍 Enhancement
- Consider a standardized log format for DHT history #266
- Replace BoltDB with sqlite #121
- Support for optional user-hashed names #77
- Consider internode gossip protocol #20
- Add universal resolver driver #18
- Store historical records #16
- Support type indexing #13
- Handle publishing old data #12
🐛 Bugs
- [Bug] The spec abstract does not provide a summary of how the DID method works #279
- [Bug] Modify caching strategy to better utilize cache space and distribution of resources. #274
🧪 Testing
🤖 Server
- Support introspecting NS records to determine if the gateway is authoritative #199
- Support DID Resolution metadata as part of the resolution API #145
- Generate server scaffold from OpenAPI spec #104
- Support for retention configuration #73
🤺 Discussion
- Disclosable DID DHT Documents #147
- Consider changing config from TOML #116
- Explore the potential for using threshold signatures with the Identity Key #101
🎊 Hacktoberfest
This project is part of Hacktoberfest! We welcome contributions from technologists of all skill levels. Here's how you can get started:
- Read the contribution guidelines
- Read the code of conduct
- Choose a website-specific task from the list above
- Comment ".take" on the corresponding issue to get assigned the task. Please assign yourself to one task at a time.
- Fork the repository and create a new branch for your work
- Make your changes and submit a pull request
- Wait for review and address any feedback
Have questions? Join our Discord community!
🌟 Resources
Happy coding, and thank you for contributing to our developer website! 🙌