Error: exceed maximum block range: 50000

[jamesnguyentech]

Issue Summary

When trying to run the aggregator on the testnet (holesky), I encountered the following error:

Fatal error opening websocket subscription for new pubkey registrations {"err":"exceed maximum block range: 50000","service":"OperatorPubkeysServiceInMemory"}
Stacktrace
    github.com/Layr-Labs/eigensdk-go/logging.(*ZapLogger).Error
        /Users/jamesnguyen/go/pkg/mod/github.com/!layr-!labs/eigensdk-go@v0.1.1-0.20240207213853-8a666597e0f1/logging/zap_logger.go:57
    github.com/Layr-Labs/eigensdk-go/services/operatorpubkeys.(*OperatorPubkeysServiceInMemory).startServiceInGoroutine.func1
        /Users/jamesnguyen/go/pkg/mod/github.com/!layr-!labs/eigensdk-go@v0.1.1-0.20240207213853-8a666597e0f1/services/operatorpubkeys/operatorpubkeys_inmemory.go:79
panic: exceed maximum block range: 50000

How can I resolve the "exceed maximum block range: 50000" error when running the example on the testnet (holesky)?

[samlaf]

This means your ethereum node only accepts log query with max 50k block ranges. I believe right now inc sq doesn’t put any bounds on the queries. There’s an update in the eigensdk to allow querying with time ranges so we’ll have to update to latest eigensdk version and for loop over 50k block ranges.

[jamesnguyentech]

If possible, could you guide me on how to update it? I will update it and create a PR, as I also want to understand more deeply and contribute to EigenLayer.

[samlaf]

@Gajesh2007 dont close issues without answering the OP’s question or at least explaining why the issue is now fixed.

[irfanshaik11]

hi we're facing a similar issue!

[maximopalopoli]

Hello, @irfanshaik11, we tried to reproduce the error by sending a very high logFilterQueryBlockRange when initializing the aggregator on testnet, but could not get the error. Could you tell the steps to reproduce the error and the error log the aggregator returns?