Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions docs/developers/build-an-avs/howto/build/add-erc20-token.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
---
sidebar_position: 7
title: Add an ERC-20 Token as a Restakable Asset
---

Any ERC-20 token can be permissionlessly added as a restakable asset, significantly broadening
the scope of assets that can contribute to the security of decentralized networks, and unlocking the cryptoeconomic security of
ERC-20 tokens on EigenLayer. Strategies are contracts that hold assets that are restaked into EigenLayer.

AVSs can choose to accept any ERC-20 token as a restaked asset to provide cryptoeconomic security for
their AVS. This allows AVSs to evaluate the supply and utility of all available tokens to create cross-ecosystem partnerships
while ensuring the safety and security of their services. This increases alignment and connectivity across the ecosystem.

## Adding a New Strategy

To add a new Strategy to the EigenLayer protocol, invoke [`StrategyFactory.deployNewStrategy()`](https://github.com/Layr-Labs/eigenlayer-contracts/blob/main/docs/core/StrategyManager.md#strategyfactorydeploynewstrategy).
The Strategy is now available to be associated with AVSs.

Once the strategy has been added to EigenLayer, add to [Operator Sets for your AVS](manage-operator-sets.md#modify-strategy-composition).

:::note
Custom Strategies have custom bytecode and do not implement `StrategyBase`. Custom Strategies are strategies that are not
deployed via `StrategyFactory.deployNewStrategy()` and require whitelisting via [`StrategyFactory.whitelistStrategies`](https://github.com/Layr-Labs/eigenlayer-contracts/blob/main/docs/core/StrategyManager.md#strategyfactorywhiteliststrategies).

Custom Strategies are not yet supported because the Strategies specification is still evolving alongside the EigenLayer
protocol. AVS developers should build their AVS using the `StrategyBase` interface and functionality, which provides a
stable and supported foundation for integration.
:::
32 changes: 0 additions & 32 deletions docs/developers/build-an-avs/howto/build/avs-permissionlesss.md

This file was deleted.

2 changes: 1 addition & 1 deletion docs/restakers/concepts/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ title: Restaking Overview

## **Liquid & Native Restaking**

**Liquid restaking** is the process of depositing "liquid" tokens, including LSTs, EIGEN token, and any ERC20 token into the EigenLayer smart contracts. For more information about adding new ERC20 tokens, please see [Permissionless Token Strategies](../../developers/build-an-avs/howto/build/avs-permissionlesss.md).
**Liquid restaking** is the process of depositing "liquid" tokens, including LSTs, EIGEN token, and any ERC20 token into the EigenLayer smart contracts. For more information about adding new ERC20 tokens, refer to [Add an ERC-20 Token as a Restakable Asset](../../developers/build-an-avs/howto/build/add-erc20-token).


**Native restaking** is the process of changing an Ethereum validator's[ withdrawal credentials](https://notes.ethereum.org/@launchpad/withdrawals-faq#Q-What-are-withdrawals) to EigenLayer's smart contracts. You must operate an Ethereum Validator node in order to participate in Native Restaking. To learn more or set up your Ethereum Validator please follow this link from the[ Ethereum Foundation](https://launchpad.ethereum.org/).
Expand Down