🎯 Problem to be solved

We want to sign deposits for new validators, but add validators is a bit high friction as it requires restarting the prod validators. Some orgs maintain a strict separation of concern between the people that manage the private key generation and the people that run the nodes.

🛠️ Proposed solution

Like we have charon exit sign and charon exit fetch. Lets make charon deposit sign and charon deposit fetch.

You should be able to specify --public-keys from the cluster-lock as a comma separated array of pubkeys to sign deposits for.

You should be able to specify --compounding, which makes the withdrawal address 0x02, otherwise 0x01

You must specify one withdrawal address or as many withdrawal addresses as your --public-keys array.

The default amount is 1 + 32 eth, but you can modify it with --deposit-amounts.

🧪 Tests

• Tested by new automated unit/integration/smoke tests
• Manually tested on core team/canary/test clusters
• Manually tested on local compose simnet

👐 Additional acceptance criteria

The Obol API needs to support this behavior

❌ Out of Scope

Modifying fee-recipients of these validators. For now an editable splitter should be used.