Core Components
1. Owner Repository
The entity responsible for merging pull requests submitted by developers.
Has control over which contributions get accepted into the repository.
Ensures that merged pull requests meet the required standards before approval.
Plays a key role in the rewarding mechanism by determining valid contributions.
2. GitHub API
Used to fetch proof of merged pull requests.
Retrieves developer contributions, PR status, and merge history.
Provides data necessary for verifying whether a developer's PR has been accepted.
Acts as the bridge between GitHub and zkTLS validation.
3. zkTLS (Zero-Knowledge Transport Layer Security)
Validates the proof of merge retrieved from GitHub API.
Ensures that a developer's pull request was actually merged without exposing sensitive data.
Uses zero-knowledge proof (ZKP) to confirm the legitimacy of claims in a trustless manner.
Enhances security and prevents manipulation or false claims.
4. Smart Contract
A decentralized contract that holds issue data and bounty rewards.
Stores the list of open issues, their respective bounty amounts, and claim statuses.
Manages fund distribution, ensuring rewards are only given to developers with valid merged PRs.
Prevents manual intervention, making the reward process transparent and trustless.
5. Developer
Contributes to the repository by creating pull requests to solve issues.
Submits code improvements, bug fixes, or feature enhancements.
Must have their PR merged by the repository owner to be eligible for rewards.
Benefits from the bounty system by successfully validating their contribution through zkTLS.
Last updated