> For the complete documentation index, see [llms.txt](https://gum-ball.gitbook.io/gumball-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gum-ball.gitbook.io/gumball-protocol/core-concepts/physical-redemptions.md). # Physical Redemptions The GumBall borrowing mechanism opens the door for creators to be paid using loans on GBT/gNFT positions. For example, a creator deploys a collection that incorporates a service or physical good. Users could pay for the service by staking their position and borrowjng against. The borrowed base asset would then be used to pay the creator for their goods and services. The staked position is still earning yield, this yield can be routed to the redeemer. Because staked positions accrues fees, this model is also perfect for creators looking to incorporate wear-to-earn or use-to-earn elements into items. Imagine wearing socks that give you passive income. More info on physical redemption coming soon... --- # 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, and the optional `goal` query parameter: ``` GET https://gum-ball.gitbook.io/gumball-protocol/core-concepts/physical-redemptions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.