> For the complete documentation index, see [llms.txt](https://docs.renfter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.renfter.com/developers/technical-overview.md).

# Technical Overview

The Renfter protocol enables NFT renting (both ERC-721 and ERC-1155 standards) by transferring the ownership of the NFT to a smart contract wallet associated with a specific user (Holder Wallet contract) and allowing the renter to use any underlying functionalities of the NFT by using a wrapped NFT received at the beginning of the renting period.

The following diagram shows a high-level overview of the protocol.

<figure><img src="/files/SIYqNJAgaN48Di52uJeV" alt=""><figcaption><p>High-level diagram of protocol</p></figcaption></figure>

### Renfter <a href="#renfter" id="renfter"></a>

The core smart contract of the protocol manages and orchestrates all the protocol parts and contains the protocol’s core logic. It also manages the majority of the interactions related to the process of renting out NFTs and the rental itself. The contract is responsible for creating each user’s Holder Wallet and for forwarding calling functionalities to the original token.

### Holder Wallet <a href="#holder-wallet" id="holder-wallet"></a>

This smart contract acts like a smart contract wallet. It is responsible for holding wrapped NFTs and calling the NFTs’ custom functionalities currently under its ownership. Only the owner of the wrapper NFT can call this contract unless specified otherwise.

### Wrapper NFT <a href="#wrapper-nft" id="wrapper-nft"></a>

There is one wrapper smart contract per NFT collection wrapped. It issues tokens that act as mirrors to the original NFTs and calls methods whitelisted by the lender for the original NFT. Thus, it acts as a key to unlock and access the original NFT.


---

# 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.renfter.com/developers/technical-overview.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.