Improved support for transaction fee estimation #3673
Labels
f:fee-mechanism
Feature: Fee Mechanism
stale
To be closed due to a lack of activity
t:enhancement
Type: Feature, refactoring.
t:epic
Type: Epic
With the occurrence of ckb network congestion, a question has been more prominently exposed, how should ckb now go about setting transaction fees? Currently, the ckb nodes and the corresponding sdk do not have good support for transaction fee estimation, so this issue serves as a feature proposal to summarize and track the next actions.
Need an RPC that returns the cycles consumed by a transaction execution verification, although
dry_run_transaction
existed before, but its placement in the Experiment module needs some tweakingfeat: add rpc estimate_cycles #3669
Need an RPC to measure the fee_rate needed for a new transaction based on the fee_rate of the on-chain transaction. Here we need a solution that can be provided as soon as possible in the short term and a solution that is more optimal in the long term.
In the short term, provide an RPC that returns the average or median of the transaction fee_rates over a historical interval on the chain, Users can use this value according to their needs and experience (e.g. estimate_fee_rate * 1.2 / 1.5 / 2) Improve support for cycles access #3684
In the long term we need to provide better algorithms to measure the fee_rates required for new transactions to provide better guarantees, such as how much fee_rate can be used for new transactions to ensure that they can be confirmed within a certain time.
The text was updated successfully, but these errors were encountered: