> For the complete documentation index, see [llms.txt](https://blog.lightningbounties.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blog.lightningbounties.com/enrique-gamboa/winning-the-mit-hackathon-2024.md).

# Winning the MIT Hackathon 2024

**Cross-Posted from** [**Medium**](https://jegamboafuentes.medium.com/our-epic-win-at-the-mit-bitcoin-hackathon-2024-34fab944e78d)

*Enrique Gamboa, May 5 2024*

<figure><img src="https://3518045692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK0Wa8Pq0phTb0SwmqL5e%2Fuploads%2FLmn7lWObbQ7OflBDRGis%2Fimage.png?alt=media&amp;token=5dae88eb-b93c-4005-92ed-5e5999ef1622" alt=""><figcaption></figcaption></figure>

## Introduction 🌟 <a href="#id-911c" id="id-911c"></a>

Greetings! As staunch advocates for open-source and cryptocurrency, participating in the [MIT Bitcoin Hackathon 2024](https://mitbitcoinexpo.org/) was an excellent match for our team’s aspirations. Driven by a commitment to innovation, we embarked on a challenge to enhance how *open-source* contributions are **rewarded 🪙**. We focused on integrating **Bitcoin, GitHub actions** and the **Lightning Network** into our solution.

## The Hackathon Challenge ⚙️ <a href="#id-63af" id="id-63af"></a>

The atmosphere at the [hackathon ](https://devpost.com/software/lightning-bounty)was charged with excitement, featuring a blend of intense coding and collaborative innovation. Over the weekend of April 19th to 21st (*the Same as the Bitcoin halving 2024), we developed our project, “Lightning Bounties,***”,** which integrates **GitHub Actions** with Bitcoin rewards **🪙**, providing a compelling incentive for open-source contributions.

(continued...)

**Read the full article here:** [**https://jegamboafuentes.medium.com/our-epic-win-at-the-mit-bitcoin-hackathon-2024-34fab944e78d**](https://jegamboafuentes.medium.com/our-epic-win-at-the-mit-bitcoin-hackathon-2024-34fab944e78d)

<figure><img src="https://3518045692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK0Wa8Pq0phTb0SwmqL5e%2Fuploads%2FU1xcTjNY1SRX3HOhnPFb%2Fimage.png?alt=media&amp;token=1aeceff0-43bc-4fc1-b5d2-ebe6dbde6370" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://blog.lightningbounties.com/enrique-gamboa/winning-the-mit-hackathon-2024.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.