ObolNetwork / ObolNetwork/obol-splits
Offer a secure, self-serve method for configuration validation
@samparsky is already working on this.
Since Sep 28, 2023.
- Dominant language
- Solidity
- Stars
- 17
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
🎯 Problem to be Solved
Users need to validate multiple aspects of their cluster configurations to ensure they match their expectations. The current setup is susceptible to trust issues due to potential Launchpad or NPM package compromise. It's important for the system to offer a secure, self-serve method for configuration validation.
🛠️ Proposed Solution
-
Create a dedicated
gettermethod on the factory smart contract. This function would return a struct containing all relevant cluster configuration data, including withdrawal address, fee recipient address, and reward split configuration. -
Implement a
viewfunction specifically for future-proofing and ease of user experience. This would be beneficial, particularly if the NFT-like approach to factories becomes prevalent.
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.
Assessment
This issue has not been assessed yet.