> For the complete documentation index, see [llms.txt](https://docs.bracket.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bracket.fi/user-guides/wrapping-and-unwrapping.md).
# Wrapping and unwrapping
At the time of NAV publishing, Bracket's contract provides shares/tokens representing a claim on the position. \
\
The token received is rebasing (increases in balance). For external markets or where users may want a non-rebasing version, Bracket's wrapper contracts will wrap and create a non-rebasing version:\
\
**Step 1**
To wrap, you must first have the vault asset itself. For instance, if you have deposited wETH into brETH vault, you will receive brETH tokens at the next NAV.
**Step 2**
Navigate to the vault's investment details page and look for the deposit section. One of the tabs will read "Wrap/Unwrap." Click on that tab
**Step 3**\
With your vault token asset, make sure you are on the wrap version. You'll see "BrETH--> wbrETH" as the direction of the wrap in the field. Enter the amount you wish to wrap. Select wrap. \
\
**Step 4**
Approve the limit and transaction in your wallet, and you will receive wrapped tokens
*For unwrapping, simply do the same but at step 3, click "Unwrap" and you'll see the direction of the wrap from "wbrETH-->brETH".*
---
# 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.bracket.fi/user-guides/wrapping-and-unwrapping.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.