Bounty Hunter — D App

function challengeAndArbitrate() external // calls to Kleros or UMA oracle

Abstract The traditional bounty hunting model—whether in software development (bug bounties), law enforcement (fugitive recovery), or digital content moderation—suffers from centralized control, opaque fund disbursement, and high intermediary fees. This paper proposes a decentralized application (DApp) architecture for bounty systems using smart contracts. It examines the shift from reputation-based, centralized escrow to trustless, code-enforced agreements. Key components include on-chain task definition, collateral staking, proof-of-completion oracles, and automated reward distribution. 1. Introduction Bounty hunting, in its digital form, involves a poster (seeking a task) and hunters (performing verifiable actions). Centralized platforms (e.g., HackerOne, Upwork) act as arbiters, taking 15–30% fees and holding funds. A bounty hunter DApp replaces the intermediary with a smart contract on a blockchain (e.g., Ethereum, Solana). bounty hunter d app

function approve(address _winner) external onlyPoster claimed = true; payable(_winner).transfer(reward); Centralized platforms (e

function submitProof(bytes32 _proofHash) external require(!claimed); submissions[msg.sender] = _proofHash; Centralized platforms (e.g.