Technical Implementation

1. Owner Repository Flow

Owner Repository Flow

1. Buy $LAZY Token on the Platform

   • The owner repository (bounty maker) purchases $LAZY tokens to fund bounties for issues.

   • The tokens can be acquired through a swap mechanism available on the platform.

2. Create Issue & Bounty

   • The owner creates a new issue on GitHub that needs to be resolved.

   • They assign a bounty (reward in $LAZY tokens) to the issue to incentivize developers.

3. Merge the Pull Request

   • Once a developer submits a pull request (PR) with a solution, the owner reviews and merges it if it meets the required criteria.

4. Proof Submission to zkTLS via GitHub API

   • The GitHub API generates proof that the pull request has been merged.

   • This proof is sent to zkTLS (Zero-Knowledge TLS) Reclaim Protocol for validation.

5. Proof Validation & Smart Contract Notification

   • zkTLS verifies the authenticity of the merged PR proof without revealing sensitive data.

   • Once validated, zkTLS sends a verification signal to the smart contract.

6. Bounty Reward Distribution via Smart Contract

   • The Claim Issue Smart Contract processes the validated proof.

   • The bounty reward ($LAZY tokens) is sent to the developer’s wallet.

7. Developer Receives the Bounty

   • The developer successfully receives the bounty reward for their contribution.

   • The cycle repeats for new issues and contributions.

8. Developer Flow

Developer Flow

1. Connect to GitHub OAuth

   • The developer logs in and connects their GitHub account using OAuth authentication.

   • This grants access to the repository and allows interaction with the GitHub API.

2. Submit a Pull Request (PR) for an Issue

   • The developer creates a pull request (PR) to solve an issue listed on the platform.

   • The PR is submitted for review by the repository owner.

3. Pull Request Merged & Proof Sent to zkTLS

   • If the PR is merged, proof of the merge is retrieved via GitHub API.

   • The merge proof is then sent to the zkTLS Reclaim Protocol for validation.

4. zkTLS Generates & Validates Proof

   • zkTLS verifies the proof that the PR was successfully merged.

   • Once verified, zkTLS sends proof verification to the smart contract.

5. Claim Bounty Reward via Smart Contract

   • The Claim Issue Smart Contract processes the verified proof.

   • The developer can now claim the bounty reward ($LAZY tokens).

6. Developer Receives Bounty & Can Swap Tokens

   • The bounty reward is sent to the developer’s wallet.

   • The developer can swap $LAZY tokens for other assets or use them for further contributions.