• Visit app.lightningbounties.com.

• Explore the feed for available bounties. Each listing includes the project, issue description, and reward amount.

• Each bounty card shows:

  • Project name (organization/repo)

  • Issue title and brief description

  • Reward amount in sats

2 - Click on a Bounty Card for Details

• Select any bounty in the feed to view more information.

  • Review the issue description, requirements, and acceptance criteria.

  • Make sure the bounty is still available (not claimed or solved).

3 - (Optional) View on GitHub

• For more context or to join the discussion, click the GitHub link at the top of the bounty detail page.

• This opens the original GitHub issue, where you can:

  • See all comments and related activity

  • Check for recent maintainer responses

  • Review any related pull requests

Next Steps

Once you’ve found a bounty you want to work on, continue to Working on a Bounty for a step-by-step guide on submitting your solution and claiming your reward.

Tips for Bounty Hunters

• Check Requirements: Always read the bounty’s requirements and acceptance criteria before starting.

• Act Fast: Some bounties may be solved quickly. Start your work as soon as you find an issue that interests you.

• Look for the Winner 🏆icon: If it’s missing, the bounty is still available.

• Stay Updated: Follow Lightning Bounties on and join our to hear about new bounties and platform updates.

Need Help?

Ask Questions: If anything is unclear, reach out to the project maintainer or join our Discord Community for help and tips.

1. Sign in to your Coinbase account.

2. Select Bitcoin as the asset you wish to receive.

3. Select the Lightning network.

4. Follow the prompts to create your invoice

   • Invoices are valid for 72 hours.

5. Copy the invoice. You will need this in the next section.

Part (2): How to withdraw sats from Lightning Bounties to Coinbase?

1. Login to Lightning Bounties: then click on your account.

1. Initiate Withdrawal: Select the option to withdraw your sats.

3a. First, paste your invoice string into the input field

(the same one you copied on your Coinbase account in the previous step).

3b. Click the “Create”

1. Your sats should now be reflected in your Coinbase account after the transaction is confirmed.

Part (3): Converting Your Crypto Into Fiat Using Coinbase.

3a. Sell crypto to your Coinbase cash balance

To sell your crypto:

1. Sign in to your Coinbase account, on the web or mobile app

2. Select Buy & Sell

3. Select Sell

4. Select the crypto you want to sell and the amount.

   If on mobile, you'll be required to crypto the asset you want to sell before entering an amount

5. Change the To destination, if applicable.

   • This will likely default to your local currency balance (USD) but you may have the option of adding to another balance (e.g., USDC).

6. Select Review order.

7. Select Sell now to complete the sale.

Once the crypto sell order is complete, the funds will be available in your cash balance to buy other assets or cash out to your bank.

3b. Cash out your funds

By aligning with the ethos of Bitcoin and FOSS, Lightning Bounties is more than just a platform—it’s a movement to decentralize opportunity, accelerate innovation, and empower individuals worldwide to build the tools that shape our future.

2. Click the "..." button at the top-right of your PR description

3. Select "Edit"

4. Add close #[issue-number] to the PR description text

Example: If fixing issue #5, add close #5 to your PR description.

5. Click on "Update Comment"

# That's it!

This connects your PR to the issue and will trigger your bounty payment automatically.

ℹ️ Important Notes:

• The closekeyword must be in the PR description itself, not in regular comments.

• Adding this connection after merging will automatically trigger the lightning bounty payment.

• If you cannot edit the PR, ask the repo owner to add the closesyntax for you.

2. Make a minimal change (can be as simple as updating documentation or adding a comment)

Example: Add a small comment or documentation update ⬇️

3. Push your branch

4. Create the new pull request

• Go to the repository on GitHub

• Click "Compare & pull request"

• Important: Include close #X or closes #X in the PR description (where X is your issue number)

• Explain that this PR is to properly close the issue for Lightning Bounty payment

• Reference your original PR: "This PR references the work completed in #Y"

ℹ️ Important Notes:

• The repository owner will need to review and approve this new PR

• This is a technical solution to trigger the Lightning Bounties payment system

• The minimal change is necessary as GitHub requires actual content changes for a PR

Crowdfunding Bounties

• Collaborative Funding: Multiple users can contribute sats (Bitcoin microtransactions) to fund a single bounty.

• Support for Third-Party Projects: Post bounties on issues from popular open-source projects like VSCode, Django, or React—even if you’re not the project owner.

Bounty Lock Time & Expiry

• Guaranteed Escrow: Rewards are locked for a set period (e.g., two weeks) to ensure bounty hunters know the reward will be available when they submit their solution.

• Flexible Expiry Options: After the lock time ends, you can manually expire the bounty and reclaim your funds if priorities change or the issue is resolved elsewhere.

Smart Reward Distribution

• GitHub API as an Oracle: Rewards are automatically sent to contributors once their pull request is successfully merged, preventing fraudulent claims.

Lightning Bounties is built to remove friction, simplify participation, and empower developers to contribute meaningfully to open-source projects while earning Bitcoin.

Some wallets are Lightning-only, some are on-chain only, and some are hybrid wallets supporting both payment methods.

How to Claim Multiple Bounties in One PR

1. Solve multiple issues

   • Make sure each issue you solve is still open bounty.

2. Create a single PR referencing all issues

   • In your PR description, use the closing keywords for each issue you solved:

   • This will close all referenced issues when the PR is merged.

3. Wait for PR approval and merge

   • Once the PR is merged, GitHub will close all referenced issues.

4. Claim rewards individually

   • Go to each issue’s page on Lightning Bounties.

   • Click 'Claim Reward' and 'Check' for each bounty you solved.

   • Each bounty reward will be processed separately.

Common Pitfalls & How to Avoid Them

• Forgetting to use closing keywords: Always include close #issue-number for each issue in the PR description (not in comments or commits).

• Not claiming each bounty: After your PR is merged, visit each issue on Lightning Bounties and click "Claim Reward" separately.

• Trying to claim after missing a close keyword: If you forgot to link an issue, create a minimal follow-up PR for that issue, include the correct closing keyword, and reference the original PR.

• Assuming rewards are automatic: Rewards are not sent automatically when the PR is merged. You must manually claim each one.

Visual Workflow

Best Practices & Troubleshooting

• Always use closing keywords (close #issue-number) in the PR description, not in comments or commits.

• You must claim each bounty individually on Lightning Bounties, even if multiple issues were closed in one PR.

• If you accidentally missed a bounty, create a minimal follow-up PR to properly close and claim it.

• Refresh the PR page after editing links to see updates.

For more details, see Claim Reward Criteria & Troubleshooting Guide and GitHub’s guide to linking pull requests to issues.

For additional assistance, join the Lightning Bounties Discord community.

In this example, we are adding 500 sats

3 - Click on the "Generate" button

4 - Use your preferred Lightning app to scan the generated QR code

5 - After scanning, your added sats will be reflected on your balance

Notice how this profile went from 300 to 800 after depositing 500 sats

You will be all set to continue using the platform!

A Taproot-powered protocol for issuing assets on the Bitcoin blockchain that can be transferred over the Lightning Network for instant, high-volume, low-fee transactions.

B

Balance

The amount of Bitcoin (measured in sats) available in a user's Lightning Bounties account that can be used to fund bounties or withdrawn.

Bitcoin

A decentralized digital currency where transactions are verified by network nodes through cryptography and recorded in a public distributed ledger.

BOLT-11 Invoice

The standardized format for Lightning Network payment requests, containing payment amount, destination, and optional message.

Bounty

A reward offered for completing a specific task, typically fixing a bug or implementing a feature in an open-source project.

Bounty Lock Time

A specified period during which bounty funds are locked in escrow to ensure they remain available when developers submit solutions.

Branta Verification

Verify with Branta is an optional security feature that lets you double-check a Lightning invoice before paying it on Lightning Bounties. When you see a "Verify Invoice - Branta" link under any payment form, clicking it opens a separate page that confirms the invoice destination is legitimate.

Bug Bounty

A reward offered to developers who discover and report bugs in a software project, enhancing security and reliability.

C

Channel Reserve

The amount of Bitcoin required to open a Lightning Network payment channel.

Crowdfunding Bounties

A feature allowing multiple users to contribute funds toward a single bounty, increasing the reward and incentivizing developers.

Custodial Wallet

A wallet where a third party maintains control of private keys, reducing user responsibility but potentially introducing security risks.

D

Decoded Invoice

The human-readable information extracted from a Lightning invoice showing payment amount, destination, and expiration time.

Deposit

The process of adding Bitcoin to your Lightning Bounties account to fund bounties.

Developers

One of the primary user groups of Lightning Bounties who can showcase skills, earn Bitcoin, and contribute to open-source projects.

Digital Signature

Cryptographic proof that the holder controls a specific Bitcoin address, used to authorize transactions from that address.

E

Escrow

A system that holds bounty funds securely until predetermined conditions are met, ensuring fair transactions between parties.

Expiry

A feature allowing a bounty creator to reclaim funds after the lock time ends if priorities change or the issue is resolved elsewhere.

F

Flexible Expiry Options

The ability to manually expire a bounty and reclaim funds after the lock time ends if the issue is resolved through other means.

Funding Transaction

The transaction that establishes a Lightning Network channel by locking Bitcoin in a multisignature address.

G

GitHub API as Oracle

The mechanism that uses GitHub's API to automatically verify when solutions are accepted, triggering reward distribution.

GitHub Issue

A ticket in a GitHub repository that identifies bugs or requested features, which can be linked to bounties on Lightning Bounties.

GitHub Projects

Software repositories on GitHub that can benefit from Lightning Bounties to incentivize contributions and bug fixes.

GitHub URL

The web address of a GitHub repository or issue that is linked to a bounty on Lightning Bounties.

H

Hash

A cryptographic function that generates a fixed-size output from variable-size input, used extensively in blockchain and Lightning Network.

K

Keypair

The combination of public and private keys that control access to Bitcoin addresses and funds.

L

Lightning Bounties Platform

A Bitcoin-powered bug bounty platform that integrates with GitHub workflows to enable developers to earn Bitcoin for open-source contributions.

Lightning Gossip Network

The network used to broadcast information about channels and peers in the Lightning Network.

Lightning Invoice

A payment request on the Lightning Network that includes payment amount, destination, and an expiration time.

Lightning Network

A layer-2 solution built on top of the Bitcoin blockchain that enables faster and cheaper transactions through payment channels.

Lightning Network Channel

A peer-to-peer payment channel that enables instant and low-cost transactions between two parties.

Lightning Wallet

A wallet specifically designed to send and receive payments through the Lightning Network, offering faster transactions than traditional Bitcoin wallets.

Lock Time

The period during which bounty funds are guaranteed to be available, giving developers confidence that rewards will be paid upon completion.

M

mSats (Millisatoshis)

Each 1/1000 of a satoshi, allowing for even smaller denominations on the Lightning Network while channels are open.

N

No Banking Restrictions

A feature of Lightning Bounties that allows global operation with Bitcoin, bypassing region-restricted payment processors.

Non-custodial Wallet

A wallet where the user maintains full control over their private keys and funds, increasing security responsibility but eliminating third-party risks.

O

Open Source Development

The collaborative practice of making source code freely available for modification and redistribution, which Lightning Bounties supports and incentivizes.

Organizations

Entities that use Lightning Bounties to tap into a global developer pool to improve software quality and security.

P

Payment

A transaction that occurs on the Lightning Network, routed through payment channels without being recorded on the Bitcoin blockchain.

Peer-to-peer Network

A decentralized system like Bitcoin or Lightning Network where connections occur directly between participants without intermediaries.

PlebLab

A Bitcoin-focused incubator that supports Lightning Bounties and other Bitcoin innovation projects.

Pull Request

A method of submitting contributions to a GitHub repository, which triggers reward distribution when merged with proper closing syntax.

R

Recovery Phrase

A series of words that can recover wallet access, also known as a seed phrase or mnemonic.

Reward Claimed

The status indicating a bounty has been successfully paid to a developer after their solution was accepted.

S

Satoshi (sats)

The smallest unit of Bitcoin, representing 1/100,000,000 (one hundred millionth) of a Bitcoin, named after Bitcoin's creator.

Seed Phrase

A list of words that store all the information needed to recover a Bitcoin wallet.

Smart Reward Distribution

The automated system that distributes bounty rewards to contributors once their pull request is verified and merged.

T

Transaction ID (txid)

The unique identifier hash of a Bitcoin transaction, used to identify Lightning Network channels.

W

Watchtower

A security service that monitors the blockchain for potential channel breaches and takes action to protect funds if necessary.

Withdraw

The process of transferring Bitcoin from your Lightning Bounties account to your personal Lightning wallet.

2. Find an Issue

• Browse available bounties on the app.lightningbounties.com feed

• Review the issue details, requirements, and reward amount

• Check if the bounty is still available (not claimed by someone else)

  • See Finding Bounties to Solve For Detailed Instructions.

3. Fix the Issue

• Fork the repository to your GitHub account

• Clone your fork locally and create a branch for your work

• Implement the fix according to the issue requirements

• Test your changes thoroughly to ensure they meet all acceptance criteria

• Push your changes to your fork

  • See For Detailed Instructions.

4. Create a Pull Request (PR) Targeting Main/Master

• Go to the original repository on GitHub.

• Click "Compare & pull request" for your branch.

ℹ️ Why?

GitHub only recognizes linked issues when the PR targets the repository's default branch (usually main or master).

• Learn more about linking PRs to issues.

• Provide a clear explanation of your changes and how they address the issue.

• You can include as much additional information as needed in your PR description.

• Submit the PR for review

Screenshot Example:

5. Wait for Maintainer to Merge the PR

• The repository maintainer will review your PR.

  • Once it is approved and merged, the issue will be closed automatically if you used the correct closesyntax.

    • See Working on a Bounty For Detailed Instructions.

6. Claim Reward Process

• Manually claim your reward:

  • Visit app.lightningbounties.com and find the Bounty you solved

  • Click the "Claim Reward" button

  • Click the "Check" button to verify your eligibility

Complete Claim Process Visualization

Troubleshooting

If you encounter issues claiming your Lightning Bounty reward, use this guide to diagnose and resolve common problems.

For more details, see the Lightning Bounties Troubleshooting Guide and GitHub’s official documentation on linking pull requests to issues.

Issue Not Linked to PR

Problem Indicators:

• The PR does not show the linked issue in the GitHub interface.

• The issue remains open after your PR is merged.

• The reward does not process automatically.

Solutions:

1. Edit PR Description

If your PR is still open, you can update the PR description to add the correct closing keyword (e.g., close #issue-number).

• Navigate to your pull request on GitHub.

• Near the top of the PR page, locate the description section (below the title).

• Hover over the description area and click the "Edit" (... or pencil) icon.

• Add the close #issue-numberkeyword at the top of the PR description (not in a comment or commit message, as only the PR body triggers the automation for Lightning Bounties and GitHub).

2. Ask Repository Owner (If you can't edit the PR)

• Contact the repository owner or maintainer

• Ask them to edit the PR description to add the closing keyword

3. Create a Follow-up PR (If original PR was already merged)

If your original PR has already been merged without the correct closing keyword: (see below)

• Create a new PR with a minimal change (e.g., update documentation, add a comment, or fix a typo).

• In the PR description, include the appropriate closing keyword (e.g., close #42).

• Reference your original PR:

• Notify the repository owner about this follow-up PR and explain its purpose.

• Once merged, return to Lightning Bounties and click "Claim Reward" and "Check."

Example of a follow-up PR created to properly link the issue for Lightning Bounty payment 🔽

4. Request an Override via Discord

If you are unable to resolve the issue through the above steps, join the Lightning Bounties Discord and request an override from the LB team.

• Add a comment to the PR, tagging the maintainer (e.g., @maintainer) and include the Lightning Bounties issue URL.

• Ask the maintainer to respond in the PR thread confirming that the PR qualifies for the bounty.

For more details on linking PRs to issues, see GitHub’s guide on linking pull requests to issues.

Payment Not Received

Verification Steps:

1. Confirm the issue is marked as "closed" on GitHub

2. Verify the PR that closed it has been merged

3. Check that you clicked "Claim Reward" on Lightning Bounties

Solutions:

• Check User Balance: Ensure your account balance is updated on app.lightningbounties.com

• Verify Wallet Setup: Make sure your Lightning Network wallet is correctly configured

• Contact Support: If issues persist, reach out to the Lightning Bounties Discord for assistance

Common Errors and Solutions

Best Practices

• Always double-check the issue number when adding close #issue-number syntax

• Communicate clearly with repository maintainers about your bounty claim

• Keep PRs focused on addressing the specific issue

• Don't forget to manually click "Claim Reward" on Lightning Bounties platform

For additional assistance, join the Lightning Bounties Discord community.

Effortless setup through:

• No installations required - no plugins or software downloads

• No account creation - immediate access to funding features

• Familiar GitHub integration - leverages existing developer workflows

Understanding No-Login Contributions

The no-login system provides:

• Instant access to bounty funding without registration

• Zero-friction contribution process in under 30 seconds

• Global accessibility without banking restrictions

• Privacy-first approach for occasional contributors

This approach aligns with Lightning Bounties' core principle of removing traditional barriers to open-source funding participation while maintaining robust security

Step-by-Step No-Login Process

Summary

The no-login reward system exemplifies Lightning Bounties' commitment to frictionless, accessible, and innovative open-source funding. By removing traditional barriers while maintaining robust security through Branta verification, this feature enables anyone to instantly support the open-source development they care about.

This approach creates a global bounty aggregator that truly democratizes software development funding, making it possible for anyone, anywhere to contribute to the projects that matter most.

Lock time helps bounty hunters know the reward will be available by the time they submit their solution. But being able to expire rewards is neccessary because sometimes you solve the issue yourself or your priorities for development change.

_{We recommend two weeks as a standard lock time, to give your hunters time to submit a PR, but also a short enough time to iterate on your bounty postings and format.}

How to Add Lock Time When Posting a New Bounty

1. Go to app.lightningbounties.com and Log-In through GitHub

2. Copy/Paste the GitHub Issue URL and set the amount in Sats for the Bounty Reward

3. Click in the Advanced Settings Toggle

4. Set the Lock Reward Time in either

   1. Minutes

   2. Hours

   3. Days

   4. Weeks

   5. Months

   _{We recommend two weeks as a standard lock time, to give your hunters time to submit a PR, but also a short enough time to iterate on your bounty postings and format.}

5. Click on "Submit New Reward"

Understanding Bounty Status: Locked vs. Unlocked

🔒 Locked Bounties

• Definition: A bounty is locked when its reward is held in escrow for a specific lock time, guaranteeing availability to bounty hunters.

• How it works:

  • The lock time is set when you post a bounty (e.g., two weeks is recommended).

  • During this period, the reward cannot be expired or reclaimed by the bounty poster.

  • Bounty hunters can work on the issue with confidence that the reward is guaranteed if they submit a valid solution within the lock window.

• Visibility:

  • The remaining lock time is displayed on the bounty detail page and in your dashboard.

  • A lock emoji or label indicates the bounty is currently locked.

• Best Practice:

  • Two weeks is suggested as a standard lock time, balancing developer opportunity and bounty iteration.

🔓 Unlocked Bounties

• Definition: A bounty becomes unlocked when the lock time expires.

• What changes:

  • The poster can now manually expire the reward and reclaim their sats if needed.

  • The bounty remains open and visible to hunters until it is solved or you take action.

  • The reward is not automatically revoked; it is still claimable by bounty hunters until you expire it.

• Visibility:

  • Unlocked bounties are labeled as such in your dashboard, and an "Expire Reward" button appears.

  • An unlock emoji or label indicates the bounty is now eligible for expiry.

How Lock Time & Expiry Protects Hunters and Posters

• Guaranteed Escrow: Lock time ensures bounty rewards are available for a set period, giving hunters confidence to submit solutions.

• Flexible Expiry: After the lock time, posters can reclaim funds if the issue is solved elsewhere or priorities change.

• Manual Control: Bounties do not expire automatically. You must take action to expire and reclaim your sats after the lock time ends.

Frequently Asked Questions

Any cryptocurrency other than Bitcoin.

ACINQ

A company that develops Lightning Network products including Phoenix wallet and Eclair implementation.

B

Base Layer

The main Bitcoin blockchain where final settlement occurs, as opposed to second-layer solutions like Lightning Network.

Bitcoin

A decentralized digital currency created in 2009 by Satoshi Nakamoto that operates without a central authority.

Bitcoin Core

The reference implementation of Bitcoin software that serves as the standard for the Bitcoin protocol.

Bitcoin Pizza Day

May 22nd, commemorating the first real-world Bitcoin transaction in 2010 when Laszlo Hanyecz paid 10,000 BTC for two pizzas.

Bitcoin Whitepaper

The original document published by Satoshi Nakamoto in 2008 titled "Bitcoin: A Peer-to-Peer Electronic Cash System."

Block

A collection of transactions bundled together and added to the blockchain.

Block Height

The number of blocks preceding a particular block in the blockchain.

Block Reward

The new bitcoins distributed by the network to miners for each successfully mined block.

Blockchain

A distributed ledger technology that maintains a continuously growing list of records (blocks) secured using cryptography.

C

Channel

A payment connection between two Lightning Network nodes that allows for multiple transactions without touching the Bitcoin blockchain.

Cold Storage

Keeping bitcoin offline in a device or medium not connected to the internet for enhanced security.

Consensus

The process by which all nodes in the network agree on the state of the blockchain.

Custodial Wallets

A custodial wallet is a wallet wherein the user’s private keys are held by a third party, such as an exchange. The third party has full control over the user’s funds, while the user only has permission to send and receive bitcoin.

The third party is responsible for providing a backup to the wallet in case the user forgets their login information. A custodial wallet is subject to the security practices of the third party, which reduces the users responsibility, but creates an increased risk to the seed phrase and the keys stored by the wallet if the third party is hacked.

F

Fee Market

The dynamic system where Bitcoin transaction fees are determined by supply (block space) and demand (pending transactions).

Full Node

A computer running software that fully validates transactions and blocks on the Bitcoin network.

H

Halving

An event occurring approximately every four years where the block reward for mining new Bitcoin blocks is cut in half.

Hard Fork

A permanent divergence in the blockchain that occurs when non-upgraded nodes can't validate blocks created by upgraded nodes following newer consensus rules.

Hardware Wallet

A physical device designed to securely store cryptocurrency private keys offline.

Hash Rate

The computational power being used by miners to secure the Bitcoin network.

L

Layer 2

Solutions built on top of the Bitcoin blockchain to improve scalability, such as the Lightning Network.

Lightning Invoinces

Users of the lightning network use a lightning invoice to request a payment. It is defined by BOLT 11 and includes an amount to be paid, destination of the payment, and an optional message. Unlike bitcoin addresses, lightning invoice’s expire after a set amount of time. By default, this is set to 60 minutes.

Lightning Network

A second-layer payment protocol that operates on top of Bitcoin to enable fast, scalable transactions and micropayments.

Lightning Service Provider (LSP)

A service that helps users establish channels and manage liquidity on the Lightning Network.

Liquidity

The availability of bitcoin in payment channels that enables routing of payments through the Lightning Network.

LNURL

A protocol for Lightning Network that simplifies the process of connecting applications to Lightning wallets.

LND (Lightning Network Daemon)

A complete implementation of a Lightning Network node by Lightning Labs.

M

Mempool

The waiting area for unconfirmed Bitcoin transactions before they're included in a block.

Multisig (Multi-signature)

A security feature that requires multiple signatures to authorize a Bitcoin transaction.

N

Node

A computer connected to the Bitcoin or Lightning network that validates transactions according to network rules.

Non-custodial Wallets

Non-custodial wallets give the user full control over their funds and the associated private keys. By using a non-custodial wallet, a user is their own bank; they can initiate transactions, and are responsible for the security of their wallet, including protection of their seed phrase, which can be used to restore their wallet if it’s lost or compromised.

Nostr

A decentralized social network protocol often used by the Bitcoin community, with integration capabilities for Lightning payments.

O

On-chain

Transactions that occur directly on the Bitcoin blockchain, not on second-layer solutions.

Off-chain

Transactions that occur outside the Bitcoin blockchain, such as those on the Lightning Network.

Open Source

Software whose source code is publicly available, allowing anyone to inspect, modify, and enhance it.

P

Private Key

A secret number that allows bitcoins to be spent, functioning as a password that gives access to your bitcoin.

Public Key

A cryptographic code derived from a private key, used to create Bitcoin addresses for receiving funds.

R

RGB

A protocol for issuing and transferring digital assets on Bitcoin and Lightning Network.

Routing

The process of finding a path through multiple payment channels to complete a Lightning Network payment.

S

Satoshi (sat)

The smallest unit of Bitcoin, equal to 0.00000001 BTC. Named after Bitcoin's creator.

Satoshi Nakamoto

The pseudonymous creator of Bitcoin whose true identity remains unknown.

SegWit (Segregated Witness)

A Bitcoin protocol upgrade that changed how data is stored in blocks, increasing capacity and fixing transaction malleability.

Self-Custody

Maintaining full control of your private keys and thus your bitcoin, rather than relying on a third party.

Soft Fork

A change to the Bitcoin protocol where only previously valid blocks/transactions are made invalid, backward-compatible with older versions.

T

Taproot

A Bitcoin upgrade implemented in 2021 that improved privacy, efficiency, and smart contract functionality.

Testnet

An alternative Bitcoin blockchain providing developers with a testing environment without using real bitcoin.

Timelock

A feature that restricts spending bitcoin until a specified future time or block height.

Tor

An anonymity network often used by Bitcoin nodes to increase privacy by concealing users' locations and usage.

U

UTXO (Unspent Transaction Output)

The output of a transaction that can be spent in the future; effectively, your bitcoin balance consists of UTXOs.

W

Wallet

Software or hardware that stores private keys and allows users to send and receive bitcoin.

Watch-only Wallet

A wallet that can see transactions but cannot spend the funds because it doesn't have the private keys.

Watchtower

A service that monitors the Lightning Network for potentially fraudulent channel closures and broadcasts justice transactions.

Z

Zero-confirmation Transaction

A transaction that has been broadcast to the network but not yet included in a block, also called an unconfirmed transaction.

_{This optional yet highly-recommended safety check is especially critical for no-login users who lack account-based recovery options}

The platform provides real-time payment tracking and transparent reward systems

See who contributed at the bottom

Your anonymous reward is now live!

Limited Support Options

• No direct support resolution through platform account

• Cannot modify contributions after payment

• Limited communication with platform support

Converting Anonymous to Account-Based Contributions

If you find yourself regularly contributing anonymously, consider:

1. Login through GitHub on Lightning Bounties for better tracking

2. Using the deposit system for more efficient contributions