Skip to content

Conversation

@asomani-ocl
Copy link

@asomani-ocl asomani-ocl commented Jan 6, 2026

Thank you for contributing to our docs!

Please fill out the below to ensure your doc gets quickly approved and merged.

Description

Document type

  • Gentle introduction
  • Quickstart
  • How-to
  • Concept
  • FAQ
  • Troubleshooting
  • Reference
  • Third-party content
  • Not applicable

Checklist

  • I have read the CONTRIBUTE.md guidelines
  • My changes follow the style conventions outlined in CONTRIBUTE.md
  • I have used sentence-case for titles and headers
  • I have used descriptive link text (not "here" or "this")
  • I have separated procedural from conceptual content where appropriate
  • I have tested my changes locally with yarn start or yarn build
  • My code follows the existing code style and conventions
  • I have added/updated frontmatter for new documents
  • I have checked for broken links
  • I have verified that my changes don't break the build
  • Third-party docs only: Do you agree to the third-party content policy outlined within CONTRIBUTE.md?
    • Yes
    • Not applicable

Additional Notes

@vercel
Copy link

vercel bot commented Jan 6, 2026

@asomani-ocl is attempting to deploy a commit to the Offchain Labs - AF Billed Team on Vercel.

A member of the Team first needs to authorize it.

@CLAassistant
Copy link

CLAassistant commented Jan 6, 2026

CLA assistant check
All committers have signed the CLA.

@anegg0 anegg0 self-requested a review January 6, 2026 22:51
Copy link
Member

@leeederek leeederek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's avoid using Constraints in our public references (as much as possible). The entire new pricing algorithm is called Dynamic Pricing. I tried to catch and suggest changes where it made sense, but i might've missed a few. Thanks!

@vercel
Copy link

vercel bot commented Jan 8, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
arbitrum-docs Ready Ready Preview Jan 14, 2026 7:55pm

@vercel
Copy link

vercel bot commented Jan 9, 2026

Deployment failed with the following error:

You don't have permission to create a Preview Deployment for this Vercel project: arbitrum-docs.

View Documentation: https://vercel.com/docs/accounts/team-members-and-roles


## How to set multiple gas targets

You can call `SetGasPricingConstraints` on the [ArbOwner precompile](../../../for-devs/dev-tools-and-resources/partials/precompile-tables/_ArbOwner) with an array of gas targets (the code refers to these targets as "constraints"), where each constraint contains \[gasTargetPerSecond, adjustmentWindowSeconds, startingBacklogValue\].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
You can call `SetGasPricingConstraints` on the [ArbOwner precompile](../../../for-devs/dev-tools-and-resources/partials/precompile-tables/_ArbOwner) with an array of gas targets (the code refers to these targets as "constraints"), where each constraint contains \[gasTargetPerSecond, adjustmentWindowSeconds, startingBacklogValue\].
You can call `SetGasPricingConstraints` on the [ArbOwner precompile](../../../for-devs/dev-tools-and-resources/partials/precompile-tables/_ArbOwner) with an array of gas targets (the code refers to these targets as "constraints"), where each constraint contains `\[gasTargetPerSecond, adjustmentWindowSeconds, startingBacklogValue\]`.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@leeederek should this be in block?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

which word are you referring to

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[gasTargetPerSecond, adjustmentWindowSeconds, startingBacklogValue]

[State Growth Guidance](../../maintain-your-chain/guidance/state-growth): Impact of high gas targets on state growth and its consequences

- node_throughput \- Sustainable maximum throughput that the nodes can maintain without any issues. This is highly dependent on your specific hardware and chain workload. Offchain Labs will soon publish testing frameworks and tools that can be used to benchmark what throughput your nodes can handle for various workloads.
- gas_limit \- Theoretical max block size limit. With the introduction of the `MaxTxGasLimit`, the effective block gas limit is twice the `MaxBlockGasLimit`. We recommend using an in-between value of `MaxBlockGasLimit` and Effective Block gas limit `(MaxTxGasLimit + MaxBlockGasLimit)` for this parameter.
Copy link
Contributor

@zk-Lumi zk-Lumi Jan 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@anegg0 we should add a link to the explanation in docs on effective block gas limit

Co-authored-by: Daniel Lumi <[email protected]>

- node_throughput \- Sustainable maximum throughput that the nodes can maintain without any issues. This is highly dependent on your specific hardware and chain workload. Offchain Labs will soon publish testing frameworks and tools that can be used to benchmark what throughput your nodes can handle for various workloads.
- gas_limit \- Theoretical max block size limit. With the introduction of the `MaxTxGasLimit`, the effective block gas limit is twice the `MaxBlockGasLimit`. We recommend using an in-between value of `MaxBlockGasLimit` and Effective Block gas limit `(MaxTxGasLimit + MaxBlockGasLimit)` for this parameter.
- max_rate_of_increase_percent_per_second \- maximum allowed rate of increase in the fee per sec when the chain is working at the max capacity.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- max_rate_of_increase_percent_per_second \- maximum allowed rate of increase in the fee per sec when the chain is working at the max capacity.
- `max_rate_of_increase_percent_per_second` \- maximum allowed rate of increase in the fee per sec when the chain is working at the max capacity.


Refer to the definitions below to understand what each parameter means:

- gasTargetPerSecond \- the target gas processing rate for your Arbitrum chain \- it's the amount of gas the system aims to process each second under normal conditions. Any demand above this target will induce a gas price increase as a way to economically disincentivize usage until it gets reduced to the target.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- gasTargetPerSecond \- the target gas processing rate for your Arbitrum chain \- it's the amount of gas the system aims to process each second under normal conditions. Any demand above this target will induce a gas price increase as a way to economically disincentivize usage until it gets reduced to the target.
- `gasTargetPerSecond` \- the target gas processing rate for your Arbitrum chain \- it's the amount of gas the system aims to process each second under normal conditions. Any demand above this target will induce a gas price increase as a way to economically disincentivize usage until it gets reduced to the target.

Refer to the definitions below to understand what each parameter means:

- gasTargetPerSecond \- the target gas processing rate for your Arbitrum chain \- it's the amount of gas the system aims to process each second under normal conditions. Any demand above this target will induce a gas price increase as a way to economically disincentivize usage until it gets reduced to the target.
- adjustmentWindowSeconds \- time period with which the system will measure average gas demand/usage over to determine whether or not the gas price needs to be adjusted, relative to the gas target. A larger window results in more stable, predictable pricing, while a smaller window reacts aggressively to traffic spikes.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- adjustmentWindowSeconds \- time period with which the system will measure average gas demand/usage over to determine whether or not the gas price needs to be adjusted, relative to the gas target. A larger window results in more stable, predictable pricing, while a smaller window reacts aggressively to traffic spikes.
- `adjustmentWindowSeconds` \- time period with which the system will measure average gas demand/usage over to determine whether or not the gas price needs to be adjusted, relative to the gas target. A larger window results in more stable, predictable pricing, while a smaller window reacts aggressively to traffic spikes.


- gasTargetPerSecond \- the target gas processing rate for your Arbitrum chain \- it's the amount of gas the system aims to process each second under normal conditions. Any demand above this target will induce a gas price increase as a way to economically disincentivize usage until it gets reduced to the target.
- adjustmentWindowSeconds \- time period with which the system will measure average gas demand/usage over to determine whether or not the gas price needs to be adjusted, relative to the gas target. A larger window results in more stable, predictable pricing, while a smaller window reacts aggressively to traffic spikes.
- startingBacklogValue \- the initial amount of gas the system uses to set prices the **exact moment** the gasTargetPerSecond and adjustmentWindowSeconds get changed.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- startingBacklogValue \- the initial amount of gas the system uses to set prices the **exact moment** the gasTargetPerSecond and adjustmentWindowSeconds get changed.
- `startingBacklogValue` \- the initial amount of gas the system uses to set prices the **exact moment** the gasTargetPerSecond and adjustmentWindowSeconds get changed.


| Param | Arbitrum One Config |
| :-------------------------------------- | :------------------ |
| long_term_gas_target | 10 Mgas/s |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| long_term_gas_target | 10 Mgas/s |
| `long_term_gas_target` | 10 Mgas/s |

| Param | Arbitrum One Config |
| :-------------------------------------- | :------------------ |
| long_term_gas_target | 10 Mgas/s |
| node_throughput | 80 Mgas/s |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| node_throughput | 80 Mgas/s |
| `node_throughput` | 80 Mgas/s |

| :-------------------------------------- | :------------------ |
| long_term_gas_target | 10 Mgas/s |
| node_throughput | 80 Mgas/s |
| gas_limit | 128 Mgas/s |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| gas_limit | 128 Mgas/s |
| `gas_limit` | 128 Mgas/s |

| long_term_gas_target | 10 Mgas/s |
| node_throughput | 80 Mgas/s |
| gas_limit | 128 Mgas/s |
| max_rate_of_increase_percent_per_second | 20 |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| max_rate_of_increase_percent_per_second | 20 |
| `max_rate_of_increase_percent_per_second` | 20 |

| node_throughput | 80 Mgas/s |
| gas_limit | 128 Mgas/s |
| max_rate_of_increase_percent_per_second | 20 |
| long_term_adjustment_window_seconds | 86400 sec |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| long_term_adjustment_window_seconds | 86400 sec |
| `long_term_adjustment_window_seconds` | 86400 sec |

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants