Open omritoptix opened 3 months ago
Quoting @omritoptix from notion
Charge more gas than ‘normal’ I believe a mitigation would be to store the gas-price as an on-chain param.
In case the sequencer decides to manipulate it (e.g increase), the relevant transaction hash can be sent to the hub as an evidence. The tx query should provide I believe with the reason for failure and maybe validator can query it using vote extension.
e.g
Error: insufficient fees; got: 100uatom required: 250uatom
Given you can also get the gas units ( "gas_wanted": "200000", "gas_used": "50132”) you can deduce the price that was passed.
the endpoint: curl -X GET "http://localhost:1317/cosmos/tx/v1beta1/txs/{tx_hash}"
@srene is this one already tackled by the recent consensus params PRs?
@omritoptix is this one in V3? I think I read somewhere it will be after?
@dawnt gas-price is not yet included in the current dymint PR
not gonna happen in 3D I blv.
related research: https://www.notion.so/dymension/ADR-x-Rollapp-Consensus-Params-d60daee1f8cb42e38e43e1ef5289a220#7bc260fefb05421d9d407727cf82cea5