> For the complete documentation index, see [llms.txt](https://cozies.gitbook.io/cozies/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cozies.gitbook.io/cozies/transit-map/wrapper-contracts.md).

# Wrapper Contracts

### Upgradability

Cozies has been intentionally designed with upgradability in mind. The genesis smart contracts deployed for the project’s NFTs will be value-enhanced over time through ‘wrapper’ contracts. Future wrapper smart contracts will call on our NFT’s original smart contract functions to enable additional services and functions for holders. We note here that careful design is vital for Ethereum wrapper contracts.

#### ENS Avatars & Sub-domains

Although outside of our core thinking for how we intend to utilize *wrapper* contracts specifically, ENS Avatars and Sub-domains are on our radar and represent an area to discuss with the Cozies community. We have been staying up-to-date with the [.earth](https://twitter.com/dotearth_?s=20\&t=pFBCG9rpDxCiebCa9l2SZw) project as a point of inspiration and proof of concept. Name Wrapper contracts enable additional capabilities for ENS domains (including sub-domains) and also enable the setting of metadata.

{% hint style="info" %}
ENS Name Wrapper Github: <https://github.com/ensdomains/name-wrapper>
{% endhint %}


---

# 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://cozies.gitbook.io/cozies/transit-map/wrapper-contracts.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.