Skip to content

Allow bounty payout to stored submitter profile wallet - #538

Merged
ralyodio merged 3 commits into
profullstack:masterfrom
evanbrown3000:fix/bounty-profile-wallet-fallback-20260819
Aug 19, 2026
Merged

Allow bounty payout to stored submitter profile wallet#538
ralyodio merged 3 commits into
profullstack:masterfrom
evanbrown3000:fix/bounty-profile-wallet-fallback-20260819

Conversation

@evanbrown3000

Copy link
Copy Markdown
Contributor

Fixes #534/#537 payout deadlock. uGig already stores validated profile wallet addresses for payer-side use without OAuth. Keep CoinPay OAuth wallets first; when OAuth wallet lookup is unavailable, fall back only to the approved submitter's own stored wallet matching the bounty payment currency. Existing paid/invoiced duplicate protections and creator-only authorization remain unchanged. Includes focused regression.

@ralyodio
ralyodio merged commit 86ff9a9 into profullstack:master Aug 19, 2026
6 checks passed
@evanbrown3000

Copy link
Copy Markdown
Contributor Author

LIVE_SETTLEMENT_COORDINATE_20260819

This PR is blocking a real existing payable coordinate right now: bounty c3137a9d-de39-4c1e-b48a-3df804c32bdf, submission 2c0db070-0507-4470-92ec-c4adc771457a, payout $1 USD in SOL. The seller already has a matching stored SOL profile wallet; live payout is still unpaid because the CoinPay OAuth client cannot provide wallet:read. Please merge/deploy this focused fallback if acceptable. I am polling only this existing submission and will count income only on provider paid plus transaction evidence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Invoicing permanently blocked: ugig requests wallet:read but the CoinPay OAuth client is not registered for it

2 participants