Tx fees need to account for blobs #11005
Assignees
Comments
just-mitch
pushed a commit
that referenced
this issue
Jan 10, 2025
fixes: #11005 fixes: #10066 Few things ended up being included here: - Tx calculation for blobs - Configuration to allow for fixed priority fee on all TXs - Fixes around user configuration to allow for fractional percentages (e.g. 8.55% increase on fees per retry) - Stripping errors from eth nodes that included massive hex strings of data - Attempting to get revert errors for all actions of l1-publisher - introduce 5s bot tx interval & fixed priority fee for our sepolia deployments --------- Co-authored-by: Santiago Palladino <santiago@aztecprotocol.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A test run on Sepolia encountered the following errors.
"replacement transaction underpriced: new tx blob gas fee cap 10000000000 <= 10000000000 queued","metaMessages":["URL: [https://json-rpc.3qfulxvuwdqzzv1b1wewwayln.blockchainnodeengine.com?key=AIzaSyB0brZDGEwqxTqEkc2fL5XCmXRKUPSyCt4](https://json-rpc.3qfulxvuwdqzzv1b1wewwayln.blockchainnodeengine.com/?key=AIzaSyB0brZDGEwqxTqEkc2fL5XCmXRKUPSyCt4)","Request body: {\"method\":\"eth_sendRawTransaction\",\"params\":"tx fee (1.06 ether) exceeds the configured cap (1.00 ether)","metaMessages":["URL: [https://json-rpc.3qfulxvuwdqzzv1b1wewwayln.blockchainnodeengine.com?key=AIzaSyB0brZDGEwqxTqEkc2fL5XCmXRKUPSyCt4](https://json-rpc.3qfulxvuwdqzzv1b1wewwayln.blockchainnodeengine.com/?key=AIzaSyB0brZDGEwqxTqEkc2fL5XCmXRKUPSyCt4)","Request body: {\"method\":\"eth_sendRawTransaction\",\"params\":These are most likely due to insufficient fee handling.
The text was updated successfully, but these errors were encountered: