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
We need to add documentation on how Charon handles the fee-recipient-address for block proposals as it is not trivial. And it can be confusing for operators as they can get confused whether to set fee-recipient-address on validator client or not.
🛠️ Proposed solution
Add docs describing how charon handles fee-recipient-address. The documentation can include:
🎯 Problem to be solved
We need to add documentation on how Charon handles the
fee-recipient-address
for block proposals as it is not trivial. And it can be confusing for operators as they can get confused whether to setfee-recipient-address
on validator client or not.🛠️ Proposed solution
Add docs describing how charon handles
fee-recipient-address
. The documentation can include:cluster-lock.json
which is generated at the end of DKG ceremony: https://github.com/ObolNetwork/charon/blob/db040d559dae37b44f5c24ea6534ce4946cb6482/app/app.go#L911-L953prepareBeaconProposer
beacon API: https://ethereum.github.io/beacon-APIs/#/Validator/prepareBeaconProposer🧪 Tests
The text was updated successfully, but these errors were encountered: