-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sequencer DA limit throttling #1357
Comments
the DA bandwith of bitcoin is 4MB / 10 mins. Ideally, we'd like to have a fee mechanism that increases L1 fee rates on soft confirmations as we reach the 4MB/10 mins mark. The L1 fee is an arbitrary fee rate selected by the sequencer and only the sequencer. We have no rules at the moment regarding the verification of this fee rate. So the sequencer can increase the fee rate independently of the fee rate on bitcoin arbitrarily. A simple solution to this would be for example, let mut l1_fee_rate = get_l1_fee_rate()
l1_fee_rate *= current_cumulative_diff_da_usage / BITCOIN_MAX_DA_BANDWITH thought this is not really smart at all. :) the idea here is that, as we reach the limit, we economically discourage transactions from happening. Not having a |
Do we want to consider a 4MB/10mins or have a moving target depending on current mempool usage ?
What is the end goal of fee ? What should happen if we hit the limit but don't make it to the l1 block in time of high congestion, as in early 2024 ? We need to be mindful of re-orgs that might throw off calculations as well. |
4MB/10mins.
Yes. But the later the disincentivization starts, the better. Don't know how to set it up though :)
Things will get delayed. There's nothing we can do unfortunately. We can leave this as a later issue. |
No description provided.
The text was updated successfully, but these errors were encountered: