Move holocene next block base fee handling into opChainspec

### Describe the feature

after #16927 we can move 

https://github.com/paradigmxyz/reth/blob/ad8fec466156245afb1fc6cbd1afed6dcbfc8b7b/crates/optimism/consensus/src/validation/mod.rs#L189-L206

into `next_block_base_fee` of OpChainSpec so that post holocene decoding is respected

## TODO
* Call this fn from opchainspec's fn

### Additional context

_No response_

	/// Read from parent to determine the base fee for the next block
	///
	/// See also [Base fee computation](https://github.com/ethereum-optimism/specs/blob/main/specs/protocol/holocene/exec-engine.md#base-fee-computation)
	pub fn next_block_base_fee(
	chain_spec: impl EthChainSpec + OpHardforks,
	parent: impl BlockHeader,
	timestamp: u64,
	) -> Result<u64, EIP1559ParamError> {
	// If we are in the Holocene, we need to use the base fee params
	// from the parent block's extra data.
	// Else, use the base fee params (default values) from chainspec
	if chain_spec.is_holocene_active_at_timestamp(parent.timestamp()) {
	Ok(decode_holocene_base_fee(chain_spec, parent, timestamp)?)
	} else {
	Ok(chain_spec.next_block_base_fee(&parent, timestamp).unwrap_or_default())
	}
	}

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Move holocene next block base fee handling into opChainspec #17090

Describe the feature

TODO

Additional context

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Move holocene next block base fee handling into opChainspec #17090

Description

Describe the feature

TODO

Additional context

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions