From 3f50a7d9cd661a2450a07a3eddb8341105a6e8c4 Mon Sep 17 00:00:00 2001 From: Dennis Date: Fri, 5 Apr 2024 18:39:05 +0200 Subject: [PATCH] docs(operate): info on using el keys using halo (#781) Adds section outlining support for EL CLI generated keys task: none --- docs/site/docs/operate/testnet/client.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/site/docs/operate/testnet/client.md b/docs/site/docs/operate/testnet/client.md index 14ab0947a..286243eb8 100644 --- a/docs/site/docs/operate/testnet/client.md +++ b/docs/site/docs/operate/testnet/client.md @@ -26,6 +26,14 @@ After adding the `halo` binary to your system, you can initialize and run the cl halo init --network testnet ``` +:::tip Using EigenLayer-Generated Private Keys + +If you are using the private keys generated by the EigenLayer CLI, you can have `halo` use them by saving them to `/config/*.ecdsa.key.json` and deleting the `init` generated key file found there (`config/priv_validator_key.json`). The `halo` client will automatically pick up these keys and use them for signing transactions. + +You will need to pass in your password for that key when you run the client. You can do this by setting the `--eigenlayer-key-password` flag when executing the client's `run` command below. + +::: + This command initializes the setup, creating several configuration files required for running the node. You can then run the client with the following command: ```bash