> For the complete documentation index, see [llms.txt](https://docs.lightningbounties.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lightningbounties.com/docs/glossary-work-in-progress/lightning-bounties-team.md). # Lightning Bounties Team We are a dedicated team of open-source enthusiasts, inspired by the spirit of our revolutionary Boston forefathers. Similar to Bitcoin enthusiasts, we strongly believe in borderless collaboration and strive to eliminate barriers and limitations. Our passion for decentralized innovation drives us to create a new era of unrestricted progress. Although we come from diverse backgrounds in crypto, AI, and software development, we share a common conviction in the transformative power of decentralization, Bitcoin, & open-source software. We are not conventional corporate employees; instead, we are advocates of open source, fervent supporters of Bitcoin, and disruptors of the status quo. We pledge to be the catalyst for a new age of unrestricted innovation, one bounty at a time.

Enrique Gamboa	Will Sutton	Pavel Kononov	Mike Abramo

`Partnerships & Growth`	`Product & Strategy`	`Engineering & Project Management`	`Marketing & Developer Relations`
GitHub	GitHub	GitHub	GitHub

--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.lightningbounties.com/docs/glossary-work-in-progress/lightning-bounties-team.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.