aac: update epoch list configuration from epoch20 #6611
+68
−53
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.
Description
This PR is mainly a wrap-up of what we discussed during our last internal sync. It introduce a very small change concerning the epoch list creation, taking into account epoch 2.X.
Here a sum-up of the points we discussed:
contract_deploy_consensus_test!andcontract_call_consensus_test!macros should be sufficient.If this reasoning is correct, considering the small change introduced in this PR would we prefer to integrate it directly into #6608 instead?
Otherwise, I’m happy to adjust and implement any missing pieces based on your feedback.
Applicable issues
Additional info (benefits, drawbacks, caveats)
Checklist
docs/rpc/openapi.yamlandrpc-endpoints.mdfor v2 endpoints,event-dispatcher.mdfor new events)clarity-benchmarkingrepo