> For the complete documentation index, see [llms.txt](https://docs.lossless.io/protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lossless.io/protocol/technical-reference/wrapped-tokens/lossless-wrapped-protection.md).

# Lossless Wrapped Protection

## **Objective** <a href="#objective" id="objective"></a>

The main objective of the Lossless Wrapped Tokens is to provide a more accessible way to integrate the Lossless Core protocol protection into any ERC20 token without the need for relaunching or rewriting the existing smart contract.

With this purpose, there are two contracts from which a Protocol can choose the one that fits their needs the most:

1. [Lossless Wrapped ERC20](https://github.com/Lossless-Cash/wrapped-lossless-erc20/blob/master/src/LosslessWrappedERC20.sol): Contains default Lossless Core protection. Similar to how the LERC20 works. Lacks admin related functions.
2. [Lossless Wrapped ERC20 Ownable](https://github.com/Lossless-Cash/wrapped-lossless-erc20/blob/master/src/LosslessWrappedERC20Ownable.sol): Contains default Lossless Core protection by inheriting from Lossless Wrapped ERC20 smart contract and adds ownership.

### **Smart Contracts** <a href="#smart-contracts" id="smart-contracts"></a>

[Lossless Wrapped ERC20 Repository](https://github.com/Lossless-Cash/wrapped-lossless-erc20)

#### *Base contracts* <a href="#base-contracts" id="base-contracts"></a>

* [Lossless Wrapped ERC20](https://github.com/Lossless-Cash/wrapped-lossless-erc20/blob/master/src/LosslessWrappedERC20.sol)
* [Lossless Wrapped ERC20 Ownable](https://github.com/Lossless-Cash/wrapped-lossless-erc20/blob/master/src/LosslessWrappedERC20Ownable.sol)

#### *Interfaces* <a href="#interfaces" id="interfaces"></a>

* [ILosslessEvents.sol](https://github.com/Lossless-Cash/wrapped-lossless-erc20/blob/master/src/Interfaces/ILosslessEvents.sol)

### **Main Workflow** <a href="#main-workflow" id="main-workflow"></a>

<figure><img src="/files/r9KPSMt7ijHGOgKt7wJR" alt=""><figcaption></figcaption></figure>

### **Usage** <a href="#usage" id="usage"></a>

In order to wrap an ERC20 with Lossless functionality, any of the previously mentioned smart contracts must be deployed.

#### *Ownable variant* <a href="#ownable-variant" id="ownable-variant"></a>

For the Ownable tokens, it is recommended that the owners of the original token deploy the smart contract and use a multisig as recoveryAdmin and the admin of the Wrapped contract. It is important to let the community know and reinforce which is the official wrapped contract, as any token can have multiple wrapped contracts deployed.

This will provide access to all the features of a regular LERC20.

#### *Adminless variant* <a href="#adminless-variant" id="adminless-variant"></a>

For adminless tokens, anyone is able to deploy the base Lossless Wrapped ERC20 with the desired underlying token. The voting process differs from a regular report related to the LERC20, in which the UMA protocol Optimistic Oracle will take the place of the admin when the voting takes place.

One other difference is that any setting at the deployment time will not be able to be changed.

### **Withdrawal Process** <a href="#withdrawal-process" id="withdrawal-process"></a>

In order to properly protect the user funds and provide another window for a report, a minor change has been added to the withdrawal process of the ERC20Wrapped contract.

First, a withdrawal request must be placed. This states that a user wants to unwrap their tokens and will have to wait a certain amount of time (unwrappingDelay) before executing the unwrap.

This provides an extra timeframe for users to generate a report on a potential malicious transaction.


---

# 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.lossless.io/protocol/technical-reference/wrapped-tokens/lossless-wrapped-protection.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.