# Welcome to Blueberry Protocol ### Concept Summary Blueberry provides next-gen tools for DeFi yield strategists to enjoy new on-chain capabilities and access more capital. Blueberry's innovative "position NFTs" combine a user's collateral, debt, and deployment into one position, allowing borrowing of 20x the collateral value or more while maintaining a healthy system. Positions are sent to liquidation at a -85% or -90% PnL depending on the collateral supplied, protecting lender capital. ### Blueberry Docs In the documentation, we will guide you through an overview of Blueberry, its core features, and functionalities; including leveraged yield farming and lending, as well as a guide to using the protocol. If you still have any questions after reading the documentation, please see the FAQs section or hop into our discord server. ### Why Build Blueberry? DeFi is hamstrung by a lack of on-chain hedging and leverage capabilities, forcing users to rely on centralized solutions with counterparty risk. Blueberry seeks to bring as much capability as possible on-chain with an improved user experience. The protocol also seeks to level the playing field for liquidity provision, allowing anyone with a Web 3 wallet to perform sophisticated Liquidity Provision strategies like a market maker. Read more about Blueberry's "Why's" on our official medium: ### For developers: We also provided Web3.0 builders/developers that are looking to integrate with Blueberry with the documentation needed in the developer guides section. See more details below: {% content-ref url="developer-guides/contracts" %} [contracts](https://v1.docs.blueberry.garden/developer-guides/contracts) {% endcontent-ref %} --- # Agent Instructions: 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://v1.docs.blueberry.garden/welcome-to-blueberry-protocol.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.