test: Add gas usage analysis for updateState function #17
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Created comprehensive gas tests to measure updateState gas consumption - Tested with varying operator counts (10-2000) and history lengths (10-1000) - Added component breakdown analysis to identify gas bottlenecks - Generated detailed report with findings and recommendations Key findings: - Function exceeds block gas limit with >50 operators - Gas usage grows linearly with operator count and history length - Stake and bitmap history updates consume ~93% of gas Recommendations include implementing incremental updates and batch processing. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
This PR addresses issue #2 by adding comprehensive gas usage tests for the
updateStatefunction inRegistryCoordinatorMimic. The tests reveal that the function exceeds Ethereum block gas limits with realistic operator counts.Changes
RegistryCoordinatorMimicGas.t.solwith comprehensive gas testing suiteKey Findings
🔴 Critical Issue Identified
The
updateStatefunction exceeds block gas limits with just 50+ operators:Gas Breakdown (100 operators, 50 history entries)
Recommendations
Test Plan
To reproduce tests:
forge test --match-path test/RegistryCoordinatorMimicGas.t.sol -vvImpact
This analysis confirms that the current implementation is not suitable for production with realistic AVS operator sets. The findings should inform the design of an incremental update mechanism as suggested in the issue description.
Closes #2
🤖 Generated with Claude Code