Currently, Astar network's transaction volume has increased drastically and we are having some trouble prioritizing the tx queue.
With EVM, there are many RPCs like
eth_feeHistory, and EIP-1159 to understand more or less what is the optimal gas price for the transaction to pass within a large tx queue. However, from what I understand, Substrate does not have this kind of RPC for native transaction tips, meaning that the tip value is completely up to the user's arbitrary input. And if we consider that the EVM transaction also has its own gas value with transaction priorities, how will this work with the native transaction pool?
So my questions are as the following:
- Is there a way to calculate the optimal way to calculate the ideal tip value?
- Will the EVM transaction affect the tx priority for native transactions (I assume it does)? If so, will the EIP-1159 method of calculating the gas cost affect the required tip value for native transactions?
- Would it be reasonable to directly use the EIP-1159 gas station and use the optimal gas price as the tip value for the native transaction?
Edit: I noticed that there is a function called
get_priority and storage called
NextFeeMultiplier in the
transaction-payment pallet. Could this be related to the solution?