Batch and Parallel Contributor Refresh

This implementation provides production-ready code for batching and parallelizing contributor refresh operations in the refresh_bounty function.

Overview

The solution consists of:

1. Smart Contract (BountyRefresh.sol): Handles batch creation, parallel processing, and task management
2. Batch Manager (batchRefresh.js): JavaScript utility for managing batch operations
3. Comprehensive Tests (BountyRefresh.test.js): Full test coverage

Key Features

Batch Processing

1. Writes (create, claim, complete, dispute) are Soroban contract invocations. The frontend uses the SDK (or XDR built by the backend's /tx/* routes), and the user signs with their wallet.
2. Contract events (bounty_created, bounty_claimed, reward_paid, …) are polled by the indexer in mergemint-backend and stored in the database.
3. Reads come from the backend API: paginated lists, assignee filters, and a Server-Sent Events stream that pushes bounty updates to open clients.

See docs/architecture.md for contract data flow and storage layout.

Repository layout

Path	What it is	Stack
src/ (Cargo.toml)	The MergeMint Soroban contract: bounties, milestones, escrow, disputes, contributor reputation	Rust, soroban-sdk
mergemint-backend/	Event indexer and HTTP API (bounty lists, assignee filter, SSE stream, /tx/* transaction builders)	Rust, Axum, SQLx
backend/	Health-check endpoint logic (indexer lag, DB reachability, network passphrase validation)	TypeScript
frontend/	Main web app: bounty list/detail, create bounty, contributor profile, wallet connect	React, Vite, Vitest, Playwright
mergemint-frontend/	Lightweight React frontend package used by the root npm workspace	React, Vite, Vitest
app/	Reusable form components for the bounty and contributor flows (@mergemint/app)	React, TypeScript
sdk/	Typed TypeScript SDK wrapping the contract's XDR interface (@mergemint/sdk)	TypeScript, @stellar/stellar-sdk
contracts/bounty/	Batch/parallel contributor-refresh prototype (see docs/batch-refresh.md)	Solidity
test/	Hardhat tests for the batch-refresh prototype and bounty fixtures	JavaScript
scripts/	Deploy, smoke/integration tests, git hooks, k6 load scenarios	Bash, JavaScript
docs/	Design docs, guides and specs (index below)	Markdown
security/	Write-ups of specific security checks enforced by the contract	Markdown
.github/	CI workflows, Dependabot, issue and PR templates	GitHub Actions
.devcontainer/	Dev container with the Rust toolchain preinstalled	Dev Containers

Quickstart

Prerequisites

• Rust (stable) with the WASM target: rustup target add wasm32-unknown-unknown
• Stellar CLI: cargo install stellar-cli
• Node.js 20+ (for the frontends, SDK and lint tooling)

Or open the repo in the provided dev container.

Contract

make test     # run the contract test suite (no network needed)
make lint     # clippy (warnings as errors) + rustfmt check
make build    # build target/wasm32-unknown-unknown/release/mergemint_contracts.wasm

To deploy to testnet, follow docs/getting-started.md (create and fund a key, then make deploy). make bindings generates TypeScript bindings into sdk/generated/.

Backend

cd mergemint-backend
cargo run            # listens on http://localhost:8080
cargo test

API Reference

Contract Functions

createBatch(address[] contributors, uint256[] bountyIds)

Creates a new batch for processing.

• Parameters:
  • contributors: Array of contributor addresses
  • bountyIds: Array of corresponding bounty IDs
• Returns: Batch ID
• Events: BatchCreated

processBatchParallel(uint256 batchId)

Processes a batch with parallel execution.

• Parameters:
  • batchId: ID of the batch to process
• Events: ParallelRefreshStarted, TaskCompleted, TaskFailed, TaskRetried

finalizeBatch(uint256 batchId)

Finalizes batch processing.

• Parameters:
  • batchId: ID of the batch to finalize
• Events: BatchProcessingCompleted

npm install                  # root workspace + lint tooling
npm run dev:frontend         # start mergemint-frontend with Vite

cd frontend && npm install && npx vitest run   # main web app tests
cd sdk && npm install && npm run build         # build @mergemint/sdk

Before your first commit

./scripts/install-hooks.sh   # runs fmt, clippy, eslint and prettier on staged files

See CONTRIBUTING.md for branch naming, the PR process, changelog rules and test snapshots.

Documentation

Topic	Doc
Getting started on testnet	docs/getting-started.md
Stellar CLI troubleshooting	docs/troubleshooting.md
Contract architecture and storage layout	docs/architecture.md
Event schema	docs/event-schema.md
Horizon / RPC polling in the indexer	docs/horizon-polling.md
Integrations	docs/integrations.md
Security model	docs/security.md
Pause and upgrade strategy	docs/pause-upgrade-strategy.md
Escrow implementation plan	docs/escrow-implementation-plan.md
create_bounty parameter design	docs/create-bounty-params-design.md
Passkey authentication	docs/passkey-auth.md
Shared type generation	docs/shared-type-generation.md
Migrations	docs/migration.md
Benchmarks	docs/benchmarks.md
Batch and parallel contributor refresh	docs/batch-refresh.md
Backend load testing (k6)	scripts/k6/README.md
Contributor FAQ	docs/contributor-faq.md
SDK usage	sdk/README.md
Changelog (contract interface)	CHANGELOG.md
Backend changelog	mergemint-backend/CHANGELOG.md

Contributing

Contributions are welcome. Every PR should be tied to an issue, so start by opening or picking one up, then read CONTRIBUTING.md. If you think you've found a security issue in the contract, read docs/security.md first.

Handsoff notes

• #869: [Backend] Request ID middleware

• #1058: [Frontend] Sync bounty filters with URL query params