Merge remote-tracking branch 'upstream/main'

Author: MadelineAu

.github/CODEOWNERS

@@ -1,2 +1,2 @@
-* @dabit3 @wesfloyd @bryangreen @shrimalmadhur @antojoseph @NimaVaziri @scotthconner @MC1823315 @nelsonijih @QuinnLee @mmurrs @non-fungible-nelson
+* @dabit3 @wesfloyd @bryangreen @shrimalmadhur @antojoseph @NimaVaziri @scotthconner @MC1823315 @nelsonijih @QuinnLee @mmurrs @non-fungible-nelson @MadelineAu
 

docs/developers/Concepts/avs-developer-guide.md

@@ -4,16 +4,15 @@ title: AVS Overview
 ---
 
 
-## What is an Actively Validated Service (AVS)?
+## What is an Autonomous Verifiable Service (AVS)?
 
+An Autonomous Verifiable Service (AVS) on EigenLayer is a decentralized service built on Ethereum that provides custom verification mechanisms of off-chain operations. Please see the [Intro to EigenLayer](https://docs.eigenlayer.xyz/eigenlayer/overview/) for background context on the broader EigenLayer ecosystem.
 
-An Actively Validated Service (AVS) on EigenLayer is a decentralized service built on Ethereum that provides custom validation mechanisms of off-chain operations. Please see the [Intro to EigenLayer](https://docs.eigenlayer.xyz/eigenlayer/overview/) for background context on the broader EigenLayer ecosystem.
+An AVS is composed of on-chain contracts for verification and an off-chain network of Operators. Operators execute the service on behalf of the AVS and then post evidence of their execution on-chain to the AVS contracts. Tasks can be initiated via on-chain contracts, off-chain via direct communication with the Operators, or via a task aggregator entity.
 
-An AVS is composed of on-chain contracts for validation and an off-chain network of Operators. Operators execute the service on behalf of the AVS and then post evidence of their execution on-chain to the AVS contracts. Tasks can be initiated via on-chain contracts, off-chain via direct communication with the Operators, or via a task aggregator entity.
-
-The design of the off-chain execution and on-chain validation is entirely flexible based on the needs of the AVS developer. 
-- If the Operators perform tasks properly, the AVS can distribute rewards.
-- If the Operators perform tasks maliciously, their delegate stake can be slashed by the AVS, and the Operator can be removed from the Operator set. 
+The design of the off-chain execution and on-chain verification is entirely flexible based on the needs of the AVS developer. 
+- If the Operators perform tasks properly, the AVS can autonomously distribute rewards.
+- If the Operators perform tasks maliciously, their delegate stake can be slashed autonomously by the AVS, and the Operator can be removed from the Operator set. 
 
  Please see the original EigenLayer whitepaper [EigenLayer: The Restaking Collective](/docs/eigenlayer/overview/whitepaper.md) for further background on AVS design.
 
@@ -22,7 +21,7 @@ The design of the off-chain execution and on-chain validation is entirely flexib
 
 ## Why Build an AVS?
 
-Launching new Web3 projects requires substantial time and effort to bootstrap capital and operators. Builders should focus on their core product differentiators rather than bootstrapping economic security. Building an Actively Validated Service (AVS) on EigenLayer offers enhanced security, decentralization, and cost efficiency by utilizing Ethereum’s staking mechanism through restaking. This allows developers to focus more on their product’s core value and innovation without the significant overhead of setting up a new consensus mechanism or validator networks from scratch.
+Launching new Web3 projects requires substantial time and effort to bootstrap capital and operators. Builders should focus on their core product differentiators rather than bootstrapping economic security. Building an Autonomous Verifiable Service (AVS) on EigenLayer offers enhanced security, decentralization, and cost efficiency by utilizing Ethereum’s staking mechanism through restaking. This allows developers to focus more on their product’s core value and innovation without the significant overhead of setting up a new consensus mechanism or validator networks from scratch.
 
 The key benefits of building an AVS on EigenLayer include:
 - Security via Restaking: leverage Ethereum’s staking mechanism to secure your service.
@@ -34,7 +33,7 @@ The key benefits of building an AVS on EigenLayer include:
 
 ## What Can You Build as an AVS?
 
-The scope of AVS design is broad. It includes **any off-chain service** that can be validated on-chain. This flexibility allows AVS developers to design custom validation mechanisms suited to the unique requirements of their service. The only requirement is that some evidence for the off-chain service’s execution is posted on-chain to enable validation of the service.
+The scope of AVS design is broad. It includes **any off-chain service** that can be verified on-chain. This flexibility allows AVS developers to design custom verification mechanisms suited to the unique requirements of their service. The only requirement is that some evidence for the off-chain service’s execution is posted on-chain to enable verification of the service.
 
 Examples of these services include rollup services, co-processors, cryptography services, zk Proof services, and more.
 

docs/developers/HowTo/avs-opset-slashing.md

@@ -106,3 +106,28 @@ AVS may integrate the AllocationManager via:
 * Specify an additional AVSRegistrar contract that applies business logic to gate Operator registration to an Operator Set.
 
 To ensure community and incentive alignment, it is generally expected that AVSs will conduct off-chain outreach to communicate the purpose and task/security makeup of their Operator Sets with their Operators and Stakers prior to beginning registration.  This likely would include any potential hardware, software, or stake requirements. It is up to the AVS to decide task distribution within an Operator Set.
+
+##  Best Practices
+
+### Operator Set Design
+
+An Operator Set is a grouping of different types of work within a single AVS. Each AVS will have at least one Operator Set. The EigenLayer protocol does not enforce criteria for Operator Sets, however there are a few best practices to consider.
+
+Plan to logically group your AVS tasks (and verification) into separate Operator Sets. First organize your Operator Sets according to which conditions you wish to distribute Rewards for. These conditions could include:
+* Unique business logic.
+* Unique Stake (cryptoeconomic security) amount and types of token required to be allocated from Operators.
+* Slashing conditions.
+* Ejection criteria.
+* Quantity of Operators and criteria for operators allowed.
+* Hardware profiles.
+* Liveness guarantees.
+
+More detail on Operator Sets are available [here](https://docs.eigenlayer.xyz/eigenlayer/operator-guides/operator-sets#operator-sets-currently-in-testnet) and implementation details are available [here](https://docs.eigenlayer.xyz/developers/avs-opset-slashing).
+
+
+
+### Slashing Design and Veto Committees
+
+The EigenLayer protocol allows each AVS builder to design their own slashing conditions. One popular design is to utilize a governance mechanism with slashing such that a committee can review a proposed (or queued) slashing request. That slashing request can then be either fulfilled or vetoed by a committee of domain experts, governance council or multisig address for the AVS. Please see the [vetoable slasher example implementation](https://github.com/Layr-Labs/eigenlayer-middleware/blob/feat/slashing-release-branch/src/slashers/VetoableSlasher.sol) for reference.
+
+Please be sure that your slashing process can be resolved within the DEALLOCATION_DELAY time window. This is the amount of blocks between an Operator queuing a deallocation of stake from an Operator Set for a strategy and the deallocation taking effect. This will ensure that the slashing event is carried out for the Operator before their stake is deallocated.

docs/developers/Reference/resources.md

@@ -24,7 +24,7 @@ These SDKs are wrappers on top of common EigenLayer AVS operations designed to s
 
 ### Developer Tooling
 - [Othentic](https://www.othentic.xyz) - Library of components for AVS builders.
-- [Layer](https://www.layer.xyz/) - Containerized Actively Validated Services (CAVS) via Web Assembly.
+- [Layer](https://www.layer.xyz/) - Containerized Autonomous Verifiable Services (CAVS) via Web Assembly.
 - [AltLayer Wizard](https://wizard.altlayer.io/) - AVS-as-a-Service platform.
 - [Gadget](https://github.com/webb-tools/gadget) - A framework for building modular AVS and Tangle Blueprints.
 

docs/eigenlayer/deployed-contracts/deployed-contracts.md

@@ -5,7 +5,7 @@ title: Contract Addresses and Docs
 
 ## EigenLayer Core Restaking Contracts
 
-The EigenLayer core contracts are located in this repo: [`Layr-Labs/eigenlayer-contracts`](https://github.com/Layr-Labs/eigenlayer-contracts). They enable restaking of liquid staking tokens (LSTs) and beacon chain ETH to secure new services, called AVSs (actively validated services).
+The EigenLayer core contracts are located in this repo: [`Layr-Labs/eigenlayer-contracts`](https://github.com/Layr-Labs/eigenlayer-contracts). They enable restaking of liquid staking tokens (LSTs) and beacon chain ETH to secure new services, called AVSs (Autonomous Verifiable Services).
 
 ### Deployment Addresses
 

docs/eigenlayer/information-and-transparency/faq.md

@@ -11,7 +11,7 @@ title: FAQ
 
 No, EigenLayer is not a DeFi protocol. EigenLayer is a platform to bootstrap new proof of stake (PoS) systems. Through the EigenLayer protocol, users CANNOT engage in any financial activities such as swapping and lending. 
 
-However, for the decentralized services built on top of EigenLayer (we call them AVSs, Actively Validated Services), these services could be DeFi applications themselves or support key functionalities in other DeFi protocols. These AVSs are external to the EigenLayer contracts.
+However, for the decentralized services built on top of EigenLayer (we call them AVSs, Autonomous Verifiable Services), these services could be DeFi applications themselves or support key functionalities in other DeFi protocols. These AVSs are external to the EigenLayer contracts.
 
 Moreover, another class of protocols built on top of EigenLayer is called liquid restaking token (LRT). They function similarly to liquid staking tokens. They are permissionlessly built on EigenLayer. We urge users to do their own research before interacting with LRTs.
 

docs/eigenlayer/overview/README.md

@@ -9,7 +9,7 @@ sidebar_position: 1
 
 Building a new Web3 service comes with significant challenges: bootstrapping crypto-economic security and assembling a reliable network of Operators. Meanwhile, the Web3 ecosystem is rich with opportunities, including a surplus of asset holders eager to earn rewards and skilled Operators seeking to expand into new, value-driven services. EigenLayer bridges this gap, aligning incentives and unlocking untapped potential for both builders and the broader community.
 
-EigenLayer is a protocol built on Ethereum that introduces Restaking, a new primitive for Web3 builders that provides a "marketplace for trust" bringing together Restakers, Operators, and Actively Validated Services (AVSs). It allows users to stake assets such as Native ETH, Liquid Staking Tokens (LSTs), the EIGEN token, or any ERC20 token into EigenLayer smart contracts, thereby extending Ethereum's cryptoeconomic security to additional applications on the network. It fosters innovation by enabling newer projects to benefit from Ethereum’s robust security guarantees without the need to replicate the costly process of securing their own network.
+EigenLayer is a protocol built on Ethereum that introduces Restaking, a new primitive for Web3 builders that provides a "marketplace for trust" bringing together Restakers, Operators, and Autonomous Verifiable Services (AVSs). It allows users to stake assets such as Native ETH, Liquid Staking Tokens (LSTs), the EIGEN token, or any ERC20 token into EigenLayer smart contracts, thereby extending Ethereum's cryptoeconomic security to additional applications on the network. It fosters innovation by enabling newer projects to benefit from Ethereum’s robust security guarantees without the need to replicate the costly process of securing their own network.
 
 AVSs have tools to make economic commitments to their end users, such as proper or fair execution of their code run by Operators. The [Rewards v2 (currently in Testnet) upgrade](https://github.com/eigenfoundation/ELIPs/blob/main/ELIPs/ELIP-001.md#eigenlayer-improvement-proposal-001-rewards-v2) enables AVSs to issue rewards to Operators and Stakers when the AVS’ services are properly run (the carrot). The [Slashing and Operator Sets](https://github.com/eigenfoundation/ELIPs/blob/main/ELIPs/ELIP-002.md) (currently in Testnet) upgrade gives AVSs the ability to slash stake in instances where the commitments to properly run their services are broken (the stick).
 
@@ -31,8 +31,8 @@ The key benefits of building an AVS on EigenLayer include:
 
 The core components of the EigenLayer protocol include:
 
-- **Restaking** enables stakers to restake their Native ETH or Liquid Staking Tokens (LST) to provide security for services in the EigenLayer ecosystem, known as Actively Validated Services (AVSs).
-- **Actively Validated Services (AVSs)** are services built on the EigenLayer protocol that leverage Ethereum's shared security. AVSs deliver services to users and the broader Web3 ecosystem. 
+- **Restaking** enables stakers to restake their Native ETH or Liquid Staking Tokens (LST) to provide security for services in the EigenLayer ecosystem, known as Autonomous Verifiable Services (AVSs).
+- **Autonomous Verifiable Services (AVSs)** are services built on the EigenLayer protocol that leverage Ethereum's shared security. AVSs deliver services to users and the broader Web3 ecosystem. 
 - **Operators** are entities that run AVS software and perform validation tasks for AVSs built on EigenLayer. They register in EigenLayer and allow stakers to delegate to them, then opt in to provide various services (AVSs) built on top of EigenLayer.
 - **Delegation** is the process where stakers delegate their restaked ETH or LSTs to Operators or run validation services themselves, effectively becoming an Operator. This process involves a double opt-in between both parties, ensuring mutual agreement. Restakers retain agency over their stake and choose which AVSs they opt-in to validate for.
 - EigenLayer **Rewards** enables AVSs to make rewards distributions to stakers and operators that opt-in to support the AVS. AVSs make RewardsSubmissions to the RewardsCoordinator, a core protocol contract.

docs/eigenlayer/overview/key-terms.md

@@ -5,7 +5,7 @@ sidebar_position: 2
 
 
 
-- **Actively Validated Services (AVS):**  a service built externally to EigenLayer that requires active validation by a set of Operators. An AVS deploys its service manager to interact with EigenLayer core contracts that allow for Operator registration to Operator Sets, slashing, and rewards distribution. Once registered, an Operator agrees to run the AVS’s off-chain code.
+- **Autonomous Verifiable Services (AVS):**  a service built externally to EigenLayer that requires active verification by a set of Operators. An AVS deploys its service manager to interact with EigenLayer core contracts that allow for Operator registration to Operator Sets, slashing, and rewards distribution. Once registered, an Operator agrees to run the AVS’s off-chain code.
 
 - **Allocation / Deallocation:** an in-protocol commitment of security to an AVS’s Operator Set by an Operator. The act of allocating demarcates portions of an Operator’s delegated stake as Unique Stake, making it slashable by a single AVS. Deallocation is the same process in reverse, subject to additional time delays that ensure AVSs can appropriately slash for tasks that have occurred in the past.
 

docs/eigenlayer/restaking-guides/0-restaking-user-guide/liquid-restaking/restake-lsts.md

@@ -12,10 +12,13 @@ The following instructions will walk you through how tokens can be restaked on t
 
 ![](/img/restake-guides/lst-restake-1.png)
 
-**Step 2:** Click **Restake**.
+**Step 2:** Click **Token** tab to view assets available for restaking.
 
 **Step 3:** Click on the asset you wish to restake. Choose the amount of the asset you wish to restake. Click **Submit** to continue.
 
+:::info
+This guide to Liquid Staking refers to all assets displayed on the Token tab, except for `Natively Staked Ether`, which refers to [Native Staking here](../native-restaking/README.md).
+:::
 ![](/img/restake-guides/lst-restake-2.png)
 
 

docs/eigenlayer/restaking-guides/0-restaking-user-guide/native-restaking/README.md

@@ -28,9 +28,10 @@ We recommend users connect many validators to a single EigenPod in order to redu
 
 Create EigenPod:
 1. Visit the [EigenLayer App](https://app.eigenlayer.xyz/).
-1. Click Create EigenPod.
-1. Sign transaction.
-2. Observe the new EigenPod contract address is displayed.
+1. Click **Natively Staked Ether** via the Dashboard or Token tab.
+1. Click **Create EigenPod**.
+1. **Sign** the transaction via your Web3 wallet when prompted.
+1. Observe the new EigenPod contract address is displayed.
 
 :::info
 This address is responsible for all subsequent restaking and withdrawal activities associated with that EigenPod.
@@ -40,7 +41,7 @@ Repoint Validator:
 1. Configure the validator(s) credentials to point to the EigenPod address when the validator is created. Please see [Ethereum Launchpad](https://launchpad.ethereum.org/en/withdrawals#enabling-withdrawals) for more information. 
     * Confirming Withdrawal Address: you can confirm your withdrawal credentials (which should match your EigenPod), via the following URL: https://beaconcha.in/validator/[validator_index]#deposits
     * Optional: as of the PEPE release you may choose to set the FEE_RECIPIENT to your EigenPod address if you wish to Restake those fees.
-1. Wait for the validator(s) to become active on-chain. Please see https://beaconcha.in/[validator_index] to follow your validator status. Please note: this process could take up to 7 days depending on the Beacon Chain deposit queue.
+1. Wait for the validator(s) to become active on-chain. Please see https://beaconcha.in/[validator_index] to follow your validator status. Please note: this process could take up to 10 days depending on the Beacon Chain deposit queue.
 1. The validator's state will transition to `Awaiting Restake` in the web app.
 
 Activate Restaking:

src/pages/index.js

@@ -57,7 +57,7 @@ function Home() {
                     label:"AVS Developers"
                   }}
                   body={{
-                    label:"Learn how to design, build, and launch an AVS (Actively Validated Service)."
+                    label:"Learn how to design, build, and launch an AVS (Autonomous Verifiable Service)."
                   }}
                 />