-
Notifications
You must be signed in to change notification settings - Fork 14
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
Coinbase address does not receive tips after transaction execution #34
Comments
Thanks for submitting the issue! Looks like there is a bug calculating the initial gas limit: tracediff generated from eip1559-splitted.json |
@cassc Thanks for your time and support. I'm afraid we're not discussing the same issue; here are the details of my situation: I'm trying to replay an ETH transfer transaction ( In a blockchain browser (e.g., Etherscan and OKO), it can be noticed that the transaction caused a change in the balances of the three EOAs (sender, receiver and miner). However, replaying the transaction on CuEVM only updates the sender's and receiver's balances, while the coinbase address's balance remains unchanged. The input JSON file: The JSON file output by CuEVM: |
@Shuwei-Song can you please try the evmcall branch and see if you still got the issue?
|
@cassc Many thanks for your advice. After switching to the evmcall branch, I get the same output as yours, in which the miner receives tips as expected. But two new problems arise:
Thank you very much for your time and assistance. |
Hi @Shuwei-Song ,
|
Hello,
After executing a transaction, the coinbase address does not receive any tips, meaning its balance does not change as expected.
Steps to Reproduce:
Run any test case, e.g., eip1559.json
Observe the balance of the coinbase address after the transaction execution.
Expected Result:
The coinbase address should receive the appropriate amount of tips, reflecting an increase in its balance.
Actual Result:
The coinbase address's balance remains unchanged.
Please look into this issue. Thank you!
The text was updated successfully, but these errors were encountered: