You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the feature
Chains are inconsistent in how they expose the pending base fee via their RPCs. See #821.
To handle this, we should implement base fee oracles (similar to our priority fee oracles) that use different RPC methods based on the chain. This oracle can be chosen via ChainSpec.
Known implementations needed:
FeeHistory (default) - use eth_feeHistory and Alloy's FeeHistory::next_block_base_fee
Constant - Provide a constant base fee (use for Flow)
BaseFee - use eth_baseFee (use for Avalanche)
The text was updated successfully, but these errors were encountered:
Describe the feature
Chains are inconsistent in how they expose the pending base fee via their RPCs. See #821.
To handle this, we should implement base fee oracles (similar to our priority fee oracles) that use different RPC methods based on the chain. This oracle can be chosen via
ChainSpec
.Known implementations needed:
eth_feeHistory
and Alloy'sFeeHistory::next_block_base_fee
eth_baseFee
(use for Avalanche)The text was updated successfully, but these errors were encountered: