-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dual transmission key protection #15969
base: develop
Are you sure you want to change the base?
Conversation
-Check primary/secondary addresses
I see you updated files related to
|
Quality Gate passedIssues Measures |
AER Report: CI Coreaer_workflow , commit , Clean Go Tidy & Generate , Detect Changes , Scheduled Run Frequency , Core Tests (go_core_tests) , Core Tests (go_core_tests_integration) , GolangCI Lint (.) , Core Tests (go_core_ccip_deployment_tests) , Core Tests (go_core_fuzz) , Core Tests (go_core_race_tests) , test-scripts , lint , SonarQube Scan 1. Key not found error: go_core_tests_integrationSource of Error:
Why: The error indicates that a required key was not found in the keystore during the job creation process. This could be due to missing or improperly configured keys in the keystore. Suggested fix: Ensure that all necessary keys are correctly added to the keystore before running the tests. Verify the keystore configuration and ensure that the keys are accessible. 2. Key not found error: go_core_testsSource of Error:
Why: Similar to the previous error, this indicates that a required key was not found in the keystore during the job creation process. This could be due to missing or improperly configured keys in the keystore. Suggested fix: Ensure that all necessary keys are correctly added to the keystore before running the tests. Verify the keystore configuration and |
This PR enhances the ETH keystore by adding tags to prevent address sharing between TXMv1 and TXMv2, avoiding nonce sync issues. This is a temporary fix until the full switch to TXMv2.