You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cluster locks with EIP1271 smart contract signatures fail normal signature checks. This means you need to run charon run --no-verify which is a reduction of the security model.
🛠️ Proposed solution
If operator_enr_signature and operator_config_hash fail validation, and we have been provided an --execution-rpc-api flag (doesn't exist yet), we fallback and try smart contract based signature check.
If the signatures fail to verify, and no JSON RPC is provided, we throw the normal verification error log, but suggest that if the cluster has smart contract wallet operators they need to provide a json rpc uri or to use --no-verify.
🧪 Tests
Tested by new automated unit/integration/smoke tests
Manually tested on core team/canary/test clusters
Manually tested on local compose simnet
The text was updated successfully, but these errors were encountered:
🎯 Problem to be solved
Cluster locks with EIP1271 smart contract signatures fail normal signature checks. This means you need to run
charon run --no-verify
which is a reduction of the security model.🛠️ Proposed solution
If operator_enr_signature and operator_config_hash fail validation, and we have been provided an
--execution-rpc-api
flag (doesn't exist yet), we fallback and try smart contract based signature check.If the signatures fail to verify, and no JSON RPC is provided, we throw the normal verification error log, but suggest that if the cluster has smart contract wallet operators they need to provide a json rpc uri or to use --no-verify.
🧪 Tests
The text was updated successfully, but these errors were encountered: