CLI panic when using add-admin

[ahmohamed]

Describe the bug
Eigenlayer CLI panic when using add-admin. Tried binary versions 0.13.0, 0.13.2 and 0.13.3-rc.0, with --broadcast and without and --output-type=calldata. All had the same error as below.

To Reproduce

> eigenlayer user admin add-pending-admin --admin-address=0xcAa0824477fc9c72297F84Ca1F9F5337b5E65B1A --account-address=0xcAa0824477fc9c72297F84Ca1F9F5337b5E65B1A --eth-rpc-url=https://rpc.hoodi.ethpandaops.io --network=hoodi --broadcast

Sep 29 07:56:04.121 INF Caller address not provided. Using account-address as default address (0xcAa0824477fc9c72297F84Ca1F9F5337b5E65B1A)
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xfad16b]

goroutine 1 [running]:
github.com/Layr-Labs/eigenlayer-cli/pkg/user/admin.readAndValidateAddPendingAdminConfig(0xc0003b6480, {0x171ab40, 0xc0006225b0})
        /home/runner/work/eigenlayer-cli/eigenlayer-cli/eigenlayer-cli/pkg/user/admin/add_pending.go:192 +0x66b
github.com/Layr-Labs/eigenlayer-cli/pkg/user/admin.addPendingAdmin(0xc0003b6480, 0xc00011ca20)
        /home/runner/work/eigenlayer-cli/eigenlayer-cli/eigenlayer-cli/pkg/user/admin/add_pending.go:56 +0x69
github.com/Layr-Labs/eigenlayer-cli/pkg/user/admin.AddPendingCmd.func1(0xc0003b6480?)
        /home/runner/work/eigenlayer-cli/eigenlayer-cli/eigenlayer-cli/pkg/user/admin/add_pending.go:40 +0x17
github.com/urfave/cli/v2.(*Command).Run(0xc0003f09a0, 0xc0003b6480, {0xc000118660, 0x6, 0x6})
        /home/runner/go/pkg/mod/github.com/urfave/cli/v2@v2.27.5/command.go:276 +0x7e2
github.com/urfave/cli/v2.(*Command).Run(0xc0003f1600, 0xc0003b6300, {0xc00033a460, 0x7, 0x7})
        /home/runner/go/pkg/mod/github.com/urfave/cli/v2@v2.27.5/command.go:269 +0xa65
github.com/urfave/cli/v2.(*Command).Run(0xc000040b00, 0xc0003b6240, {0xc0002c6200, 0x8, 0x8})
        /home/runner/go/pkg/mod/github.com/urfave/cli/v2@v2.27.5/command.go:269 +0xa65
github.com/urfave/cli/v2.(*Command).Run(0xc0004be000, 0xc0003b6100, {0xc00003e090, 0x9, 0x9})
        /home/runner/go/pkg/mod/github.com/urfave/cli/v2@v2.27.5/command.go:269 +0xa65
github.com/urfave/cli/v2.(*App).RunContext(0xc000146a00, {0x1712bd0, 0x1fde980}, {0xc00003e090, 0x9, 0x9})
        /home/runner/go/pkg/mod/github.com/urfave/cli/v2@v2.27.5/app.go:333 +0x5a5
github.com/urfave/cli/v2.(*App).Run(...)
        /home/runner/go/pkg/mod/github.com/urfave/cli/v2@v2.27.5/app.go:307
main.main()
        /home/runner/work/eigenlayer-cli/eigenlayer-cli/eigenlayer-cli/cmd/eigenlayer/main.go:48 +0x525

Expected behavior
Add pending admin tx broadcast.

Screenshots
N/A

OS details

Ubuntu amd64.

[bdchatham]

Hi there, it looks like you aren't providing a private key, unless I'm missing something. That is causing a nil signer config under the hood and a subsequent nil panic.

[ahmohamed]

Thanks for the response. A few comments:

• It would be great if the CLI does not panic and acutally display an error message if it cannot find the private key.
• The key is in its default path ~/.eigenlayer/operator_keys/*.json. I can call eigenlayer operator update-metadata-uri and it doesn't error out.
• The docs don't mention anything about providing the private key explicitly.
• When using --output-type=calldata --broadcast=false, why do we still need to provide the private key?

Our initial intention was to generate the calldata and sign it offline. Is this at all possible?