# EigenCloud

## Docs

- [AI Resources](get-started/ai-resources): These text and markdown files contain documentation and code optimized for use with LLMs and AI tools.
- [Build Faster with DevKit and Hourglass](get-started/developers/concepts/build-faster-hourglass-devkit): Click here  get started building with DevKit.
- [Understanding AVSs on EigenLayer](get-started/developers/concepts/understanding-avs-on-eigenlayer): What is an AVS
- [Why Build on EigenLayer](get-started/developers/concepts/why-build-on-eigenlayer): What is EigenLayer
- [Build and Test Locally](get-started/developers/howto/build-test-locally): Building with DevKit enables:
- [Publish Task-based AVS](get-started/developers/howto/publish-task-based-avs-release): DevKit publishes your AVS release to the ReleaseManager contract which makes it available for operators to upgrade to.
- [Get Started Building a Task-based AVS](get-started/developers/howto/start-building-task-based-avs): To get started:
- [EigenCloud Overview](get-started/eigencloud/eigencloud-overview): Cloud-scale Programmability, Crypto-grade Verifiability
- [EigenCloud Roadmap](get-started/eigencloud/eigencloud-roadmap): Pillars of EigenCloud
- [Run Task-based AVS](get-started/operators/run-task-based-avs): The Hourglass CLI (hgctl) is a comprehensive CLI toolkit for deploying and managing Hourglass task-based AVS and
- [Building with DevKit and Hourglass](products/devkit/buildingTaskBasedAVS): DevKit and Hourglass are currently in public preview meaning they are in active development.
- [EigenAI Overview](products/eigenai/eigenai-overview): While in Alpha an allowlisted account is required to use the API. If you have a wallet address already for EigenCompute or if you have a separate address, use that address to submit an onboarding request here to receive an API key.
- [Authentication](products/eigencompute/cli-commands/authentication): EigenX CLI requires authentication to sign transactions for deploying and managing applications. These commands help you manage authentication credentials securely.
- [Configuration](products/eigencompute/cli-commands/configuration): Manage CLI settings, check versions, and control telemetry.
- [Deployment & Upgrades](products/eigencompute/cli-commands/deployment): Deploy new applications to TEE instances and upgrade existing deployments with new code or configuration.
- [Environment Management](products/eigencompute/cli-commands/environment): Manage deployment environments to switch between mainnet and testnet.
- [Lifecycle Management](products/eigencompute/cli-commands/lifecycle): Manage the lifecycle of your deployed applications, including starting, stopping, and terminating apps.
- [Monitoring](products/eigencompute/cli-commands/monitoring): Monitor your deployed applications with commands to list apps, view detailed information, and stream logs in real-time.
- [Project Management](products/eigencompute/cli-commands/project-management): These commands help you create new projects and configure existing ones for deployment to EigenX.
- [EigenCompute Overview](products/eigencompute/eigencompute-overview): Follow the EigenX CLI documentation to deploy your application to EigenCompute.
- [Quickstart](products/eigencompute/quickstart): Get started with EigenX CLI and deploy your first verifiable application to a Trusted Execution Environment (TEE) in minutes.
- [Blob Serialization Requirements](products/eigenda/api/disperser-v1-API/blob-serialization-requirements): BN254 Field Element Compatibility
- [API Error Codes](products/eigenda/api/disperser-v1-API/error-codes): There are three categories of response status codes that the EigenDA GRPC API
- [Dispersal Rate Limits](products/eigenda/api/disperser-v1-API/metering-and-rate-limits): Encoded Blob Size
- [Overview](products/eigenda/api/disperser-v1-API/overview): The EigenDA disperser provides an API for dispersing and retrieving blobs to and from the EigenDA network in an untrusted fashion. (Note: as part of its essential data availability guarantee, the EigenDA network already supports direct communication with the EigenDA network for blob retrieval; permissionless dispersal of blobs to the EigenDA network is planned as a future protocol upgrade).
- [Overview](products/eigenda/api/disperser-v2-API/overview): Dispersing Blobs
- [Glossary](products/eigenda/core-concepts/glossary): This glossary provides definitions for core components and related terms of the EigenDA protocol.
- [EigenDA Overview](products/eigenda/core-concepts/overview): EigenDA is a data availability protocol developed by Eigen Labs and built on EigenLayer, live on Mainnet and Sepolia testnet.
- [Payments](products/eigenda/core-concepts/payments): The Payments system streamlines user interactions with the EigenDA, offering clear, flexible options for managing network bandwidth. With the payments update, EigenDA will support two flexible payment modalities:
- [Security FAQs](products/eigenda/core-concepts/security/security-FAQs): The purpose of this post is to review frequently asked questions and better understand security tradeoffs when using DA solutions to Ethereum as an Ethereum L2. Outside of the scope of this is a holistic security assessment of DA.
- [Security Model](products/eigenda/core-concepts/security/security-model): Introduction
- [Using the Go Clients](products/eigenda/integrations-guides/clients/golang-client-v2): EigenDA provides low-level golang clients which wraps the bottom-level GRPC client with ECDSA keypair authentication logic.
- [Custom Security](products/eigenda/integrations-guides/custom-security): EigenDA allows users to tailor their data availability solution while maintaining security guarantees.
- [EigenDA Proxy](products/eigenda/integrations-guides/eigenda-proxy/eigenda-proxy): About
- [Overview](products/eigenda/integrations-guides/overview): To disperse and retrieve payloads, there are three options:
- [V1 Guide](products/eigenda/integrations-guides/quick-start/v1/index): In this guide, we manually disperse and retrieve a blob from the EigenDA disperser. This is an extremely simple example that circumvents most of the complexities needed to benefit from the secure properties
- [V2 Guide](products/eigenda/integrations-guides/quick-start/v2/index): This guide walks through the process of setting up payments and dispersing data using EigenDA on Sepolia.
- [Glossary](products/eigenda/integrations-guides/rollup-guides/glossary): This glossary contains terms related to rollup integrations and EigenDA. It attemps to use stack-agnostic terms, and detail the equivalent terms in the different rollup stacks.
- [Secure Integration Overview](products/eigenda/integrations-guides/rollup-guides/integrations-overview): This document aims to outline what a secure EigenDA integration looks like, to provide rollup
- [OP Stack and EigenDA](products/eigenda/integrations-guides/rollup-guides/op-stack/README): OP Stack is the set of software
- [Deploying a new chain](products/eigenda/integrations-guides/rollup-guides/orbit/deployment): [Arbitrum
- [Migrating an existing chain](products/eigenda/integrations-guides/rollup-guides/orbit/migrating): Defined below is the process for which you can use to migrate your vanilla Arbitrum sequencer using native Arbitrum DA (i.e, Ethereum calldata, 4844 blobs, anytrust) to one using high throughput and low cost via EigenDA. This procedure is identical regardless of your parent chain context (e.g, Ethereum, Arbitrum One) with varying security implications based on the depth of your deployment.
- [Technical overview](products/eigenda/integrations-guides/rollup-guides/orbit/overview): Defined below is a technical breakdown of the key changes we've made to securely enable fraud proofs and high throughput for Arbitrum with EigenDA. This also goes over some key caveats and features.
- [ZK Stack](products/eigenda/integrations-guides/rollup-guides/zksync/README): ZK Stack is ZKsync's rollup framework. We have implemented an EigenDA Client following ZK Stack's validium architecture. Our integration is currently in Stage 1 and we are working towards Stage 2.
- [EigenDA Proxy v1](products/eigenda/integrations-guides/v1/eigenda-proxyv1): About
- [Golang Client](products/eigenda/integrations-guides/v1/golang-client-v1/golang-client-v1): EigenDA offers a low-level golang client which wraps the bottom-level GRPC client with ECDSA keypair authentication logic. That client is available in the EigenDA repo in disperser_client.go. This is a tutorial for getting started using this client.
- [Holesky](products/eigenda/networks/holesky): Holesky is deprecated. It is planned to be completely sunset 2 weeks after the Fusaka hardfork in November.
- [Hoodi](products/eigenda/networks/hoodi): The EigenDA Hoodi testnet is the EigenDA testnet for operators.
- [Mainnet](products/eigenda/networks/mainnet): Quick Links
- [Sepolia](products/eigenda/networks/sepolia): The EigenDA Sepolia testnet is the current EigenDA testnet for integrations.
- [Blazar (V2) Migration](products/eigenda/operator-guides/blazar-migration): Operators running v1 will need to define new v2 specific environment variables, expose 2 new ports, and update their socket registration as part of the migration to v2.
- [Metrics and Monitoring](products/eigenda/operator-guides/metrics-and-monitoring): Setup Grafana and Prometheus Metrics and Monitoring Stack
- [FAQ](products/eigenda/operator-guides/operator-faq): I have a static IP/DNS address. How do I register and fix this address for EigenDA?
- [Overview](products/eigenda/operator-guides/overview): This guide contains the steps needed to set up your node on the EigenDA testnet.
- [Registration Protocol](products/eigenda/operator-guides/registration-protocol): This page contains further background information about the registration process for EigenDA operators. The steps described in this section are performed automatically by the scripts referenced in the registration instructions.
- [Delegation Requirements](products/eigenda/operator-guides/requirements/delegation-requirements): EigenDA operators start by first registering as an EigenLayer operator and meeting stake requirements. These requirements are evaluated on a per-quorum basis, relative to the weighting for each quorum:
- [Protocol SLA](products/eigenda/operator-guides/requirements/protocol-SLA): When operators opt-in to EigenDA, they assume responsibilities imposed by the protocol to provide the EigenDA node service honestly and with at least a certain level of availability and performance. Operators are held accountable for these responsibilities by the network and may face penalties such as ejection for unavailability faults.
- [Requirements Overview](products/eigenda/operator-guides/requirements/requirements-overview): Before deciding to operate an EigenDA node, be sure to fully understand the following aspects of node operation eligibility:
- [System Requirements](products/eigenda/operator-guides/requirements/system-requirements): The following system requirements apply to the Blazar (V2) upgrade and are critical for maintaining optimal node performance and protocol compliance.
- [System Requirements (Deprecated)](products/eigenda/operator-guides/requirements/system-requirements-deprecated): The following system requirements have been deprecated in favor of Blazar (V2) upgrade. Please refer to Blazar (V2) System Requirements.
- [Register Your Operator](products/eigenda/operator-guides/run-a-node/registration): Your operator will not begin receiving traffic from the EigenDA disperser until it has registered for one or more quorums with EigenDA.
- [Overview](products/eigenda/operator-guides/run-a-node/run-overview): If you are able to satisfy all of the eligibility requirements for becoming a node operator, then you're ready to set up and run your node.
- [Run with Docker](products/eigenda/operator-guides/run-a-node/run-with-docker): We provide an Operator Setup Repository which contains various templates that make it easy to run an EigenDA node using docker and docker compose. Operators wishing to make use of other setups can use the docker-compose-based setup as a template for constructing their own custom setups.
- [Troubleshooting](products/eigenda/operator-guides/troubleshooting): Where do I check if my operator is a part of EigenDA set?
- [Software Upgrades](products/eigenda/operator-guides/upgrades/software-upgrades): Please monitor the following channels for updates to EigenDA Operator software:
- [System Upgrades](products/eigenda/operator-guides/upgrades/system-upgrades): Since system requirements scale dynamically in accordance with the amount of stake delegated to the operator, node operators may from time to time need to upgrade their system setups in order to continue meeting the Protocol SLA
- [Blazar (EigenDA V2)](products/eigenda/releases/blazar): Blazar (aka EigenDA V2) release is a comprehensive network upgrade bringing together variety of architectural updates along with more efficient bridging strategies, in order to make EigenDA more performant, robust, and user-friendly.
- [Resources](products/eigenda/resources): Educational resources
- [EigenLayer Overview](products/eigenlayer/concepts/eigenlayer-overview): What is EigenLayer?
- [Key Terms](products/eigenlayer/concepts/key-terms): - 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.
- [Keys and Signatures](products/eigenlayer/concepts/keys-and-signatures): In the EigenLayer ecosystem, signatures play a crucial role in ensuring the integrity and authenticity of operations.
- [Allocation and Deallocation](products/eigenlayer/concepts/operator-sets/allocation-deallocation): Allocations
- [Operator Sets Overview](products/eigenlayer/concepts/operator-sets/operator-sets-concept): ELIP-006 Redistributable Slashing introduced Redistributable Operator Sets, and is now available on mainnet.
- [Strategies and Magnitudes](products/eigenlayer/concepts/operator-sets/strategies-and-magnitudes): ELIP-002 Slashing via Unique Stake & Operator Sets introduced Operator Sets.
- [Earners, Claimers, and Reward Recipients](products/eigenlayer/concepts/rewards/earners-claimers-recipients): Earners are addresses that accrue Rewards within the EigenLayer ecosystem and are Stakers, Operators, or in the case of refunds,
- [Programmatic Incentives Split](products/eigenlayer/concepts/rewards/pi-split): Programmatic Incentives are EIGEN tokens minted by the EigenLayer protocol to Stakers and Operators.
- [Rewards Claiming](products/eigenlayer/concepts/rewards/rewards-claiming): The process to claim rewards is the same for AVS Rewards and Programmatic Incentives. That is, both AVS Rewards and Programmatic
- [Rewards Claiming FAQ](products/eigenlayer/concepts/rewards/rewards-claiming-faq): When can I claim my rewards?
- [Overview](products/eigenlayer/concepts/rewards/rewards-concept): Rewards are tokens distributed to Stakers and Operators by an AVS to reward Stakers and Operators for participation in securing AVSs.
- [Rewards Split](products/eigenlayer/concepts/rewards/rewards-split): Operators earn rewards by opting into the Operator Sets of AVSs that implement Rewards. By default, Operators earn a 10% split
- [Rewards Submission](products/eigenlayer/concepts/rewards/rewards-submission): AVSs make rewards submissions specifying:
- [Magnitudes when Slashed](products/eigenlayer/concepts/slashing/magnitudes-when-slashed): If you're new to slashing in EigenLayer, make sure you're familiar with Operator Sets
- [Redistribution](products/eigenlayer/concepts/slashing/redistribution): ELIP-006 Redistributable Slashing introduced Redistributable Operator Sets, and is now available on mainnet.
- [Safety Delays](products/eigenlayer/concepts/slashing/safety-delays-concept): Stake delegated to an Operator can become slashable, and when redistributable slashing is live on mainnet, previously delegated
- [Slashable Stake Risks](products/eigenlayer/concepts/slashing/slashable-stake-risks): Stake delegated to an Operator can become slashable, and when redistributable slashing is live on mainnet, previously delegated
- [Overview](products/eigenlayer/concepts/slashing/slashing-concept): ELIP-006 Redistributable Slashing introduced Redistributable Operator Sets, and is now available on mainnet.
- [Unique Stake](products/eigenlayer/concepts/slashing/unique-stake): Unique Stake ensures AVSs and Operators maintain key safety properties when handling staked security and slashing on EigenLayer.
- [Accounts](products/eigenlayer/concepts/uam/uam-accounts): The account is the Ethereum address that interacts with the EigenLayer core contracts if no appointees are set.
- [Admins](products/eigenlayer/concepts/uam/uam-admins): Admins can take any action on behalf of the original account that appointed them including adding or removing admins. Creating
- [Appointees](products/eigenlayer/concepts/uam/uam-appointees): Appointees act as another account for a specific function for a specific contract, granting accounts granular access control.
- [User Access Management](products/eigenlayer/concepts/uam/user-access-management): UAM implements ELIP-003: User Access Management (UAM).
- [Whitepapers](products/eigenlayer/concepts/whitepaper): EigenLayer the research paper that formed the basis of the EigenLayer protocol development. The document discusses the original architecture of EigenLayer, the Restaking primitive, and the concept of AVSs. Please note that some components of the design have changed since the original conception of the protocol. Use this document for high level guidance. For specific implementation details, please see the respective protocol implementation source code repositories.
- [AVS Contracts](products/eigenlayer/developers/concepts/avs-contracts): The AVS contracts are the contracts that call the EigenLayer contacts. An AVS can split onchain components across
- [AVS Overview](products/eigenlayer/developers/concepts/avs-developer-guide): What is an Autonomous Verifiable Service (AVS)?
- [AVS Security Models](products/eigenlayer/developers/concepts/avs-security-models): The security model of an AVS defines who or what is trusted in an AVS, and under what conditions that trust holds. AVSs may
- [EigenLayer Core Contracts](products/eigenlayer/developers/concepts/eigenlayer-contracts/core-contracts): The EigenLayer core contracts are the set of contracts that are implemented and maintained by EigenLabs and upgradeable by
- [Contract Addresses and Docs](products/eigenlayer/developers/concepts/eigenlayer-contracts/deployed-contracts): EigenLayer Core Restaking Contracts
- [EigenLayer Middleware Contracts](products/eigenlayer/developers/concepts/eigenlayer-contracts/middleware-contracts): The EigenLayer middleware contracts are higher level interfaces to the EigenLayer core contracts.
- [Certificates](products/eigenlayer/developers/concepts/multichain/certificates): A certificate is a proof of a task being executed offchain by the Operators of an Operator Set. Typically, a certificate consists of an
- [Architecture](products/eigenlayer/developers/concepts/multichain/multichain-architecture): The Multichain Verification framework uses the core contracts and templates in EigenLayer middleware described in the table.
- [Overview](products/eigenlayer/developers/concepts/multichain/multichain-overview): Multichain verification is early-access and in active development. Expect iterative updates before the mainnet release.
- [Stake Weighting](products/eigenlayer/developers/concepts/multichain/stake-weighting): The OperatorTableCalculator defines how Operator stakes are weighted and formatted for your specific use case.
- [Key Management for Redistributable Slashing](products/eigenlayer/developers/concepts/slashing/key-management-redistributable-slashing): When implementing redistributable slashing, AVSs face significantly heightened security requirements. Unlike burn-only slashing where compromised keys result in destroyed funds, redistributable slashing allows attackers to steal funds directly.
- [Slashing](products/eigenlayer/developers/concepts/slashing/slashing-concept-developers): For information on how slashing works, refer to concept content on Slashing and
- [Tasks](products/eigenlayer/developers/concepts/task): Tasks are a common design model used for AVS operations. The task design model is not required by the EigenLayer protocol but
- [User Access Management](products/eigenlayer/developers/concepts/uam-for-avs): There is no support for setting appointees for AVSDirectory functions. The AVSDirectory method will be deprecated in a future upgrade.
- [Add ERC-20 Tokens as Restakable Asset](products/eigenlayer/developers/howto/build/avs-permissionlesss): Permissionless token support enables any ERC-20 token to be permissionlessly added as a restakable asset, significantly broadening
- [Manage Registered Operators](products/eigenlayer/developers/howto/build/manage-registered-operators): AVSRegistrar
- [Multichain Security Considerations](products/eigenlayer/developers/howto/build/multichain-security-considerations): The following table outlines the key security aspects to consider when implementing multichain verification services.
- [Configure Multichain AVS](products/eigenlayer/developers/howto/build/multichain/configure-multichain): Multichain verification is early-access and in active development. Expect iterative updates before the mainnet release.
- [Consume certificates](products/eigenlayer/developers/howto/build/multichain/consume-certificates): Obtain, Verify, and Act On Certificates
- [Create and Deliver Certificates](products/eigenlayer/developers/howto/build/multichain/implement-certificate-verification): The AVS developer needs to enable their service to produce stake-backed certificates that are verifiable by
- [Overview](products/eigenlayer/developers/howto/build/multichain/multichain-howto-overview): The following diagram shows:
- [Verify certificates](products/eigenlayer/developers/howto/build/multichain/verification-methods): This topic includes:
- [Create Operator Sets](products/eigenlayer/developers/howto/build/operator-sets/create-operator-sets): If you're new to Operator Sets in EigenLayer, review the Operator Sets concepts before continuing with this topic.
- [Design Operator Sets](products/eigenlayer/developers/howto/build/operator-sets/design-operator-set): An Operator Set is a grouping of different types of work within a single AVS. Each AVS has at least one Operator Set. The
- [Migrate to Operator Sets](products/eigenlayer/developers/howto/build/operator-sets/migrate-to-operatorsets): The AVSDirectory method will be deprecated in a future upgrade. All AVSs will need to migrate to Operator Sets before the
- [Modify Strategy Composition](products/eigenlayer/developers/howto/build/operator-sets/modify-strategy-composition): An Operator Set requires at least one Strategy.
- [Update AVS Metadata](products/eigenlayer/developers/howto/build/operator-sets/update-avs-metadata): The AVS metadata is used to provide information on the EigenLayer App for Stakers and Operators.
- [Register AVS Metadata](products/eigenlayer/developers/howto/build/register-avs-metadata): Metadata must be registered:
- [Implement Slashing](products/eigenlayer/developers/howto/build/slashing/implement-slashing): If you're new to slashing in EigenLayer, make sure you're familiar with Operator Sets
- [Precision and Rounding Considerations](products/eigenlayer/developers/howto/build/slashing/precision-rounding-considerations): Slashing in very small increments, slashing operators with very low magnitudes, or slashing operators with very low share balances may lead to precision loss that results in burned and redistributed amounts being far lower than expected.
- [Risk Assessment for Redistributable Slashing](products/eigenlayer/developers/howto/build/slashing/risk-assessment-redistributable-slashing): Before implementing redistributable slashing, AVSs should conduct:
- [Security for Redistributable Slashing](products/eigenlayer/developers/howto/build/slashing/security-redistributable-slashing): Redistributable slashing increases the attack surface and potential impact of security vulnerabilities. AVSs must implement additional security measures beyond what would be required for burn-only slashing.
- [Design Slashing](products/eigenlayer/developers/howto/build/slashing/slashing-veto-committee-design): Slashing Vetoes
- [Submit Rewards Submissions](products/eigenlayer/developers/howto/build/submit-rewards-submissions): RewardsCoordinator.createAVSRewardsSubmission and RewardsCoordinator.createOperatorDirectedAVSRewardsSubmission use AVSDirectory.
- [Add and Remove Admins](products/eigenlayer/developers/howto/build/uam/dev-add-remove-admins): Security of admin keys is critical. UAM enables appointees with lessened permissions, and use of keys that can be rotated or
- [Add and Remove Appointees](products/eigenlayer/developers/howto/build/uam/dev-add-remove-appointees): Only admins (or the account if no admin has been set) can add appointees. Unlike adding an admin, there is no requirement
- [Prepare for and Deploy to Testnet and Mainnet](products/eigenlayer/developers/howto/deploy/deployment-testnet-mainnet): Preparing and Deploying to Testnet
- [Implement onchain components](products/eigenlayer/developers/howto/get-started/implement-minimum-onchain-components): To build an AVS, the minimum set of functionality to be defined in the AVS contracts is:
- [Get started](products/eigenlayer/developers/howto/get-started/quickstart): We are in the process of updating our samples to include Rewards and Slashing capabilities. The Hello World AVS example will be
- [Get Support](products/eigenlayer/developers/howto/get-started/support): If you have any questions or comments throughout the AVS development process, you can get support by reaching out to us using
- [Onboard to AVS Dashboard](products/eigenlayer/developers/howto/publish/onboard-avs-dashboard): The AVS Dashboard (also known as AVS Marketplace) lists registered AVSs.
- [Obtain Testnet ETH](products/eigenlayer/developers/howto/test/obtain-testnet-eth): The Obtaining testnet ETH and liquid staking tokens (LSTs) topic describes how to obtain testnet ETH and LSTs for
- [Test AVS](products/eigenlayer/developers/howto/test/test-avs): AVS Devnet is currently in Public Alpha and is rapidly being upgraded. Features may be added, removed or otherwise improved or modified,
- [AVS Developer Security Best Practices](products/eigenlayer/developers/reference/avs-developer-best-practices): AVS Developer Security Best Practices
- [EigenLayer SDKs](products/eigenlayer/developers/reference/eigenlayer-sdks): The EigenLayer SDKs wrap common EigenLayer AVS operations and are designed for AVS developers.
- [Multichain Parameters](products/eigenlayer/developers/reference/multichain-parameters): Protocol parameters for multichain verification include:
- [Developer Resources](products/eigenlayer/developers/reference/resources): We are in the process of updating our samples, SDKs, and the EigenLayer CLI to include Rewards and Slashing capabilities. The samples, SDKs, and CLI will be
- [Acceptable Use Policy](products/eigenlayer/legal/acceptable-use-policy): EigenCloud Acceptable Use Policy
- [Disclaimers](products/eigenlayer/legal/disclaimers): Last Revised on September 30, 2024
- [Disclosures Related to Employee and Investor Staking](products/eigenlayer/legal/disclosures): Last Revised on September 30, 2024
- [Privacy Policy](products/eigenlayer/legal/privacy-policy): Last Revised on March 20, 2024
- [Terms of Service](products/eigenlayer/legal/terms-of-service): Last Revised on June 17, 2025
- [Overview](products/eigenlayer/operators/concepts/operator-introduction): What is a Node Operator within EigenLayer?
- [Operator Keys](products/eigenlayer/operators/concepts/operator-keys): For information on Operator keys, refer to Keys.
- [User Access Management](products/eigenlayer/operators/concepts/uam-for-operators): For concept material on User Access Management (UAM) and roles, refer to:
- [Implement Security Best Practices](products/eigenlayer/operators/howto/avs-operator-risks-mitigations-bp): Malicious AVS
- [Batch Claim Rewards](products/eigenlayer/operators/howto/claimrewards/batch-claim-rewards): Batch rewards claiming for Stakers and Operators using the EigenLayer CLI is a gas efficient way to claim on behalf
- [Claim Rewards](products/eigenlayer/operators/howto/claimrewards/claim-rewards-cli): Prerequisites
- [Claim Rewards as a Smart Contract](products/eigenlayer/operators/howto/claimrewards/claim-rewards-smart-contract): To claim rewards when the Earner is a smart contract,
- [Rewards Distribution Data](products/eigenlayer/operators/howto/configurerewards/rewards-snapshot-data): After July 16, Rewards snapshot distribution data will no longer be updated in the public S3 bucket. To continue getting updated rewards data,
- [Set Programmatic Incentives Split](products/eigenlayer/operators/howto/configurerewards/set-pi-split): The default Operator split for Programmatic Incentives (PI) is 10%.
- [Set Rewards Claimer](products/eigenlayer/operators/howto/configurerewards/set-rewards-claimer): Prerequisites
- [Set Rewards Split](products/eigenlayer/operators/howto/configurerewards/set-rewards-split): The default Operator split for rewards is 10%. The Operator split can be varied by AVS or by Operator Set.
- [Node and Smart Contract Operators](products/eigenlayer/operators/howto/managekeys/institutional-operators): - Secure keys, including secrets such as passphrases or mnemonics, using services like AWS Secrets Manager or Hashicorp Vault. These services can be seamlessly integrated with automated mechanisms that safely retrieve secrets or keys (e.g., remote signers). If resources permit, consider running your own Hashicorp Vault instance, which grants full custody of keys and secrets while sacrificing the service provider's availability and security guarantees.
- [Solo stakers](products/eigenlayer/operators/howto/managekeys/solo-stakers): Individuals managing a limited number of validator keys typically do not require intricate distributed infrastructure for running nodes or employing remote signers. For these individuals, extensive staking services may be excessive and unnecessary. This means they will often store the keys with the decryption keys locally with the validator client or Node (which they maintain), which increases the vulnerability of the secrets, but, while stakers must safeguard validator keys against attacks, most key losses typically result from mundane reasons, such as losing the hardware containing the key. Users necessitate a backup strategy, mindful that if an attacker accesses the backed-up keys, they can sign any message deemed valid against the validator's public key. Appropriate precautions should be implemented to guarantee that backed-up validator keys are as inaccessible as feasible, ideally being completely offline and physically secure. Some of these precautions can be listed:
- [Run Multichain Services](products/eigenlayer/operators/howto/mulitchain): To operate a multichain verification service, the following is required:
- [Follow Webapp Content Guidelines](products/eigenlayer/operators/howto/operator-content-guidelines): Operator Page
- [Allocate and Register to Operator Set](products/eigenlayer/operators/howto/operator-sets): Before proceeding, review the Slashing Concept content for information on how Operator Sets, Allocations, and Redistribution work.
- [Install and Register Operators](products/eigenlayer/operators/howto/registeroperators/operator-installation): Node Operator Checklist
- [Install and Register Operators using Fireblocks](products/eigenlayer/operators/howto/registeroperators/register-operator-with-fireblocks): The steps below specify how to onboard to EigenLayer and connect to an AVS when using Fireblocks.
- [Troubleshoot](products/eigenlayer/operators/howto/troubleshooting): Before creating an issue with EigenLayer support please check this page to see if you can resolve your issues. If you are still stuck, please create a support ticket
- [Add and Remove Admins](products/eigenlayer/operators/howto/uam/op-add-remove-admins): Security of admin keys is critical. UAM enables appointees with lessened permissions, and use of keys that can be rotated or
- [Add and Remove Appointees](products/eigenlayer/operators/howto/uam/op-add-remove-appointees): Only admins (or the account if no admin has been set) can add appointees. Unlike adding an admin, there is no requirement
- [Operator FAQ](products/eigenlayer/operators/reference/operator-faq): Am I required to publicly host metadata url?
- [APIs, Dashboards, and Tooling](products/eigenlayer/reference/apis-and-dashboards): APIs
- [Economy Calculation and Formulas](products/eigenlayer/reference/economy/economy-calculation-and-formulas): Overview
- [Sidecar](products/eigenlayer/reference/economy/sidecar): Overview
- [Learning Resources](products/eigenlayer/reference/learning-resources): Start here
- [Safety Delays](products/eigenlayer/reference/safety-delays-reference): ELIP-006 Redistributable Slashing introduced Redistributable Operator Sets with instant redistribution.
- [Releases and Compatibility Matrix](products/eigenlayer/releases): The table displays:
- [Native ETH Restaking Withdrawal Delays](products/eigenlayer/restakers/concepts/native-restaking-withdrawal-delays): Withdrawing funds from BeaconChain to an EigenPod and ultimately to a user’s wallet involves multiple sequential steps with
- [Restaking Overview](products/eigenlayer/restakers/concepts/overview): Liquid & Native Restaking
- [Claim Rewards using EigenLayer App](products/eigenlayer/restakers/restaking-guides/claim-rewards-app): For information on Rewards concepts, refer to Rewards Overview.
- [Restaking Smart Contract Developer](products/eigenlayer/restakers/restaking-guides/restaking-developer-guide): Smart Contract Restaking allows the user to interact directly with the EigenLayer core contracts. The following sections describe how to setup your Restaking integration with the EigenLayer contracts directly with no reliance on the EigenLayer Web App.
- [Restake and Delegate](products/eigenlayer/restakers/restaking-guides/restaking-user-guide/liquid-restaking/restake-lsts): The following instructions will walk you through how tokens can be restaked on the EigenLayer Web App.
- [Unstake and Withdraw](products/eigenlayer/restakers/restaking-guides/restaking-user-guide/liquid-restaking/withdraw-from-eigenlayer): Unstaking is the first step in the process of exiting restaked assets from EigenLayer. Unstaked tokens enter the withdrawal
- [Native Restaking](products/eigenlayer/restakers/restaking-guides/restaking-user-guide/native-restaking/README): Please read this entire guide before launching your new validator or integrating your existing validator. Before you deploy a new validator you must plan to either:
- [Delegate to an Operator](products/eigenlayer/restakers/restaking-guides/restaking-user-guide/restaker-delegation/delegate-to-an-operator): Follow the steps below to initiate delegation of your Restaked balance to an Operator of your choice. This Restaked balance includes EIGEN tokens, LST tokens, and Native Restaked TVL.
- [Change Your Delegation](products/eigenlayer/restakers/restaking-guides/restaking-user-guide/restaker-delegation/redelegation-process): The following steps are necessary for a Restaker to move their Delegated balance to a New Operator. The process below requires users to perform each of the following steps in order:
- [Undelegate and Initiate Withdrawal](products/eigenlayer/restakers/restaking-guides/restaking-user-guide/restaker-delegation/undelegate-from-an-operator-and-initiate-withdrawal): Restakers can Undelegate their balance from an Operator at any time. Undelegation flows are the same for both Native and LST Restakers.
- [Obtaining Testnet ETH & Liquid Staking Tokens (LSTs)](products/eigenlayer/restakers/restaking-guides/testnet/obtaining-testnet-eth-and-liquid-staking-tokens-lsts): To obtain testnet ETH, use a faucet to load your wallet with testnet ETH.
- [Testnet Restaking](products/eigenlayer/restakers/restaking-guides/testnet/README): Testing Restaking on the Holesky Testnet
- [Restaking Smart Contract Developer (Testnet)](products/eigenlayer/restakers/restaking-guides/testnet/restaking-developer-guide): The following instructions include an overview of the changes to Smart Contract Restaking per the Slashing and Operator Set release. All existing instructions on Restaking Smart Contract Developer remain unchanged for this update, except where noted below.
- [Audits](products/eigenlayer/security/audits): As a key component of our development process, please see the most recent audits that help assess the robustness and reliability of our systems:
- [Bug Bounty](products/eigenlayer/security/bug-bounty): Check out the official bug bounty program for EigenLayer on Immunefi
- [Guardrails](products/eigenlayer/security/guardrails): There will be a 14-day withdrawal delay that will serve as a security measure during the early stages of the EigenLayer mainnet, to optimize for the safety of assets. This withdrawal lag, which is common in staking protocols, is required when AVSs go live, as there is a lag to verify that activity associated with any AVS was completed successfully.
- [Governance](products/eigenlayer/security/multisig-governance): Please see EigenFoundation Governance for latest information.
- [Withdrawal Delay](products/eigenlayer/security/withdrawal-delay): EigenLayer contracts feature a withdrawal delay for LST tokens, EIGEN token, and Native Restaking, a critical security measure for instances of vulnerability disclosure or when anomalous behavior is detected by monitoring systems. The delays serve as a preventive mechanism and also allows, in certain cases, to help mitigate protocol attacks. When contracts are paused and withdrawals disabled, the system enables arbitrary state or code changes to the contracts through upgrades. While technically feasible, such interventions are not a routine practice and should be approached with caution.
- [Community and Support](products/eigenlayer/support): Community
- [EigenVerify Overview](products/eigenverify/eigenverify-overview): What is EigenVerify?