Skip to content

docs: claim error messages table + Mexico MXN polish #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cornerblue wants to merge 2 commits into
base: master
Choose a base branch
from
Open

docs: claim error messages table + Mexico MXN polish #33

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0d3098a
docs: claim error table + Mexico MXN cash-out section
cornerblue Jul 21, 2026
c4f53ea
docs: drop duplicate Mexico Part 4; keep claim table + LB LN notes
cornerblue Jul 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions ...ing-started/solving-a-bounty/claim-reward-criteria-and-troubleshooting-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -258,3 +258,24 @@ _Both steps are essential for successful reward processing_
{% endhint %}

For additional assistance, join the Lightning Bounties [Discord](https://discord.gg/zBxj4x4Cbq) community.

***

## Common platform error messages

| Platform message | Meaning | What to do |
|------------------|---------|------------|
| *Invalid pull request. Make sure it is merged into default branch.* | PR is still open, draft, or not merged to `main`/`master` | Wait for merge into the repository default branch, then claim again |
| *No winner found* | Issue not closed/linked, or claim not ready | Confirm PR body has `close #N`, issue is closed by the merge, then retry |
| Reward shows locked / claim does nothing | Lock time not finished (`unlocks_at` in the future) | Wait until the bounty unlocks, then claim |
| Logged in but claim fails for your PR | Different GitHub identity | Log out of Lightning Bounties and log in with the **same** GitHub account that opened the PR |

### Quick pre-claim checklist

1. PR shows **Merged** on GitHub into the **default** branch
2. PR description contains `close #<issue-number>` (not only a later comment)
3. GitHub issue is **Closed**
4. LB issue page shows **no Winner** trophy yet
5. Reward lock time has passed
6. You are logged into LB as the PR author

4 changes: 3 additions & 1 deletion getting-started/solving-a-bounty/how-to-convert-sats-into-local-currencies.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,7 @@ If you want to end up with MXN in a Mexican bank account, the common flow is:

### **4a. Choose an exchange that supports MXN withdrawals**

The exchange you choose should be able to:
Examples people in Mexico often use include Coinbase (where MXN is available) and Bitso. The exchange you choose should be able to:
- Hold an MXN balance
- Let you sell BTC -> MXN
- Withdraw MXN to a Mexican bank account (often via CLABE)
Expand All @@ -105,6 +105,8 @@ Rules, fees, and availability can change. If you are moving a meaningful amount,

### **4b. Deposit BTC to the exchange**

If you earned sats on Lightning Bounties, prefer a **Lightning deposit** when the exchange supports it (generate a LN invoice in the exchange, withdraw from LB). Otherwise:

1. Create a BTC deposit address in the exchange app.
2. Send BTC from your current wallet/exchange to that deposit address.
3. Wait for the deposit to confirm.
Expand Down