#1153 GitHub Tip Bot Integration

[createkr]

Summary

Build the GitHub tip bot integration for RustChain bounty and tipping workflows.

Why This Matters

This issue is really a workflow and trust problem, not just a bot script. If tipping via GitHub comments works cleanly, it creates a stronger contributor flywheel and makes RustChain payouts feel native to repository activity instead of manual and fragmented.

Scope

• process /tip @username <amount> RTC style commands in supported issue or PR comment contexts
• define how tip commands are parsed, validated, and rejected when malformed
• persist bot state so duplicate processing and payout drift are prevented
• verify webhook authenticity before any payout logic runs
• document wallet or payout configuration required by the bot
• provide tests covering parse, validation, idempotency, and failure cases
• document expected maintainer setup and operating model

Deliverable

A concrete GitHub tip bot implementation or spec-backed PR that safely parses supported tip commands, verifies events, persists state, and documents how maintainers run it.

Acceptance Criteria

• supported /tip command format is explicit and validated
• malformed or unauthorized commands are rejected cleanly
• webhook signature verification is implemented or specified concretely
• state persistence prevents duplicate or replayed payouts
• bot posts a clear confirmation or failure response back to GitHub
• payout wallet and maintainer configuration are documented clearly
• tests cover parsing, replay/idempotency, auth checks, and expected failure paths
• operating instructions are concrete enough for maintainers to run the bot without another spec pass

Non-Goals

• broad GitHub App platform work beyond this tipping workflow
• replacing the entire RustChain bounty payout system
• implementing unrelated GitHub automations
• UI polish or dashboard work outside the bot’s command and payout flow

Claim Routing

Use this issue for GitHub tip bot implementation and proof. If code lands in a separate service directory, Actions workflow, or supporting repo, link the PR back here. Keep payout and behavior discussion here unless the work is later split into child issues.

Notes

Existing target capabilities from the original bounty framing still apply:

• process /tip @username <amount> RTC commands
• persist state across runs
• use GitHub workflow or service automation as appropriate
• include security checks, tests, and documentation
• document payout wallet configuration

[algora-pbc]

Please visit Algora to complete your tip via Stripe.

[github-actions]

Welcome to RustChain! Thanks for opening your first issue.

New here? Check out these resources:

• CONTRIBUTING.md — how to earn RTC bounties
• Good First Issues — easy starter tasks (5-10 RTC)
• Bounty Board — all open bounties

Earn RTC tokens by contributing code, docs, or security fixes. Every merged PR gets paid!

1 RTC = $0.10 USD | pip install clawrtc to start mining

[Scottcjn]

Treating this as an umbrella/spec issue now that the GitHub tip bot work is split into narrower contributor tasks.

Implementation work should land through:

• #715 parse and validate /tip command syntax
• #716 persist tip state and prevent duplicate or replayed payouts
• #717 verify GitHub webhook signatures and authorize supported events
• #718 post GitHub confirmation comments and document maintainer setup

Use this parent issue to track the full integration scope, but claim or implement the child issues first.

[Scottcjn]

@createkr Only repository collaborators (write/admin/maintain) can issue tips.

-- RustChain Tip Bot