EigenDA Churn Approver Down

0xbmac commented 8 months ago

Issue Summary

After upgrading to 0.3.0, and re-running opt-in, the script fails to request churn approval, receiving 404 error from the server.

Environment

EigenDA version: 0.3.0
Operating System: Ubuntu 22.04
Node configuration (if applicable): Followed steps in upgrade, everything else was configured properly, as I was participating in EigenDA AVS
Any specific settings or modifications: NODE_CHURNER_URL=churner-goerli.eigenda.xyz:443 should this be changed? (not mentioned in upgrade

Steps to Reproduce

Configure node
run ./run.sh opt-in

Expected Behavior

using socket: REDACTED:32005;32004
2024/01/21 22:33:54 maxprocs: Leaving GOMAXPROCS=2: CPU quota undefined
2024/01/21 22:33:54 Info: plugin configs and flags parsed
2024/01/21 22:33:55 Info: Bls key read and decrypted from /app/operator_keys/bls_key.json
2024/01/21 22:33:57 Info: ECDSA key read and decrypted from /app/operator_keys/ecdsa_key.json
2024/01/21 22:33:57 Info: ethclient created for url: https://REDACTED
2024/01/21 22:33:59 Info: Operator with Operator Address: REDACTED is opting in to EigenDA
DEBUG[01-21|22:33:59.540|github.com/Layr-Labs/eigenda/node/operator.go:35] Registered quorum ids                    registeredQuorumIds=[] caller=operator.go:35
INFO [01-21|22:33:59.803|github.com/Layr-Labs/eigenda/node/operator.go:46] Quorums to register for                  quorums=[0] caller=operator.go:46
INFO [01-21|22:34:00.331|github.com/Layr-Labs/eigenda/node/operator.go:73] Should call churner                      shouldCallChurner=true caller=operator.go:73
INFO [01-21|22:34:00.331|github.com/Layr-Labs/eigenda/node/operator.go:115] churner url                              url=churner-goerli.eigenda.xyz:443 caller=operator.go:115
2024/01/21 22:35:02 Info: successfully opt-in the EigenDA, for operator ID: REDACTED, operator address: REDACTED, socket: REDACTED:32005;32004, and quorums: [0]

Actual Behavior

Churn approval request returns 404 as if it is currently down (or has migrated to a new address).

2024/02/16 18:13:43 maxprocs: Leaving GOMAXPROCS=2: CPU quota undefined
2024/02/16 18:13:43 Info: plugin configs and flags parsed
2024/02/16 18:13:44 Info: Bls key read and decrypted from /app/operator_keys/bls_key.json
2024/02/16 18:13:45 Info: ECDSA key read and decrypted from /app/operator_keys/ecdsa_key.json
2024/02/16 18:13:45 Info: ethclient created for url: https://REDACTED
DEBUG[02-16|18:13:46.957|github.com/Layr-Labs/eigenda/core/eth/tx.go:662] Addresses                                blsOperatorStateRetrieverAddr=0x357a99ccF04fC68Bd8d220263F9182506CBFEaF8 eigenDAServiceManagerAddr=0xa3b1689Ab85409B15e07d2ED50A6EA9905074Ee5 registryCoordinatorAddr=0x7661dA87296c0A245d11ADeD7f48265463bc3eC6 blsPubkeyRegistryAddr=0xb406d8e5F4BA1430D57c8231cc872C2c369E1F5F caller=tx.go:662
2024/02/16 18:13:47 Info: Operator with Operator Address: REDACTED is opting in to EigenDA
DEBUG[02-16|18:13:47.724|github.com/Layr-Labs/eigenda/node/operator.go:40] Registered quorum ids                    registeredQuorumIds=[] caller=operator.go:40
INFO [02-16|18:13:47.724|github.com/Layr-Labs/eigenda/node/operator.go:45] Quorums to register for                  quorums=[0] caller=operator.go:45
INFO [02-16|18:13:48.220|github.com/Layr-Labs/eigenda/node/operator.go:72] Should call churner                      shouldCallChurner=true caller=operator.go:72
INFO [02-16|18:13:48.220|github.com/Layr-Labs/eigenda/node/operator.go:128] churner url                              url=churner-goerli.eigenda.xyz:443 caller=operator.go:128
2024/02/16 18:13:49 Error: failed to opt-in EigenDA Node Network for operator ID: REDACTED, operator address: REDACTED, error: failed to request churn approval: rpc error: code = Unimplemented desc = unexpected HTTP status code received from server: 404 (Not Found); transport: received unexpected content-type "text/plain; charset=utf-8"

Possible Solution

Update goerli NODE_CHURNER_URL Reboot Node Churner at churner-goerli.eigenda.xyz:443

Additional Context

Many others are having the same issue, as reported in Discord.

shrimalmadhur commented 8 months ago

Hi, we are aware of this issue and working to fix the churner. will update here once it's up again. Thanks for reporting.

shrimalmadhur commented 8 months ago

@0xbmac Hello this has been fixed. Please try again.

Layr-Labs / eigenda-operator-setup