ObolNetwork / ObolNetwork/charon
Analyze the requirements necessary to set up up for web3signer based DKGs in future
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 222
- Forks
- 138
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 35
Description
🎯 Problem to be solved:
To analyze the requirements necessary to set up Web3Signer-based DKGs in the future.
https://github.com/ethereum/pm/issues/823#issuecomment-1631261567
🛠️ Proposed solution:
The Web3Signer team is looking to work with the community to standardize remote signing APIs in a new repository under github.com/ethereum. As part of this effort, they are analyzing the requirements for setting up Web3Signer based DKGs in the future. By gathering and documenting the requirements, the team aims to establish a solid foundation for developing and implementing Web3Signer-based DKGs.
Contributor 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.
Research direction
Start with the linked Ethereum discussion and the Web3Signer remote signing API effort described in the issue. Identify and document the requirements for setting up Web3Signer-based DKGs, including the relevant community and team expectations. Done means the requirements are collected in a clear, reviewable document; no source files or tests are named.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design, blockchain, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100