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
charon create cluster command generates a cluster-lock.json file which has incorrect builder registrations. It consists of withdrawal addresses instead of fee-recipient addresses which causes lock verification to fail.
Has this worked before in a previous version?
No
🔬 Minimal Reproduction
Run create cluster command with different fee-recipient and withdrawal address and check fee_recipient field in builder_registration data for the given withdrawal address.
🔥 Error
🌍 Your Environment
What version of Charon are you running? (Which release)
v0.17.1
The text was updated successfully, but these errors were encountered:
This PR fixes a bug in the `create cluster` command that was generating incorrect builder registrations in cluster-lock.json. The issue stemmed from the usage of withdrawal addresses instead of fee recipient addresses, which resulted in signature verification failures when the command was used for the 'charon run' operation.
Here's the error log caused by this bug:
![image](https://github.com/ObolNetwork/charon/assets/37813203/42f3fa00-cff8-4107-b8c1-55d91f485a42)
category: bug
ticket: #2674
This PR fixes a bug in the `create cluster` command that was generating incorrect builder registrations in cluster-lock.json. The issue stemmed from the usage of withdrawal addresses instead of fee recipient addresses, which resulted in signature verification failures when the command was used for the 'charon run' operation.
Here's the error log caused by this bug:
![image](https://github.com/ObolNetwork/charon/assets/37813203/42f3fa00-cff8-4107-b8c1-55d91f485a42)
category: bug
ticket: #2674
🐞 Bug Report
Description
charon create cluster
command generates a cluster-lock.json file which has incorrect builder registrations. It consists of withdrawal addresses instead of fee-recipient addresses which causes lock verification to fail.Has this worked before in a previous version?
No
🔬 Minimal Reproduction
Run create cluster command with different fee-recipient and withdrawal address and check
fee_recipient
field inbuilder_registration
data for the given withdrawal address.🔥 Error
🌍 Your Environment
What version of Charon are you running? (Which release)
The text was updated successfully, but these errors were encountered: