Fix Fee Oversight ArbOS v20 "Atlas"

Request Non-Emergency Security Council Action

Abstract

The transaction fee paid by users is composed of two parts, L2 fees and L1 fees, which together include the execution cost for running the transaction on Arbitrum alongside the cost of posting data to Ethereum (to learn more about this, read the deep dive on the subject).

Historically, the rollup fee market has been dominated by the L1 cost component. With the Dencun upgrade soon being enabled on Ethereum, the current pricing structure may no longer be optimal. The ArbOS Version 20 “Atlas” upgrade is a step towards better consuming the new data availability affordances offered by Ethereum, but will also potentially require further adjustment once EIP-4844 has been deployed and tested.

There was an oversight during the ArbOS Version 20 “Atlas” upgrade where two configuration should be updated for users when the Dencun upgrade occurs:

  • L1 surplus fee. Reduce the surplus fee per byte from 2 gwei to 0.
  • L2 base fee. Reduce the minimum from 0.1 gwei to 0.01 gwei.

In both cases, the configuration changes will match what is currently implemented in Arbitrum Nova. As evidenced by the recent surge of transactions in Arbitrum Nova, the network can handle the increased transaction throughput while offering lower fees for users in general under that configuration.

Impact on the ArbitrumDAO’s revenue

The L2 base fee change will impact the revenue received by the ArbitrumDAO. The potential impact based on the past 30 days of activity was calculated, which if the changes had been implemented (ignoring potential changes in demand based on lower fees), would have resulted in overall profit going from 816.13 ETH → 79.89 ETH

While the fee reduction will result in lower revenue for the ArbitrumDAO in the short term, it will ensure that the Arbitrum One network continues to offer competitive costs to its users and in turn it can lead to an increase in transaction traffic.

Since the parameter change affects the revenue generated, it is important to carry out a temperature check for the ArbitrumDAO to discuss and ultimately vote on the change. If it is approved by the ArbitrumDAO, then the Security Council will be requested to initiate a non-emergency action to execute the configuration change. The goal is to ensure the fees are changed as soon as possible in line with the Decun upgrade.

Implementation details

The following configured values will be changed in the ArbOwner smart contract that can be viewed in Contract Address 0x000000000000000000000000000000000000006b | Arbiscan.

The following governance action smart contracts will be used to initiate the action:

The security council will separate the two parameter change actions to enable the ArbitrumDAO to decide whether to accept one, both, or neither. The ability to decide will be reflected on Snapshot using a ranked voting with the following options:

  • Set L1 surplus fee and L2 minimum base fee.
  • Set only L1 surplus fee.
  • Set only L2 minimum base fee.
  • Set neither option and cancel security council action.

Timeline

The ArbOS v20 “Atlas” upgrade is due to be activated on the 14th of March, and the following schedule will be pursued to address the configuration issues in a timely manner:

  • 5th March - Temperature Vote on Snapshot
  • 5th March - Initiate non-emergency security council action
  • 18th March - Activate configuration change to reduce fees

A non-emergency security council action is viewed as ideal as it exists primarily to approve and implement routine software upgrades, routine maintenance and other parameter adjustments in a non-emergency setting.

Temperature check:
https://snapshot.org/#/arbitrumfoundation.eth/proposal/0x13bcccfeeb736c732bdd08032841d6a07614d17dcee2d29a435e7b0114361a0a
Security council transaction: Arbitrum Transaction Hash (Txhash) Details | Arbiscan

Taking this route will mean that Arbitrum One network will have higher than anticipated fees for 5 days.

The following governance calls will also enable the community to discuss the technical changes:

  • 6th March - Wednesday at 6pm EST
  • 7th March - Thursday at 9am EST

Both calls will be added to the governance call and more calls can be arranged if necessary.

7 Likes

Seems appropriate. Let’s get it done.

1 Like

Hello,
I think that it is important to know how ArbitrumDAO uses this fees.
It’s a huge amount of fee, therefore, it would be good to understand that this will not affect a significant reduction in Arbitrum nodes due to the lack of profit.

1 Like

A simulation of the change is available in governance-seatbelt and can be run locally with SIM_NAME=non-emerg-sc-atlas-fees yarn start

2 Likes

Hello,
I found old comment about this changes, and I have some same questions
L2 base fee needs to prevent certain attack vectors/spamming/DDOS of the chain.
Therefore, questions I think needing clear answers:

  • Is the attack vector the gas floor price is guarding against expected to always exist? (If it’s expected to eventually become obsolete, the gas floor price could be retired at that time)
  • Would a governance proposal to reduce the gas floor price (e.g. reduce to 0.001 gwei)? Why 0.01?
1 Like
  • Is the attack vector the gas floor price is guarding against expected to always exist? (If it’s expected to eventually become obsolete, the gas floor price could be retired at that time)

The base fee does help with DOS resistance.
Even without a floor to this value (which Ethereum also doesn’t have), the base fee will rise when demand is bigger than supply - deterring attacks by making them more expensive (just like in Ethereum).

Would a governance proposal to reduce the gas floor price (e.g. reduce to 0.001 gwei)? Why 0.01?

The Arbitrum Nova chain has been running with the 0.01gwei configuration for some time now and has evidenced that the system is stable under that config. The current proposal aligns Arbitrum One with that configuration.

2 Likes

The security council non emergency action was initiated in Arbitrum Transaction Hash (Txhash) Details | Arbiscan

It will execute onchain and update the parameters in 13 days unless vetoed.
The veto smart contracts are available in ActionCanExecute | Address 0xb50b01F98aa7Ad564688175506edE255B53e8193 | Arbiscan and ActionCanExecute | Address 0xbd8aee9e75ebc23774273bdee518245a99191b44 | Arbiscan

1 Like

Out team cp0x voted FOR this fix.
It fixes important parameters for reducing commissions and increasing competitiveness Arbitrum.

1 Like

I see no reason not to implement this update. The main issue is network security and I see that you have already answered that question, so I support it

1 Like

Maintaining competitive costs while optimizing fee structures is crucial for the network’s sustainability. Fully support this initiative!

2 Likes

This explanation is awesome and as usual we trust our arbitrum overloards. Yes vote, and we set L1 surplus and L2 min cause we love the race to 0.

2 Likes

@juanbug and I have posted our perspective below on behalf of the Uniswap DAO’s Arbitrum governance team (UADP).

We voted to “Set L1 surplus fee and L2 min” since by aligning Arbitrum’s fee structure with these enhancements, costs for users will fall, which is critical for maintaining Arbitrum’s appeal in a competitive Layer 2 landscape. Sure, we’ll see a revenue decrease, but that’s a needed sacrifice to make sure Arbitrum is able to price compete. The hope is that higher volume compensates for lower marginal revenues, thereby returning total revenue to its previous level–and ideally beyond that.

1 Like

We voted “Set L1 surplus fee and L2 min” because we believe this is necessary for Arbitrum to stay the number one L2 and potentially even increase our lead. We’re confident that the higher volume and potential priority fees will make up for most of the decrease in profits. Worst case scenario we can change these parameters later on.

1 Like

On behalf of the Arbitrum delegates who entrusted their voting power to me, I’m voting FOR the proposed fix related to Fee Oversight in ArbOS v20 “Atlas” at the Snapshot stage. After carefully reviewing the details and simulations provided by the Arbitrum Foundation, I feel well-informed about the consequences of this adjustment.

The Foundation has been transparent in their communication, offering a comprehensive breakdown of the issue at hand and the proposed solution. The simulations they provided demonstrate the potential impact of the fix, allowing delegates to make an educated decision.

Moreover, Fred from the Foundation has been diligent in addressing the questions and concerns raised by the community. His prompt and thorough responses have further clarified the rationale behind the proposal and its expected outcomes.

1 Like

I have voted “Set L1 Surplus Fee and L2 Minimum Base Fee”. The fee reduction will keep Arbitrum competitive and the security concerns have been addressed. I have trust in the Arbitrum team / security council understanding of the network as part of the implementation of this change.

I will also add the explanation for this is very easy to follow and greatly appreciated, as I know from the last upgrade posts there was an ask to make the upgrades simpler to follow for less technically-savy Delegates. While I know ultimately this is a fairly simple topic itself, thank you for taking that into consideration on this post.

1 Like

Blockworks Research is voting in favor of setting both the L1 surplus and L2 min fees. We believe that at this point in the rollup race, Arbitrum is greatly benefited by optimizing for UX and minimizing end user fees. That said, it is worth continuing the conversation around fees. We believe research should be commissioned into at what fee users become insensitive in order to optimize for both sequencer revenue and user experience (possibly a good use of the ARDC.)

3 Likes

After consideration Treasure’s Arbitrum Representative Council (ARC) would like to share the following feedback on the proposal

We’ve voted in favour of “Set L1 Surplus Fee and L2 Minimum Base Fee.”

Our decision is driven by the importance of optimising user experience and minimising fees to uphold Arbitrum’s competitiveness in Layer 2. We are supportive of @BlockworksResearch’s suggestion for further research on user fee sensitivity, but for the time being feel confident that potential increases in transaction volume and priority fees will counterbalance any profit reductions from these adjustments.

Thus, we wholeheartedly endorse the proposed fix in ArbOS v20 “Atlas,” seeing it as a strategic step towards maintaining Arbitrum’s leading position in Layer 2 while prioritizing user experience.

1 Like

At Tané, we are voting in favor of “Set L1 Surplus Fee and L2 Minimum Base Fee” because we believe DAO should prioritize the protocol’s UX over its revenue at this moment.

However, 90% reduction of the revenue shouldn’t be taken naturally, especially when more reductions comes from the L2 base fee change while its reasoning is only that the same number is set for Arbitrum Nova without any other base fee simulations. We would love to see further researches around fee, suggested by @BlockworksResearch and discuss the suitable fee in the future.

1 Like

After reviewing the proposal, we will support reducing the L1 Surplus Fee and L2 Minimum Base Fee.

This decision prioritizes improving user experience by lowering transaction costs on the Arbitrum network, ensuring we remain competitive in the Layer 2 space. Lowering these fees is crucial for attracting more users by making transactions more affordable, which can lead to increased network activity. However, we also believe that a research should be done on the fee rate in order to optimize between the sequencer revenue and user experience like @BlockworksResearch suggested.

1 Like

The below response reflects the views of L2BEAT’s governance team, composed of @krst and @Sinkas, and it’s based on the combined research, fact-checking, and ideation of the two.

We’re voting in favor of the proposal during temp-check (both to set the surplus fee and L2 minimum base fee) and we are supportive of this action being executed solely by the security council given the exceptional circumstances.

One thing that was mentioned during the call hosted by the Foundation to discuss the fix was that it would be interesting to be able to manage those parameters in a different way (for example by a separate smart contract controlled by the Foundation with limited ability to adapt the parameters) and not have to do a full contract upgrade route every time. It’s something that we should consider exploring as a DAO going forward.

4 Likes