Skip to content

Gas price in receipt changed from 1.5 > 2.0 #83

@poplexity

Description

@poplexity

Gas price on 1.5 and earlier was the gas price charged on-chain which may be less than the gas price that was in the signed transaction.

2.0 and newer this is the gas price that was signed for in the transaction, which resolves issues that some clients have had (i.e. go-ethereum) where they want to read the transaction and reconstruct their own hash which would not match on 1.5, now with 2.0 as the RPC transaction response includes the price that was signed in the original transaction the hashes match.

We should consider putting the gas price charged on-chain as the effectiveGasPrice, as a means to provide more accurate response data. Currently gasPrice and effectiveGasPrice are both the same value in the RPC response.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions