Background
The award-rtc GitHub Actions workflow scans PR body for the payout wallet on merge. Currently it matches a narrow phrase pattern. PR bodies that use different but valid phrasings get missed.
Concrete miss this session
@jonathanpopham PR #6541 + #6548 had Payout address if accepted: RTC4730a64f821a590972e8b37781fae5d568b5865c in the body. The auto-pay parser didn't catch this phrasing. Operator manual pay defaulted to github:jonathanpopham lazy-pay. Routing error required follow-up correction (75 RTC) + this tracking issue.
Required change
The PR-body wallet parser should match ANY of these patterns (case-insensitive):
Payout wallet: followed by RTC addressPayout address: followed by RTC addressPayout address if accepted: followed by RTC addressRTC Wallet: (capitalized) followed by RTC addressRTC wallet: (lowercase) followed by RTC addressWallet: (alone, if RTC address follows on same line)- Any line matching
RTC[0-9a-f]{40} if accompanied by labels like "payout", "wallet", "address"
Plus also match lazy-pay specifications:
miner ID for payout if accepted: followed by <id>miner ID: followed by <id>miner_id: followed by <id>
Verification
After the workflow change, a test PR body with each phrasing variant should successfully parse the wallet address.
Bounty
Low tier: 10 RTC at current $0.10 ref. The change is small (regex update in the workflow file + tests), but the value is real (prevents future routing misses + operator manual-pay overhead).
If you go beyond just adding the regex variants and audit the existing workflow for other parsing gaps (e.g., wallet in code blocks, multi-line bodies, edge cases), that's Medium (25 RTC).
Out of scope
- Adding a wallet-discovery API (separate concern)
- Changing wallet validation rules (RTC + 40 hex is fixed)
- Scanning bounty-claim comments (separate issue path)
Related
Surfaced during 2026-05-30 bounty sweep. Welcome to claim; comment your wallet (Payout wallet: RTCxxx… to test that variant).
Background
The
award-rtcGitHub Actions workflow scans PR body for the payout wallet on merge. Currently it matches a narrow phrase pattern. PR bodies that use different but valid phrasings get missed.Concrete miss this session
@jonathanpopham PR #6541 + #6548 had
Payout address if accepted: RTC4730a64f821a590972e8b37781fae5d568b5865cin the body. The auto-pay parser didn't catch this phrasing. Operator manual pay defaulted togithub:jonathanpophamlazy-pay. Routing error required follow-up correction (75 RTC) + this tracking issue.Required change
The PR-body wallet parser should match ANY of these patterns (case-insensitive):
Payout wallet:followed by RTC addressPayout address:followed by RTC addressPayout address if accepted:followed by RTC addressRTC Wallet:(capitalized) followed by RTC addressRTC wallet:(lowercase) followed by RTC addressWallet:(alone, if RTC address follows on same line)RTC[0-9a-f]{40}if accompanied by labels like "payout", "wallet", "address"Plus also match lazy-pay specifications:
miner ID for payout if accepted:followed by<id>miner ID:followed by<id>miner_id:followed by<id>Verification
After the workflow change, a test PR body with each phrasing variant should successfully parse the wallet address.
Bounty
Low tier: 10 RTC at current $0.10 ref. The change is small (regex update in the workflow file + tests), but the value is real (prevents future routing misses + operator manual-pay overhead).
If you go beyond just adding the regex variants and audit the existing workflow for other parsing gaps (e.g., wallet in code blocks, multi-line bodies, edge cases), that's Medium (25 RTC).
Out of scope
Related
Surfaced during 2026-05-30 bounty sweep. Welcome to claim; comment your wallet (
Payout wallet: RTCxxx…to test that variant).