We built this project to solve a trust gap in bounty-driven collaboration. In many communities, bounties are posted and completed, but it is often unclear:

who contributed what,

whether deliverables are authentic,

and whether rewards were distributed fairly.

We wanted a system where work, proof, and payouts are transparent by default. That inspired us to combine XRPL for on-chain state changes with Pinata/IPFS for content-addressed storage of submissions and evidence.

What we built We built a decentralized bounty and innovation platform where teams can create tasks, contributors can submit work, and reviewers can approve milestones with verifiable records.

Core flow:

A creator posts a bounty with milestones.

Contributors submit deliverables (files/metadata) stored on Pinata/IPFS.

The app records milestone and payout-related state updates on XRPL.

Anyone can verify both the content integrity and the on-chain history.

This transforms bounty coordination from “trust me” to cryptographic proof.

How we built it The app uses a three-layer architecture:

Application layer (frontend + backend logic): bounty creation, submission, review, payout flow.

Storage layer (Pinata/IPFS): stores user-generated deliverables and metadata as immutable CIDs.

Blockchain layer (XRPL Testnet/Devnet): records state-changing events (bounty lifecycle, approvals, payment actions).

Integrity model:

CID

H ( file or metadata ) CID=H(file or metadata) BountyEvent o n c h a i

n

{ bountyId , submissionCID , status , payoutRef , actor , timestamp } BountyEvent onchain ​ ={bountyId,submissionCID,status,payoutRef,actor,timestamp} If content is modified, the hash changes, so the original proof no longer matches. That gives us tamper-evident submissions tied to on-chain decisions.

Challenges we faced UX vs blockchain complexity: making wallet signatures and transaction finality intuitive for non-crypto users.

Asynchronous confirmations: handling pending/confirmed/failed states cleanly in the bounty workflow.

Off-chain/on-chain consistency: ensuring submission metadata and XRPL state transitions remain synchronized.

Testnet constraints: dealing with occasional faucet/network instability and building retries/fallback logic.

What we learned Bounty systems become much fairer when work proof and payout proof are both verifiable.

Content-addressed storage is ideal for preserving contributor ownership and auditability.

XRPL’s speed and low transaction costs fit high-frequency coordination flows like milestone updates.

Great dApps require product clarity as much as blockchain correctness.

Why this matters This project is a foundation for trustworthy bounty ecosystems: open-source funding, DAO task boards, community grants, and innovation programs where outcomes must be transparent and rewards must be accountable.

By linking submissions to immutable CIDs and recording bounty state changes on XRPL, we make collaboration more reliable for both builders and sponsors.

Built With

• css
• javascript
• pinata
• react
• ripple
• xrpl