> For the complete documentation index, see [llms.txt](https://etherfi.gitbook.io/etherfi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://etherfi.gitbook.io/etherfi/resources/ether.fi-whitepaper/ether.fi-re-staking.md).

# ether.fi Re-staking

ether.fi's `eETH` and `weETH` are **Natively ReStaked** tokens.

In a conventional [Liquid ReStaking](https://docs.eigencloud.xyz/products/eigenlayer/restakers/restaking-guides/restaking-developer-guide#liquid-restaking-guide) strategy, the users lock their Liquid Staking Tokens such as `stETH` into the EigenLayer's Liquid ReStaking Strategy contracts. The cons are that the restaked assets are non-transferrable, non-usable in DeFi, and require 14 days withdrawal period for redemption back into the LSTs. Note that you will need additional delays to redeem ETH from your LSTs, again.

In ether.fi's `eETH` and `weETH` where the Native ReStaking happens in the protocol level:

* By holding `eETH/weETH`, you earn the staking rewards based on the staked ETH amount and protocol's staking yields.
* By holding `eETH/weETH`, you earn the restaking rewards based on the natively restaked ETH in the protocol level and protocol's restaking yields (+ EigenLayer points). Users do not need to make separate actions or lock up their assets.
* You can bring your `eETH/weETH` to another DeFi and do degens!
* you can redeem your ETH out of `eETH/weETH` without the 14 days withdrawal period as long as ether.fi has the available liquid ETH in the contract.

Doc's by EigenLayer regarding the process of restaking are provided for guidance on how it works:

* [Native Restaking with EigenLayer](https://docs.eigencloud.xyz/products/eigenlayer/restakers/restaking-guides/restaking-user-guide/native-restaking/)


---

# 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://etherfi.gitbook.io/etherfi/resources/ether.fi-whitepaper/ether.fi-re-staking.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.