> For the complete documentation index, see [llms.txt](https://goldilocks-1.gitbook.io/goldidocs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://goldilocks-1.gitbook.io/goldidocs/ecosystem-nft-utilities.md).

# Ecosystem NFT utilities

Goldilocks DAO is partnering with Berachain ecosystem projects to allow their NFT's to have multiple utilities within Goldilend.

(i) A borrower can lock partner NFT’s on Goldilend for the duration of their loan in order to decrease the interest rate paid on that loan. Partner NFT’s can be stacked so that locking e.g. 5 NFT’s will generate 5 times as much discount as locking 1 NFT, up to a maximum discount of 50% (in which case the locker is paying half the interest that a standard locker would pay).

(ii) Secondly, partner NFT’s can be locked on the platform in order to boost PORRIDGE yield for GiBGT stakers. Each NFT represents an increase in the PORRIDGE yield rate for a GiBGT staker, and these boosts stack up to a maximum of 50%.

At the time of writing, we have partnered with several leading native Berachain projects and are actively seeking to establish further similar partnerships.\
\
\
\
\
\
\
\ <br>


---

# 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://goldilocks-1.gitbook.io/goldidocs/ecosystem-nft-utilities.md?ask=<question>&goal=<endgoal>
```

`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.