Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add config for eth_getLogs max block depth #5652

Merged
merged 1 commit into from
May 4, 2023

Conversation

asdacap
Copy link
Contributor

@asdacap asdacap commented May 4, 2023

  • Increase max block depth from 1000 to 10000 and make it configurable.
  • Does not matter if bloom is on.
  • Teku's default max request is 10000.

Types of changes

What types of changes does your code introduce?

  • Bugfix (a non-breaking change that fixes an issue)
  • New feature (a non-breaking change that adds functionality)

Testing

Requires testing

  • Yes
  • No

If yes, did you write tests?

  • Yes
  • No

Notes on testing

Optional. Remove if not applicable.

Remarks

Optional. Remove if not applicable.

@asdacap asdacap changed the title Add config for max block depth Add config for eth_getLogs max block depth May 4, 2023
@LukaszRozmej LukaszRozmej merged commit b9afd3d into master May 4, 2023
@LukaszRozmej LukaszRozmej deleted the feature/configurable-max-block-depth branch May 4, 2023 09:26
@@ -21,4 +21,7 @@ public interface IReceiptConfig : IConfig

[ConfigItem(Description = "Number of recent blocks to maintain transaction index. 0 to never remove tx index. -1 to never index.", DefaultValue = "2350000")]
long? TxLookupLimit { get; set; }

[ConfigItem(Description = "Max num of block per eth_getLogs request.", DefaultValue = "10000")]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As it doesn't matter with Bloom Index (which is default), maybe we should hide it from docs?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants