Replies: 2 comments
-
|
Maybe this is not the right place to discuss this, I craeted another issue in filecoin-project/specs: filecoin-project/specs#1257 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We know that base fee change is determined by the average block gas limit of the previous epoch. The next base fee can be calculated like this:
Note that
block_gas_limitis not the average value of every block's gas limit, because every message counts only once in one epoch, which means, the higher message repetition rate is, the lower finalblock_gas_limitwill be. We can simply describe the relationship as this:I collected block gas limit & gas data from
2021.05.14 00:00:00Zto2021.05.14 01:00:00Z:It's a typical period because base fee changed a lot in this period:
We can find that
block_gas_limit_undedupedvalues across different epochs are almost the same (very close to the max block gas limit: 10_000_000_000), which means, there are always enough messages for miners to package, and miners always package as many messages as they can.messageRepetitionRateturns to be the decisive factor of finalblock_gas_limitvalue.Here is my problem: how can
messageRepetitionRatemeasure network congestion, as the doc says:Beta Was this translation helpful? Give feedback.
All reactions