> 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/values.md). # Values At Lightning Bounties, our values are rooted in the ethos of Bitcoin and the Free and Open-Source Software (FOSS) movement. These principles guide every aspect of our platform: * **Decentralization**: We break down barriers, empowering individuals worldwide to contribute freely without gatekeepers or restrictions. * **Accessibility**: Talent and effort—not privilege or location—define success on our open platform, available to anyone, anywhere. * **Transparency**: We uphold trust and accountability by fostering openness in every process, reflecting the collaborative spirit of FOSS. * **Empowerment**: By rewarding contributors with Bitcoin, we champion financial sovereignty and provide a censorship-resistant way to earn for meaningful work. * **Innovation**: We accelerate the development of decentralized technologies by connecting talent with impactful projects that shape the future. * **Community**: Collaboration drives us. We cultivate a thriving ecosystem where creators, developers, and innovators come together to solve challenges and build tools for everyone. These values are not just ideals—they are a call to action to decentralize opportunity, empower individuals, and drive innovation that benefits all of humanity. Lightning Bounties is more than a platform; it’s a movement to build a freer, fairer future through open collaboration. --- # 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://docs.lightningbounties.com/docs/glossary-work-in-progress/values.md?ask=&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.