fix: use LST_STRATEGY_ADDRESS env var instead of hardcoded Holesky address #23
+36
−31
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
IncredibleSquaringDeployer.s.solto readLST_STRATEGY_ADDRESSfrom environment variableRegisterOperator.s.solto readLST_STRATEGY_ADDRESSfrom environment variableSetupMiddleware.s.solto readLST_STRATEGY_ADDRESSfrom environment variableProblem
The scripts had hardcoded Holesky stETH strategy address (
0x7D704507b76571a51d9caE8AdDAbBFd0ba0e63d3) which prevented running on other networks like Sepolia.Solution
Now reads
LST_STRATEGY_ADDRESSfrom environment variable, allowing deployment to any network.Sepolia Deployment (Live)
0x111fa1fdbe49a2ffe1d45674d80313910b59c1ca0xf5345a7f9fa4f625bea43908a1f34bacf29405c50xad31af1ef6181a86ad1ea5abbb25f5d2c191a9e90x15ece179352bd3d3cd7a9f5a52673809c550eb540x0a535bfd9eb4509caffb4d8d06c9f95cbc62a8a7Test plan