EigenLayer

June 24, 2026 ยท View on GitHub

EigenLayer

EigenLayer is a protocol built on Ethereum that introduces Restaking, a primitive for app and service builders to make verifiable commitments to their users.

EigenLayer brings together Restakers, Operators, and Autonomous Verifiable Services (AVSs) to extend Ethereum's cryptoeconomic security with penalty and reward commitments (like slashing) on staked assets acting as security. The protocol supports permissionless security; EIGEN, Native ETH, LSTs, and ERC-20s.

Deployments

The deployments on mainnet, base, sepolia, hoodi, and base sepolia are on the below versions:

EnvironmentVersionCore Protocol DeployedSupports Native RestakingSupports Multichain
Mainnet Ethereumv1.13.0YesYesYes (source & destination)
Basev1.9.0NoNoYes (destination)
Testnet Sepoliav1.12.1YesNoYes (source & destination)
Testnet Hoodiv1.11.0YesYesNo
Testnet Base Sepoliav1.9.0NoNoYes (destination)

Current Deployment Contracts

Mainnet Ethereum
Core
NameProxyImplementationNotes
DelegationManager0x39053D51B77DC0d36036Fc1fCc8Cb819df8Ef37A0xE702...cE75Proxy: TUP@4.7.1
StrategyManager0x858646372CC42E1A627fcE94aa7A7033e7CF075A0xa753...656AProxy: TUP@4.7.1
EigenPodManager0x91E677b07F7AF907ec9a428aafA9fc14a0d3A3380xd22d...E9dBProxy: TUP@4.7.1
AVSDirectory0x135dda560e946695d6f155dacafc6f1f25c1f5af0xcD35...862bProxy: TUP@4.7.1
RewardsCoordinator0x7750d328b314EfFa365A0402CcfD489B80B0adda0xa067...3C26Proxy: TUP@4.7.1
PermissionController0x25E5F8B1E7aDf44518d35D5B2271f114e081f0E50x36dd...EEd2Proxy: TUP@4.9.0
AllocationManager0x948a420b8CC1d6BFd0B6087C2E7c344a2CD0bc390xdA2A...97C4Proxy: TUP@4.9.0
EmissionsController0x619F988b4EA2f896ED068d84cE6F52550d6acE840x29Db...CA01Proxy: TUP@4.7.1
Strategies

Anyone can deploy and whitelist strategies for standard ERC20s by using the StrategyFactory deployed to the address below (see docs). Strategies deployed from the StrategyFactory are deployed using the beacon proxy pattern:

NameProxyImplementationNotes
StrategyFactory0x5e4C39Ad7A3E881585e383dB9827EB4811f6F6470xbbc4...2b76Proxy: TUP@4.7.1
StrategyBase0x0ed6703C298d28aE0878d1b28e88cA87F9662fE90x8F6b...1Ce- Beacon: BeaconProxy
- Strategies: UpgradeableBeacon
DurationVaultStrategy0x0fCE0A591D96BB76883323eF555867111E2050a90xc946...8903- Beacon: BeaconProxy
- Strategies: UpgradeableBeacon

The following strategies were originally deployed and whitelisted outside of the StrategyFactory:

NameProxyImplementationNotes
StrategyBase (cbETH)0x54945180dB7943c0ed0FEE7EdaB2Bd24620256bc0xB427...7230Proxy: TUP@4.7.1
StrategyBase (stETH)0x93c4b944D05dfe6df7645A86cd2206016c51564D0xB427...7230Proxy: TUP@4.7.1
StrategyBase (rETH)0x1BeE69b7dFFfA4E2d53C2a2Df135C388AD25dCD20xB427...7230Proxy: TUP@4.7.1
StrategyBase (ETHx)0x9d7eD45EE2E8FC5482fa2428f15C971e6369011d0xB427...7230Proxy: TUP@4.7.1
StrategyBase (ankrETH)0x13760F50a9d7377e4F20CB8CF9e4c26586c658ff0xB427...7230Proxy: TUP@4.7.1
StrategyBase (OETH)0xa4C637e0F704745D182e4D38cAb7E7485321d0590xB427...7230Proxy: TUP@4.7.1
StrategyBase (osETH)0x57ba429517c3473B6d34CA9aCd56c0e735b94c020xB427...7230Proxy: TUP@4.7.1
StrategyBase (swETH)0x0Fe4F44beE93503346A3Ac9EE5A26b130a5796d60xB427...7230Proxy: TUP@4.7.1
StrategyBase (wBETH)0x7CA911E83dabf90C90dD3De5411a10F1A61121840xB427...7230Proxy: TUP@4.7.1
StrategyBase (sfrxETH)0x8CA7A5d6f3acd3A7A8bC468a8CD0FB14B6BD28b60xB427...7230Proxy: TUP@4.7.1
StrategyBase (lsETH)0xAe60d8180437b5C34bB956822ac27109725844730xB427...7230Proxy: TUP@4.7.1
StrategyBase (mETH)0x298aFB19A105D59E74658C4C334Ff360BadE6dd20xB427...7230Proxy: TUP@4.7.1
Strategies - Special

The following strategies differ significantly from the other strategies deployed/used above:

NameProxyImplementationNotes
EigenStrategy (EIGEN)0xaCB55C530Acdb2849e6d4f36992Cd8c9D50ED8F70x509A...8f40Proxy: TUP@4.9.0
Beacon Chain ETH0xbeaC0eeEeeeeEEeEeEEEEeeEEeEeeeEeeEEBEaC0-- Used for Beacon Chain ETH shares
- Not a real contract!
EigenPods
NameProxyImplementationNotes
EigenPod (beacon)0x5a2a4F2F3C18f09179B6703e63D9eDD1659090730x53cC...e868- Beacon: BeaconProxy
- Pods: UpgradeableBeacon
EIGEN/bEIGEN
NameProxyImplementationNotes
Eigen0xec53bf9167f50cdeb3ae105f56099aaab9061f830x2C4A...2E50Proxy: TUP@4.9.0
Backing Eigen0x83E9115d334D248Ce39a6f36144aEaB5b3456e750xF2b2...9b17Proxy: TUP@4.9.0
SignedDistributor-0x035b...ad02-
AVS

The following contracts are used by AVSs.

NameProxyImplementationNotes
ReleaseManager0xeDA3CAd031c0cf367cF3f517Ee0DC98F9bA80C8F0xD0cb...13bdProxy: TUP@4.9.0
TaskMailbox0x132b466d9d5723531F68797519DfED701aC2C7490xA2A9...c55eProxy: TUP@4.9.0
Multichain - Source

The multichain protocol expects AVSs to register on the source chain. AVS's stakes are then transported to supported destination chains. For the mainnet Ethereum network, the destination chains include Base.

NameProxyImplementationNotes
CrossChainRegistry0x9376A5863F2193cdE13e1aB7c678F22554E2Ea2b0xdc23...642CProxy: TUP@4.9.0
KeyRegistrar0x54f4bC6bDEbe479173a2bbDc31dD7178408A57A40x0f93...C219Proxy: TUP@4.9.0
Multichain - Destination
NameProxyImplementationNotes
OperatorTableUpdater0x5557E1fE3068A1e823cE5Dcd052c6C352E2617B50x8c4F...adF7Proxy: TUP@4.9.0
ECDSACertificateVerifier0xd0930ee96D07de4F9d493c259232222e46B6EC250x2d52...40dCProxy: TUP@4.9.0
BN254CertificateVerifier0x3F55654b2b2b86bB11bE2f72657f9C33bf88120A0x9907...eaD2Proxy: TUP@4.9.0
Multisigs
NameProxyImplementationNotes
PauserRegistry-0xB876...2806
OZ: TimelockController-0xC06F...Aa2d
OZ: TimelockController (BEIGEN)-0x7381...bc53
OZ: Proxy Admin-0x8b95...2444
Pauser Multisig0x5050389572f2d220ad927CcbeA0D406831012390-
Community Multisig0xFEA47018D632A77bA579846c840d5706705Dc598-
Executor Multisig0x369e6F597e22EaB55fFb173C6d9cD234BD699111-
Operations Multisig0xBE1685C81aA44FF9FB319dD389addd9374383e90-
Protocol Council Multisig0x461854d84ee845f905e0ecf6c288ddeeb4a9533f-
Foundation Multisig0xbb00DDa2832850a43840A3A86515E3Fe226865F2-
BEIGEN Executor Multisig0x942eaF324971440384e4cA0ffA39fC3bb369D67d-
Multichain Deployer Multisig0xa3053EF25F1F7d9D55a7655372B8a31D0f40eCA9-
Base

Note: Base only supports verification of tasks from stake that lives on Mainnet Ethereum. Standard core protocol functionality (restaking, slashing) does not exist on Base.

Multichain - Destination
NameProxyImplementationNotes
OperatorTableUpdater0x5557E1fE3068A1e823cE5Dcd052c6C352E2617B50x792F...419DProxy: TUP@4.9.0
ECDSACertificateVerifier0xd0930ee96D07de4F9d493c259232222e46B6EC250xf2cC...025FProxy: TUP@4.9.0
BN254CertificateVerifier0x3F55654b2b2b86bB11bE2f72657f9C33bf88120A0xc6c7...5D7dProxy: TUP@4.9.0
AVS

The following contracts are used by AVSs.

NameProxyImplementationNotes
TaskMailbox0x132b466d9d5723531F68797519DfED701aC2C7490x6eD2...c1bdProxy: TUP@4.9.0
Multisigs
NameProxyImplementationNotes
PauserRegistry-0xb175...6ea
OZ: TimelockController-0xE48D...ABd
OZ: Proxy Admin-0xDb00...9CE
Pauser Multisig0x1a051eF1524cbaEa57Ca04319ef93fE78903D5E6-
Operations Multisig0x8eD55c7640497Db15aC32c698c1a06E2E604d865-
Protocol Council Multisig0x841B988aaEafce13b6456ff34015FBc42Aedb7e6-
Community Multisig0xC107547924C7D1d3E2d10eA8DF534BBfC5F373e6-
Executor Multisig0x5d808608Ad70873ca4dE50F83416264dc15264C2-
Multichain Deployer Multisig0xa3053EF25F1F7d9D55a7655372B8a31D0f40eCA9-
Testnet Sepolia

You can view the deployed contract addresses below, or check out the code itself on the testnet-sepolia branch.

Core
NameProxyImplementationNotes
DelegationManager0xD4A7E1Bd8015057293f0D0A557088c286942e84b0xa6Fe...C0f5Proxy: TUP@4.9.0
StrategyManager0x2E3D6c0744b10eb0A4e6F679F71554a39Ec47a5D0x7D59...E6F1Proxy: TUP@4.9.0
EigenPodManager0x56BfEb94879F4543E756d26103976c567256034a0x151e...75D4Proxy: TUP@4.9.0
AVSDirectory0xa789c91ECDdae96865913130B786140Ee17aF5450x3216...6D69Proxy: TUP@4.9.0
RewardsCoordinator0x5ae8152fb88c26ff9ca5C014c94fca3c680293490x5Ac1...FF61Proxy: TUP@4.9.0
AllocationManager0x42583067658071247ec8CE0A516A58f682002d070x87cf...4f31Proxy: TUP@4.9.0
PermissionController0x44632dfBdCb6D3E21EF613B0ca8A6A0c618F5a370xEBDa...B720Proxy: TUP@4.9.0
KeyRegistrar0xA4dB30D08d8bbcA00D40600bee9F029984dB162a0x1AFc...68e6Proxy: TUP@4.9.0
Strategies

Anyone can deploy and whitelist strategies for standard ERC20s by using the StrategyFactory deployed to the address below (see docs). Strategies deployed from the StrategyFactory are deployed using the beacon proxy pattern:

NameProxyImplementationNotes
StrategyFactory0x066cF95c1bf0927124DFB8B02B401bc23A79730D0x3f98...c5AcProxy: TUP@4.9.0
StrategyBase0x427e627Bc7E83cac0f84337d3Ad94230C32697D30x8f31...5cEf- Beacon: BeaconProxy
- Strategies: UpgradeableBeacon
StETH Strategy0x8b29d91e67b013e855EaFe0ad704aC4Ab086a5740x8f31...5cEfStrategy Factory deployed
WETH Strategy0x424246eF71b01ee33aA33aC590fd9a0855F5eFbc0x8f31...5cEfStrategy Factory deployed
Strategies - Special

The following strategies differ significantly from the other strategies deployed/used above:

NameProxyImplementationNotes
EigenStrategy (EIGEN)0x8E93249a6C37a32024756aaBd813E6139b17D1d50xE8E4...7afCProxy: TUP@4.9.0
Beacon Chain ETH0xbeaC0eeEeeeeEEeEeEEEEeeEEeEeeeEeeEEBEaC0-- Used for Beacon Chain ETH shares
- Not a real contract!
EigenPods

NOTE: Due to the permissioned validator set on Sepolia, all EigenPod functionality is PAUSED.

NameProxyImplementationNotes
EigenPod (beacon)0x0e19E56E41D42137d00dD4f51EC2F613E50cAcf40xb1B6...B533- Beacon: BeaconProxy
- Pods: UpgradeableBeacon
EIGEN/bEIGEN
NameProxyImplementationNotes
Eigen0x0011FA2c512063C495f77296Af8d195F33A8Dd380x7ec6...BD6FProxy: TUP@4.9.0
Backing Eigen0xc5B857A92245f64e9D90cCc5b096Db82eB77eB5c0x1298...3173Proxy: TUP@4.9.0
AVS

The following contracts are used by AVSs.

NameProxyImplementationNotes
ReleaseManager0x59c8D715DCa616e032B744a753C017c9f3E16bf40x67cE...2ac6Proxy: TUP@4.9.0
TaskMailbox0xB99CC53e8db7018f557606C2a5B066527bF96b260x49A8...5AdBProxy: TUP@4.9.0
Multichain - Source

The multichain protocol expects AVSs to register on the source chain. AVS's stakes are then transported to supported destination chains. For the sepolia network, the destination chains are sepolia and base-sepolia.

NameProxyImplementationNotes
CrossChainRegistry0x287381B1570d9048c4B4C7EC94d21dDb8Aa1352a0x4a93...3084Proxy: TUP@4.9.0
Multichain - Destination
NameProxyImplementationNotes
OperatorTableUpdater0xB02A15c6Bd0882b35e9936A9579f35FB26E114760x0F26...0F5CProxy: TUP@4.9.0
ECDSACertificateVerifier0xb3Cd1A457dEa9A9A6F6406c6419B1c326670A96F0xFc86...7B26Proxy: TUP@4.9.0
BN254CertificateVerifier0xff58A373c18268F483C1F5cA03Cf885c0C43373a0x7a2b...8f5dProxy: TUP@4.9.0
Multisigs
NameProxyImplementationNotes
PauserRegistry-0x63AA...20f3
OZ: TimelockController-0x1BEF...1b5B
OZ: Proxy Admin-0x56E8...6Fa1
Pauser Multisig0x0B415f75980D863872C3eb8caa76E6eC8Bc815360x4167...461aProxy: Gnosis@1.3.0
Community Multisig0x6f8459810197cc9fE123BBeB918451757a4fBAc60x4167...461aProxy: Gnosis@1.3.0
Executor Multisig0x4FDA8998EC3b7d4b4A612d45FeB8fB36734470f20x4167...461aProxy: Gnosis@1.3.0
Operations Multisig0xb094Ba769b4976Dc37fC689A76675f31bc4923b00x4167...461aProxy: Gnosis@1.3.0
Testnet Hoodi

You can view the deployed contract addresses below, or check out the code itself on the testnet-hoodi branch.

Core
NameProxyImplementationNotes
DelegationManager0x867837a9722C512e0862d8c2E15b8bE220E8b87d0x6FE5...1407Proxy: TUP@4.9.0
StrategyManager0xeE45e76ddbEDdA2918b8C7E3035cd37Eab3b5D410x1B76...0f62Proxy: TUP@4.9.0
EigenPodManager0xcd1442415Fc5C29Aa848A49d2e232720BE07976c0x0F26...0F5CProxy: TUP@4.9.0
AVSDirectory0xD58f6844f79eB1fbd9f7091d05f7cb30d33639260xE368...13EbProxy: TUP@4.9.0
RewardsCoordinator0x29e8572678e0c272350aa0b4B8f304E47EBcd5e70x35a8...0525Proxy: TUP@4.9.0
AllocationManager0x95a7431400F362F3647a69535C5666cA0133CAA00xe1b7...fFB9Proxy: TUP@4.9.0
PermissionController0xdcCF401fD121d8C542E96BC1d0078884422aFAD20x151e...75D4Proxy: TUP@4.9.0
Strategies

Anyone can deploy and whitelist strategies for standard ERC20s by using the StrategyFactory deployed to the address below (see docs). Strategies deployed from the StrategyFactory are deployed using the beacon proxy pattern:

NameProxyImplementationNotes
StrategyFactory0xfB7d94501E4d4ACC264833Ef4ede70a11517422B0x0d82...A3f3Proxy: TUP@4.9.0
StrategyBase0x6d28cEC1659BC3a9BC814c3EFc1412878B4065790xa621...063A- Beacon: BeaconProxy
- Strategies: UpgradeableBeacon
StETH Strategy0xf8a1a66130d614c7360e868576d5e59203475fe00xa621...063AStrategy Factory deployed
WETH Strategy0x24579aD4fe83aC53546E5c2D3dF5F85D6383420d0xa621...063AStrategy Factory deployed
Strategies - Special

The following strategies differ significantly from the other strategies deployed/used above:

NameProxyImplementationNotes
EigenStrategy (EIGEN)0xB27b10291DBFE6576d17afF3e251c954Ae14f1D30xd318...caE8Proxy: TUP@4.9.0
Beacon Chain ETH0xbeaC0eeEeeeeEEeEeEEEEeeEEeEeeeEeeEEBEaC0-- Used for Beacon Chain ETH shares
- Not a real contract!
EigenPods
NameProxyImplementationNotes
EigenPod (beacon)0x5e1577f8efB21b229cD5Eb4C5Aa3d6C4b228f6500x49A8...5AdB- Beacon: BeaconProxy
- Pods: UpgradeableBeacon
EIGEN/bEIGEN
NameProxyImplementationNotes
Eigen0x8ae2520954db7D80D66835cB71E692835bbA45bf0x68F3...2FE9Proxy: TUP@4.9.0
Backing Eigen0x6e60888132Cc7e637488379B4B40c42b3751f63a0x43e4...1C4Proxy: TUP@4.9.0
Multisigs
NameProxyImplementationNotes
PauserRegistry-0x64D7...c13D
OZ: TimelockController-0xE332...2d15
OZ: Proxy Admin-0xE7f4...2257
Testnet Base Sepolia

Note: Testnet Base Sepolia only supports verification of tasks from stake that lives on Sepolia. Standard core protocol functionality (restaking, slashing) does not exist on Base Sepolia.

Multichain - Destination
NameProxyImplementationNotes
OperatorTableUpdater0xB02A15c6Bd0882b35e9936A9579f35FB26E114760x6514...2D6FProxy: TUP@4.9.0
ECDSACertificateVerifier0xb3Cd1A457dEa9A9A6F6406c6419B1c326670A96F0xEE41...ca1AProxy: TUP@4.9.0
BN254CertificateVerifier0xff58A373c18268F483C1F5cA03Cf885c0C43373a0x59B1...f525Proxy: TUP@4.9.0
AVS

The following contracts are used by AVSs.

NameProxyImplementationNotes
TaskMailbox0xB99CC53e8db7018f557606C2a5B066527bF96b260x46CF...16dbProxy: TUP@4.9.0
Multisigs
NameProxyImplementationNotes
PauserRegistry-0x6ffE...672B
OZ: Proxy Admin-0xbe2F...0b5
Pauser Multisig0x2DD9BDDf299C846f61C0105905f9a60ee99242d6-
Operations Multisig0x4ACA7e09eF90612941A9185A6690Dbe9e39aae8f-
Multichain Deployer Multisig0xA591635DE4C254BD3fa9C9Db9000eA6488344C28-

Branching

Branches we use:

  • main: The canonical, most up-to-date branch, containing the work-in-progress code for upcoming releases
  • Vx.y.z: Release branch with version x.y.z that matches a release of EigenLayer, release branch is always cut from main via cherry-picking
  • release-dev/xxx: A development branch for a large feature to be released, the branch should eventually be deleted after merge to main

Building Apps & Services on EigenLayer

Developer & User Basics

Our documentation is a great place to start to understand EigenLayer and the Eigen ecosystem. If you are an audio/visual learner, check out the "You Could've Invented EigenLayer" video.

To understand more about how our ecosystem and its participants work, checkout the guides below. These are split out by who you are: AVS developers, restakers and Operators. All have different roles and interactioons with EigenLayer:

Contract Docs & Deep Dive

The most up-to-date and technical documentation on our core contracts can be found in /docs. If you're a shadowy super coder, this is a great place to get an overview of the contracts before diving into the code.

To learn more about interfacing with the EigenLayer core contracts onchain, see our middleware repo.

To get an idea of how users interact with these contracts, check out our integration tests: /src/test/integration.

Contribute to the Core

See CONTRIBUTING.

Contributions that do not follow our fork base PR practices will be either rejected or immediately deleted based on your role, preventing branch pollution, keeping our repository clean, make it more readable and searchable.