Implement On-Chain Bounty Status Sync and Event Listener

[0xdevcollins]

Feature: On-Chain Bounty Status Sync and Event Listener

Overview

The Bounty Registry contract emits events for all state changes (BountyCreated, BountyApplied, BountyAssigned, WorkSubmitted, SubmissionApproved, BountyClaimed, BountyCancelled, etc.). The frontend needs to listen to these events for real-time status updates and data consistency between on-chain and off-chain state.

Depends on: #139 (TypeScript contract bindings)

---

Goals

• Sync frontend bounty state with on-chain contract state
• Listen to contract events for real-time updates
• Reconcile GraphQL data with on-chain truth
• Handle state conflicts gracefully

---

Contract Events

BountyCreated { bounty_id, creator }
BountyApplied { bounty_id, applicant }
BountyAssigned { bounty_id, assignee }
WorkSubmitted { bounty_id, submitter }
SubmissionApproved { bounty_id, winner }
BountyClaimed { bounty_id, claimer }
BountyCancelled { bounty_id, reason }
SplitApproved { bounty_id, amount }
ApplicationRejected { bounty_id, applicant }

---

Implementation Details

1. Contract Event Poller

Create: lib/contracts/event-listener.ts

• Poll Stellar RPC for contract events at interval
• Parse event topics and data
• Dispatch to relevant query cache invalidations

2. On-Chain Status Verification Hook

Create: hooks/use-onchain-bounty.ts

• useOnChainBounty(bountyId) — reads directly from contract
• Compare with GraphQL data for consistency
• Show "verified on-chain" indicator

3. Transaction Confirmation Tracker

Create: hooks/use-transaction-status.ts

• After submitting a transaction, track confirmation
• Show pending → confirmed → finalized states
• Link to Stellar explorer for verification

---

Files Affected

Created

• lib/contracts/event-listener.ts
• hooks/use-onchain-bounty.ts
• hooks/use-transaction-status.ts
• components/bounty/onchain-status-badge.tsx

---

Acceptance Criteria

• Contract events trigger UI updates
• On-chain status readable for any bounty
• Transaction confirmation tracked after submission
• Status conflicts between GraphQL and on-chain detected

[linear]

BOU-157

[coderabbitai]

🔗 Related PRs

#41 - feat: add websocket client module [merged]
#55 - feat-Implement Bounty Status Logic & Anti-Squatting [merged]
#110 - feat: Implement Earnings & Payout Tracking [merged]
#111 - Feat: implementation logic for single claim model [merged]
#117 - feat: add frontend hooks for submission mutations [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[WeberG619]

Hi,

Feature: On-Chain Bounty Status Sync and Event Listener

Overview

The Bounty Registry contract emits events for all state changes (BountyCreated, BountyApplied, BountyAssigned, WorkSubmitted,...

I'm a full-stack developer working across Python, C#, and TypeScript daily — building everything from REST APIs and database systems to desktop applications and automation pipelines.

What I deliver:

• Clean, tested code with proactive communication — no surprises
• Experience with TypeScript, API, AI/ML in production environments
• Fast turnaround — I typically have a working first version within days, not weeks

For [boundlessfi/bounties] Implement On-Chain Bounty Status Sync and Event Listener:
I'd start with a quick technical review of your requirements and existing code, then propose a concrete approach before writing a line. I focus on solutions that are easy to maintain after handoff.

Can start immediately. What's the current state of the codebase I'd be working with?

Weber Gouin

[zhaog100]

/attempt

[zhaog100]

/attempt