Skip to content

Conversation

@RonTuretzky
Copy link

@RonTuretzky RonTuretzky commented Dec 17, 2025

Summary

  • Fix IncredibleSquaringDeployer.s.sol to read LST_STRATEGY_ADDRESS from environment variable
  • Fix RegisterOperator.s.sol to read LST_STRATEGY_ADDRESS from environment variable
  • Fix SetupMiddleware.s.sol to read LST_STRATEGY_ADDRESS from environment variable
  • Add Sepolia deployment addresses

Problem

The scripts had hardcoded Holesky stETH strategy address (0x7D704507b76571a51d9caE8AdDAbBFd0ba0e63d3) which prevented running on other networks like Sepolia.

Solution

Now reads LST_STRATEGY_ADDRESS from environment variable, allowing deployment to any network.

Sepolia Deployment (Live)

Contract Address
ServiceManager 0x111fa1fdbe49a2ffe1d45674d80313910b59c1ca
TaskManager 0xf5345a7f9fa4f625bea43908a1f34bacf29405c5
RegistryCoordinator 0xad31af1ef6181a86ad1ea5abbb25f5d2c191a9e9
StakeRegistry 0x15ece179352bd3d3cd7a9f5a52673809c550eb54
InstantSlasher 0x0a535bfd9eb4509caffb4d8d06c9f95cbc62a8a7

Test plan

  • Verify deployment works on local anvil (no fork)
  • Verify deployment works on Sepolia fork (LOCAL mode)
  • Verify deployment works on Sepolia testnet (TESTNET mode)
  • Verify operator registration works with correct strategy address

…dress

The scripts had hardcoded Holesky stETH strategy address
(0x7D704507b76571a51d9caE8AdDAbBFd0ba0e63d3) which prevented
running on other networks like Sepolia.

Now reads LST_STRATEGY_ADDRESS from environment variable.
Changed hardcoded Holesky strategy address to use env variable
for multi-network support (Sepolia, Holesky, Mainnet).
RonTuretzky added a commit to BreadchainCoop/eigenlayer-bls-local that referenced this pull request Dec 17, 2025
Uses RonTuretzky/sepolia-local-mode branch from bls-middleware
which has the fix for hardcoded Holesky strategy addresses.

Depends on: BreadchainCoop/bls-middleware#23
Deployed IncredibleSquaring AVS contracts to Sepolia testnet:
- ServiceManager: 0x111fa1fdbe49a2ffe1d45674d80313910b59c1ca
- TaskManager: 0xf5345a7f9fa4f625bea43908a1f34bacf29405c5
- RegistryCoordinator: 0xad31af1ef6181a86ad1ea5abbb25f5d2c191a9e9
- StakeRegistry: 0x15ece179352bd3d3cd7a9f5a52673809c550eb54
- InstantSlasher: 0x0a535bfd9eb4509caffb4d8d06c9f95cbc62a8a7
Deployment addresses are documented in the PR description instead.
Added require statements to fail with clear error message if
LST_STRATEGY_ADDRESS environment variable is not set or invalid.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants