add effectiveGasPrice field to eth_getTransactionReceipt, eth_getBlockReceipts

[dubuqingfeng]

Some projects would like to have effectiveGasPrice in eth_getTransactionReceipt.

So add effectiveGasPrice field to eth_getTransactionReceipt, eth_getBlockReceipts.

ethereum/execution-specs#206

the effectiveGasPrice field:

The actual value per gas deducted from the senders account. Before EIP-1559, this is equal to the transaction's gas price. After, it is equal to baseFeePerGas + min(maxFeePerGas - baseFeePerGas, maxPriorityFeePerGas). Legacy transactions and EIP-2930 transactions are coerced into the EIP-1559 format by setting both maxFeePerGas and maxPriorityFeePerGas as the transaction's gas price.

Refence:

https://notes.ethereum.org/@timbeiko/london-json-rpc
ethereum/execution-specs#206

[AskAlexSharov]

Do you think need create hexutil.Uint256() method?

[dubuqingfeng]

The main reason for using hexutil.Uint64 is because I think EffectiveGasPrice type might be uint64,
but I see the GasPrice uses uint256.
Is there any specific reason for using uint256?
And how to do the "overflow" check here?
I think it would be nice to have hexutil.Uint256().

Before:

baseFee, _ := uint256.FromBig(block.BaseFee())
gasPrice := baseFee.Add(baseFee, txn.GetEffectiveGasTip(baseFee))
fields["effectiveGasPrice"] = hexutil.Uint64(gasPrice.Uint64())

After:

baseFee, _ := uint256.FromBig(block.BaseFee())
gasPrice := baseFee.Add(baseFee, txn.GetEffectiveGasTip(baseFee))
fields["effectiveGasPrice"] = hexutil.Uint256(gasPrice)

[AskAlexSharov]

Is there any specific reason for using uint256? - we just using uint256 everywhere where go-ethereum using big.Int (because it's more compatible with ETH spec/paper). But why GasPrice is big.Int (answer is as usually "security"): 1ETH it's 2^60 Wei - which is already almost MaxUint64=2^64. It means using Uint64 for any operations with Wei is bad idea - in general - but in this case it's fine.

How to handle overflow - just return error on overflow.