From e188f783e0afea84b7e1c183a794a235be3c090c Mon Sep 17 00:00:00 2001 From: Air <69623664+AirLabJP@users.noreply.github.com> Date: Sun, 17 May 2026 20:16:10 +0900 Subject: [PATCH 1/2] docs: add guide on converting sats to MXN for Mexican users --- SUMMARY.md | 1 + docs/solve-a-bounty/sats-to-mxn.md | 72 +++++++++++++++++++ ...w-to-convert-sats-into-local-currencies.md | 2 + 3 files changed, 75 insertions(+) create mode 100644 docs/solve-a-bounty/sats-to-mxn.md diff --git a/SUMMARY.md b/SUMMARY.md index 3773382..6d7bd8a 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -12,6 +12,7 @@ * [Withdrawing Funds](getting-started/solving-a-bounty/withdraw-funds.md) * [Working on Opensource Frontend: lb-next](getting-started/solving-a-bounty/working-on-opensource-frontend-lb-next.md) * [How to Convert Sats into Local Currencies](getting-started/solving-a-bounty/how-to-convert-sats-into-local-currencies.md) + * [Convert Sats to MXN (Mexico)](docs/solve-a-bounty/sats-to-mxn.md) * [POSTING A BOUNTY](getting-started/posting-a-bounty/README.md) * [Deposit Funds](getting-started/posting-a-bounty/deposit-funds.md) * [Create a GitHub issue and Submit a new reward](getting-started/posting-a-bounty/create-a-github-issue-and-submit-a-new-reward.md) diff --git a/docs/solve-a-bounty/sats-to-mxn.md b/docs/solve-a-bounty/sats-to-mxn.md new file mode 100644 index 0000000..e2089ba --- /dev/null +++ b/docs/solve-a-bounty/sats-to-mxn.md @@ -0,0 +1,72 @@ +# How to Convert Sats into Mexican Pesos (MXN) + +Once you've earned satoshis (sats) through Lightning Bounties, you might want to convert them into your local currency. This guide covers how to convert your sats into Mexican Pesos (MXN) and transfer them directly into your bank account. + +## Overview + +Converting sats to MXN generally involves these steps: +1. Sending sats from your Lightning wallet to a crypto exchange that supports MXN. +2. Selling the sats (or Bitcoin) for Mexican Pesos within the exchange. +3. Withdrawing the Mexican Pesos via SPEI transfer to your local bank account. + +--- + +## Recommended Exchanges for Mexico + +Two of the most popular and reliable exchanges supporting both the Lightning Network (for low fees) and MXN withdrawals (via SPEI) are: + +- **Bitso** (The largest crypto exchange in Mexico, supports SPEI transfers). +- **Strike** (Supports Lightning Network natively and allows cross-border fiat payouts). +- **Binance** (Global platform with P2P options or MXN fiat gateways). + +Below is a step-by-step example using **Bitso**. + +--- + +## Step-by-Step Guide: Using Bitso + +### 1. Set Up Your Bitso Account +If you do not already have a Bitso account, download the app or visit Bitso.com to create one. +* **Verify your identity (KYC):** You will need to provide identification to enable fiat withdrawals to your bank. + +### 2. Get Your Bitcoin Deposit Address +Since you have satoshis on the Lightning Network, you need to ensure you deposit via the correct network. + +1. Open the Bitso app and select **Deposit**. +2. Choose **Bitcoin (BTC)**. +3. Make sure to select the **Lightning Network** option (if available) to save on fees. +4. If Bitso only supports regular on-chain Bitcoin deposits for your account tier, you may need a wallet like *Muun* or *Breez* to swap Lightning sats to an on-chain BTC address seamlessly. +5. Copy your deposit address or generate a Lightning invoice for the specific amount. + +### 3. Send Sats from Your Wallet +1. Open the wallet where you received your Lightning Bounties (e.g., Wallet of Satoshi, Zeus, Alby). +2. Click **Send**. +3. Paste the invoice or address from Bitso. +4. Confirm the transaction. It should arrive almost instantly if using the Lightning Network. + +### 4. Sell Crypto for MXN +1. On Bitso, go to your **Wallet** or **Exchange** tab. +2. Select your Bitcoin balance and choose **Sell** or **Convert**. +3. Enter the amount of BTC you want to sell and choose **MXN (Mexican Pesos)** as the receiving currency. +4. Review the exchange rate and confirm the sale. + +### 5. Withdraw MXN via SPEI +1. Go back to the main menu and select **Send** or **Withdraw**. +2. Choose **Mexican Pesos (MXN)**. +3. Select **Bank transfer (SPEI)**. +4. Enter your 18-digit CLABE number (the standard for Mexican bank transfers), the bank name, and the beneficiary name. +5. Enter the amount you wish to withdraw and confirm. +6. SPEI transfers are processed 24/7 and usually arrive in your bank account within minutes! + +--- + +## Bonus: What to Do with Sats Without Converting! + +Instead of converting your sats to fiat, did you know you can spend them directly in Mexico or online? Here are a few ways to use your sats: + +* **Pay for Bills + Services:** Use services like Bitrefill to buy gift cards for Amazon MX, Uber, cellular top-ups (Telcel, AT/T), and more, directly with Lightning. +* **Support Creators:** Use the Alby extension or apps like Nostr to tip your favorite podcasters, writers, and developers who accept Zaps. +* **Shop at Lightning-friendly stores:** An increasing number of online merchants accept Bitcoin via Lightning. Check out directories like Lightning Network Stores. +* **Save/HODL:** Keep your sats in a secure self-custodial wallet as a long-term digital asset. + +By keeping your funds in the Bitcoin ecosystem, you completely avoid exchange fees and bank withdrawal limits. diff --git a/getting-started/solving-a-bounty/how-to-convert-sats-into-local-currencies.md b/getting-started/solving-a-bounty/how-to-convert-sats-into-local-currencies.md index c2a4347..0e74114 100644 --- a/getting-started/solving-a-bounty/how-to-convert-sats-into-local-currencies.md +++ b/getting-started/solving-a-bounty/how-to-convert-sats-into-local-currencies.md @@ -1,5 +1,7 @@ # How to Convert Sats into Local Currencies +- [Sats to MXN (Mexico)](../../docs/solve-a-bounty/sats-to-mxn.md) + ## Getting Started To withdraw Sats from the Lightning Network to Coinbase (or any other wallet/exchange), follow these steps. The process remains similar no matter where you're transferring your funds. From e0055562924c0b88377a272818e3edadf5a38cef Mon Sep 17 00:00:00 2001 From: Hermes Agent Date: Thu, 4 Jun 2026 22:26:46 -0700 Subject: [PATCH 2/2] Add section: Posting and solving bounties for GitBook / Wikis --- SUMMARY.md | 1 + .../posting-a-bounty/gitbook-wiki/README.md | 44 +++++++++++++++++++ 2 files changed, 45 insertions(+) create mode 100644 getting-started/posting-a-bounty/gitbook-wiki/README.md diff --git a/SUMMARY.md b/SUMMARY.md index 6d7bd8a..71d6b48 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -16,6 +16,7 @@ * [POSTING A BOUNTY](getting-started/posting-a-bounty/README.md) * [Deposit Funds](getting-started/posting-a-bounty/deposit-funds.md) * [Create a GitHub issue and Submit a new reward](getting-started/posting-a-bounty/create-a-github-issue-and-submit-a-new-reward.md) + * [Posting and solving bounties for GitBook / Wikis](getting-started/posting-a-bounty/gitbook-wiki/README.md) * [MANAGING YOUR BOUNTY](getting-started/managing-your-bounty/README.md) * [Issue Lock Time](getting-started/managing-your-bounty/issue-lock-time.md) * [Add Reward to an Existing Bounty](getting-started/managing-your-bounty/add-reward-to-an-existing-bounty.md) diff --git a/getting-started/posting-a-bounty/gitbook-wiki/README.md b/getting-started/posting-a-bounty/gitbook-wiki/README.md new file mode 100644 index 0000000..694936f --- /dev/null +++ b/getting-started/posting-a-bounty/gitbook-wiki/README.md @@ -0,0 +1,44 @@ +# Posting and Solving Bounties for GitBook / Wikis + +This guide explains how to post and solve bounties for GitBook or wiki-based documentation sites. + +## Posting a Bounty + +To post a bounty for a GitBook or wiki documentation improvement: + +1. Identify the specific documentation page or section that needs improvement +2. Fork the repository (if it's open source) or request edit access +3. Create a clear issue describing: + - What documentation needs to be updated/created + - Where it should be located in the documentation structure + - Any specific requirements or examples to include + - Label it appropriately as a documentation bounty +4. Set a reward amount in satoshis based on the complexity and value of the documentation work + +## Solving a Bounty + +To solve a documentation bounty: + +1. Review the issue requirements carefully +2. Fork the repository if you haven't already +3. Create a new branch for your documentation changes +4. Make the necessary documentation improvements: + - Write clear, concise content + - Follow the existing documentation style and tone + - Include relevant examples or code snippets if applicable + - Ensure proper formatting for GitBook/Markdown +5. Test your changes by previewing them in GitBook if possible +6. Commit your changes and push to your fork +7. Open a pull request referencing the original issue +8. Wait for maintainer review and approval +9. Once merged, claim your reward via Lightning Bounties + +## Best Practices + +- Keep documentation focused and task-oriented +- Use clear headings and subheadings +- Include code blocks with proper syntax highlighting when relevant +- Link to related documentation when appropriate +- Follow the contribution guidelines of the specific project +- Ensure your documentation is accessible and inclusive +