> For the complete documentation index, see [llms.txt](https://docs.pinto.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pinto.money/appendix/beanstalk-obligations/beanstalk-fertilizer.md). # Beanstalk Fertilizer Beanstalk [Fertilizer](https://docs.bean.money/almanac/farm/barn#fertilizer) was originally purchased during the Barn Raise to fund Beanstalk's recapitalization after the April 2022 exploit. Holders of Fertilizer on Beanstalk received equivalent ERC-1155 tokens on the Beanstalk Barn Payback contract. Each Fertilizer token is identified by a unique ID that corresponds to its target Beans Per Fertilizer (BPF) threshold. ### Sprouts and Humidity Each Fertilizer token has a Humidity, which represents the interest rate associated with that Fertilizer when it was originally purchased. Sprouts represent the Pinto remaining to be earned before a Fertilizer token is fully repaid: > Sprouts = Balance × max(0, Fertilizer ID − Current BPF) As the protocol distributes Pinto to the Beanstalk Barn Payback contract, the global BPF increases. As BPF rises, Sprouts decrease and Fertilized Pinto (the claimable amount) increases. ### How Fertilization Works Each [Season](https://docs.pinto.money/resources/glossary#season), when the Pinto supply exceeds 1 billion and the [time-weighted average price](https://docs.pinto.money/responding-to-state/minting) of Pinto is above $1, a portion of newly minted Pinto is distributed to the Beanstalk Barn Payback contract. These Pinto increase the BPF proportionally across all Active Fertilizer (Fertilizer whose ID has not yet been reached by the current BPF). When BPF reaches or exceeds a Fertilizer ID, that Fertilizer is considered fully fertilized and is removed from the active set. Remaining Pinto are then distributed across the smaller pool of still-Active Fertilizer, accelerating the repayment of subsequent Fertilizer IDs. Any Pinto that cannot be evenly distributed in a given Season are carried over as a remainder and included in the next Season's distribution. ### Rinsing Rinsing is the process of claiming Fertilized Pinto. To Rinse, visit the [Beanstalk Obligations](https://pinto.money/beanstalk) page on the Pinto interface and click **Rinse** in the Beanstalk Fertilizer section. Fertilized Pinto accumulates automatically and can be Rinsed at any time. Rinsed Pinto are sent to the Farmer's wallet. ### Transferring Beanstalk Fertilizer tokens can be transferred to another address by clicking **Send** in the Beanstalk Fertilizer section. When Fertilizer is transferred, any accumulated Fertilized Pinto for both the sender and the recipient is automatically claimed to their respective Farm Balances before the transfer occurs. The recipient then begins earning from the current BPF going forward. Farmers who hold multiple Fertilizer IDs can transfer them individually or in batches. ### Completion Once all Fertilizer IDs have been fully fertilized (BPF reaches or exceeds the highest Fertilizer ID), the Beanstalk Barn repayment is complete. Any mints previously allocated to this route are redistributed to the remaining active repayment routes. --- # 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://docs.pinto.money/appendix/beanstalk-obligations/beanstalk-fertilizer.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.