Skip to content
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

[EIP-1559] Transaction pool pricing rules must handle both frontier and EIP-1559 transactions. #919

Merged
merged 5 commits into from
May 14, 2020

Conversation

AbdelStark
Copy link
Contributor

PR description

The transaction gas price is computed when adding a transaction into the local pool using eth_sendRawTransaction JSON RPC endpoint. Transaction price must be computed properly depending on the type of the transaction.
For instance shouldReplace method of PendingTransactions must be updated to deal with EIP-1559 transactions.

  • Updated PendingTransactions to add access to the chain header in order to retrieve the last base fee value.
  • Updated TransactionReplacementByPriceRule to compute the transaction price depending on the type of the transaction (frontier or eip-1559).
  • Added unit tests to cover all possible replacement scenarios.

Issues

fixes #905

Signed-off-by: Abdelhamid Bakhta abdelhamid.bakhta@consensys.net

…the local pool using eth_sendRawTransaction JSON RPC endpoint. Transaction price must be computed properly depending on the type of the transaction.

For instance `shouldReplace` method of PendingTransactions must be updated to deal with EIP-1559 transactions.

- Updated `PendingTransactions` to add access to the chain header in order to retrieve the last base fee value.
- Updated `TransactionReplacementByPriceRule` to compute the transaction price depending on the type of the transaction (frontier or eip-1559).
- Added unit tests to cover all possible replacement scenarios.

Signed-off-by: Abdelhamid Bakhta <abdelhamid.bakhta@consensys.net>
@AbdelStark AbdelStark self-assigned this May 13, 2020
Signed-off-by: Abdelhamid Bakhta <abdelhamid.bakhta@consensys.net>
Signed-off-by: Abdelhamid Bakhta <abdelhamid.bakhta@consensys.net>
Signed-off-by: Abdelhamid Bakhta <abdelhamid.bakhta@consensys.net>
Signed-off-by: Abdelhamid Bakhta <abdelhamid.bakhta@consensys.net>
Copy link
Contributor

@matkt matkt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@AbdelStark AbdelStark merged commit b784344 into hyperledger:master May 14, 2020
shemnon pushed a commit to shemnon/besu that referenced this pull request May 23, 2020
…nd EIP-1559 transactions. (hyperledger#919)

* The transaction gas price is computed when adding a transaction into the local pool using eth_sendRawTransaction JSON RPC endpoint. Transaction price must be computed properly depending on the type of the transaction.
For instance `shouldReplace` method of PendingTransactions must be updated to deal with EIP-1559 transactions.

- Updated `PendingTransactions` to add access to the chain header in order to retrieve the last base fee value.
- Updated `TransactionReplacementByPriceRule` to compute the transaction price depending on the type of the transaction (frontier or eip-1559).
- Added unit tests to cover all possible replacement scenarios.

Signed-off-by: Abdelhamid Bakhta <abdelhamid.bakhta@consensys.net>
Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>
macfarla pushed a commit to macfarla/besu that referenced this pull request Jun 3, 2020
…nd EIP-1559 transactions. (hyperledger#919)

* The transaction gas price is computed when adding a transaction into the local pool using eth_sendRawTransaction JSON RPC endpoint. Transaction price must be computed properly depending on the type of the transaction.
For instance `shouldReplace` method of PendingTransactions must be updated to deal with EIP-1559 transactions.

- Updated `PendingTransactions` to add access to the chain header in order to retrieve the last base fee value.
- Updated `TransactionReplacementByPriceRule` to compute the transaction price depending on the type of the transaction (frontier or eip-1559).
- Added unit tests to cover all possible replacement scenarios.

Signed-off-by: Abdelhamid Bakhta <abdelhamid.bakhta@consensys.net>
Signed-off-by: Sally MacFarlane <sally.macfarlane@consensys.net>
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.

[EIP-1559] Transaction pool pricing rules must handle both frontier and EIP-1559 transactions
2 participants