Skip to content

all: rename blockchain option #31925

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rjl493456442
Copy link
Member

@rjl493456442 rjl493456442 commented May 29, 2025

In this pull request, the original CacheConfig has been renamed to BlockchainOptions.

Over time, more fields have been added to CacheConfig to support blockchain configuration.
Such as ChainHistoryMode, which clearly extends beyond just caching concerns.

Additionally, adding new parameters to the blockchain constructor has become increasingly
complicated, since it’s initialized across multiple places in the codebase. A natural solution
is to consolidate these arguments into a dedicated configuration struct.

As a result, the existing CacheConfig has been redefined as BlockchainOptions. Some parameters,
such as (a) VmConfig, (b) TxLookupLimit, and (c) ChainOverrides have been moved into
BlockchainOptions to simplify the blockchain configuration. Besides, a few fields in BlockchainOptions
is renamed, specifically:

  • TrieCleanNoPrefetch -> NoPrefetch
  • TrieDirtyDisabled -> ArchiveMode

Notably, this change won't affect the command line flags or the toml configuration file.
It's just an internal refactoring and fully backward-compatible.

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.

1 participant