From 15ab29022289a6ed898eb7f0b9d039c49a51a537 Mon Sep 17 00:00:00 2001 From: Jason-Wanxt Date: Wed, 28 May 2025 00:51:47 +0800 Subject: [PATCH 1/4] add more optional parameters and refer to arbos docs --- .../14-enable-post-4844-blobs.mdx | 16 ++++++++++++- .../arbos-releases/arbos20.mdx | 24 +------------------ 2 files changed, 16 insertions(+), 24 deletions(-) diff --git a/arbitrum-docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/14-enable-post-4844-blobs.mdx b/arbitrum-docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/14-enable-post-4844-blobs.mdx index 31581904c..e3347207b 100644 --- a/arbitrum-docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/14-enable-post-4844-blobs.mdx +++ b/arbitrum-docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/14-enable-post-4844-blobs.mdx @@ -92,7 +92,21 @@ numBlobs=1 Your node may continue using calldata in these scenarios: -1. **Cost optimization**: When blob gas prices are high, calldata posting may be more economical +1. **Cost optimization**: When blob gas prices are high, calldata posting may be more economical, but you can set the `--node.batch-poster.ignore-blob-price` flag to `true` to force the batch poster to use blobs. 2. **Batch Type Switching Protection**: After a non-blob transaction is posted, the next 16 transactions will also use calldata to prevent frequent switching Check your node logs for blob-related error messages and verify that your parent chain is accessible and fully synced. + +## Optional parameters + +You can also set the following optional parameters to control blob posting behavior: + +| Flag | Description | +| ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `--node.batch-poster.ignore-blob-price` | Boolean. Default: `false`. If the parent chain supports EIP4844 blobs and `ignore-blob-price` is set to `true`, the batch poster will use EIP4844 blobs even if using calldata is cheaper. Can be `true` or `false`. | +| `--parent-chain.blob-client.authorization` | String. Default: `""`. Value to send with the HTTP Authorization: header for Beacon REST requests, must include both scheme and scheme parameters | +| `--parent-chain.blob-client.secondary-beacon-url` | String. Default: `""`. Value to send with the HTTP Authorization: header for Beacon REST requests, must include both scheme and scheme parameters | +| `--node.batch-poster.data-poster.blob-tx-replacement-times` | durationSlice. Default: `[5m0s,10m0s,30m0s,1h0m0s,4h0m0s,8h0m0s,16h0m0s,22h0m0s]`. comma-separated list of durations since first posting a blob transaction to attempt a replace-by-fee | +| `--node.batch-poster.data-poster.max-blob-tx-tip-cap-gwei` | float. Default: `1`. the maximum tip cap to post EIP-4844 blob carrying transactions at | +| `--node.batch-poster.data-poster.min-blob-tx-tip-cap-gwei` | float. Default: `1`. the minimum tip cap to post EIP-4844 blob carrying transactions at | +| `--node.batch-poster.max-4844-batch-size` | int. Default: `0`. maximum estimated compressed 4844 blob enabled batch size | diff --git a/arbitrum-docs/run-arbitrum-node/arbos-releases/arbos20.mdx b/arbitrum-docs/run-arbitrum-node/arbos-releases/arbos20.mdx index cfe8ada88..7f894ca01 100644 --- a/arbitrum-docs/run-arbitrum-node/arbos-releases/arbos20.mdx +++ b/arbitrum-docs/run-arbitrum-node/arbos-releases/arbos20.mdx @@ -49,29 +49,7 @@ This section maps to [Step 4 in the guide on _How to upgrade ArbOS on your Arbit :::caution Before proceeding, make sure you have successfully completed Steps 1 through 3 of the guide on [How to upgrade ArbOS on your Arbitrum chain](/launch-arbitrum-chain/02-configure-your-chain/common-configurations/13-arbos-upgrade.mdx). -To enable the posting of transaction data in Blobs to L1 Ethereum, you must set `node.batch-poster.post-4844-blobs=true` on the batch poster. - -#### Full list of ArbOS Atlas specific configuration options for Arbitrum chains - -| Flag | Description | -| --------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `--node.batch-poster.post-4844-blobs` | Boolean. Default: `false`. Used to enable or disable the posting of transaction data using Blobs to L1 Ethereum. If using calldata is more expensive and if the parent chain supports EIP4844 blobs, the batch poster will use blobs when this flag is set to `true`. Can be `true` or `false`. | -| `--node.batch-poster.ignore-blob-price` | Boolean. Default: `false`. If the parent chain supports EIP4844 blobs and `ignore-blob-price` is set to `true`, the batch poster will use EIP4844 blobs even if using calldata is cheaper. Can be `true` or `false`. | - -The above configurations are also available in the [Nitro command line options reference section](/run-arbitrum-node/03-run-full-node.mdx#optional-parameters) and can be set using the command line or using the JSON node configuration below: - -```json - "node": { - ... - "batch-poster": { - ... - "post-4844-blobs": true, - "ignore-blob-price": false, - ... - }, - } - -``` +To enable the posting of transaction data in Blobs to L1 Ethereum, please refer to the [Enable post-4844 blobs](/launch-arbitrum-chain/02-configure-your-chain/common-configurations/14-enable-post-4844-blobs.mdx) section of the Arbitrum chain configuration guide. ### Reference links for ArbOS 20 Atlas From 89bb93811aec477f2428fdccd12d8f15f7d5c748 Mon Sep 17 00:00:00 2001 From: Jason-Wanxt Date: Wed, 28 May 2025 00:55:59 +0800 Subject: [PATCH 2/4] remove --- .../common-configurations/14-enable-post-4844-blobs.mdx | 1 - 1 file changed, 1 deletion(-) diff --git a/arbitrum-docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/14-enable-post-4844-blobs.mdx b/arbitrum-docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/14-enable-post-4844-blobs.mdx index e3347207b..4a264b9b5 100644 --- a/arbitrum-docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/14-enable-post-4844-blobs.mdx +++ b/arbitrum-docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/14-enable-post-4844-blobs.mdx @@ -109,4 +109,3 @@ You can also set the following optional parameters to control blob posting behav | `--node.batch-poster.data-poster.blob-tx-replacement-times` | durationSlice. Default: `[5m0s,10m0s,30m0s,1h0m0s,4h0m0s,8h0m0s,16h0m0s,22h0m0s]`. comma-separated list of durations since first posting a blob transaction to attempt a replace-by-fee | | `--node.batch-poster.data-poster.max-blob-tx-tip-cap-gwei` | float. Default: `1`. the maximum tip cap to post EIP-4844 blob carrying transactions at | | `--node.batch-poster.data-poster.min-blob-tx-tip-cap-gwei` | float. Default: `1`. the minimum tip cap to post EIP-4844 blob carrying transactions at | -| `--node.batch-poster.max-4844-batch-size` | int. Default: `0`. maximum estimated compressed 4844 blob enabled batch size | From c5d252e7edb266d3be81e799ca3706cb569f1648 Mon Sep 17 00:00:00 2001 From: Jason-W123 <147362502+Jason-W123@users.noreply.github.com> Date: Wed, 28 May 2025 15:53:57 +0800 Subject: [PATCH 3/4] Update arbitrum-docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/14-enable-post-4844-blobs.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Gaël Blanchemain --- .../common-configurations/14-enable-post-4844-blobs.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/arbitrum-docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/14-enable-post-4844-blobs.mdx b/arbitrum-docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/14-enable-post-4844-blobs.mdx index 4a264b9b5..8244e9e12 100644 --- a/arbitrum-docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/14-enable-post-4844-blobs.mdx +++ b/arbitrum-docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/14-enable-post-4844-blobs.mdx @@ -103,9 +103,9 @@ You can also set the following optional parameters to control blob posting behav | Flag | Description | | ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `--node.batch-poster.ignore-blob-price` | Boolean. Default: `false`. If the parent chain supports EIP4844 blobs and `ignore-blob-price` is set to `true`, the batch poster will use EIP4844 blobs even if using calldata is cheaper. Can be `true` or `false`. | +| `--node.batch-poster.ignore-blob-price` | Boolean. Default: `false`. If the parent chain supports `EIP-4844` blobs and `ignore-blob-price` is set to `true`, the batch poster will use `EIP-4844` blobs even if using calldata is cheaper. Can be `true` or `false`. | | `--parent-chain.blob-client.authorization` | String. Default: `""`. Value to send with the HTTP Authorization: header for Beacon REST requests, must include both scheme and scheme parameters | | `--parent-chain.blob-client.secondary-beacon-url` | String. Default: `""`. Value to send with the HTTP Authorization: header for Beacon REST requests, must include both scheme and scheme parameters | | `--node.batch-poster.data-poster.blob-tx-replacement-times` | durationSlice. Default: `[5m0s,10m0s,30m0s,1h0m0s,4h0m0s,8h0m0s,16h0m0s,22h0m0s]`. comma-separated list of durations since first posting a blob transaction to attempt a replace-by-fee | -| `--node.batch-poster.data-poster.max-blob-tx-tip-cap-gwei` | float. Default: `1`. the maximum tip cap to post EIP-4844 blob carrying transactions at | -| `--node.batch-poster.data-poster.min-blob-tx-tip-cap-gwei` | float. Default: `1`. the minimum tip cap to post EIP-4844 blob carrying transactions at | +| `--node.batch-poster.data-poster.max-blob-tx-tip-cap-gwei` | float. Default: `1`. the maximum tip cap to post `EIP-4844` blob-carrying transactions at | +| `--node.batch-poster.data-poster.min-blob-tx-tip-cap-gwei` | float. Default: `1`. the minimum tip cap to post `EIP-4844` blob-carrying transactions at | From 566d88618ba49c975fd4adc15a2249b9f437c56d Mon Sep 17 00:00:00 2001 From: Jason-Wanxt Date: Wed, 28 May 2025 15:57:38 +0800 Subject: [PATCH 4/4] format --- .../14-enable-post-4844-blobs.mdx | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/arbitrum-docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/14-enable-post-4844-blobs.mdx b/arbitrum-docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/14-enable-post-4844-blobs.mdx index 8244e9e12..b4c85ff69 100644 --- a/arbitrum-docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/14-enable-post-4844-blobs.mdx +++ b/arbitrum-docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/14-enable-post-4844-blobs.mdx @@ -101,11 +101,11 @@ Check your node logs for blob-related error messages and verify that your parent You can also set the following optional parameters to control blob posting behavior: -| Flag | Description | -| ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Flag | Description | +| ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `--node.batch-poster.ignore-blob-price` | Boolean. Default: `false`. If the parent chain supports `EIP-4844` blobs and `ignore-blob-price` is set to `true`, the batch poster will use `EIP-4844` blobs even if using calldata is cheaper. Can be `true` or `false`. | -| `--parent-chain.blob-client.authorization` | String. Default: `""`. Value to send with the HTTP Authorization: header for Beacon REST requests, must include both scheme and scheme parameters | -| `--parent-chain.blob-client.secondary-beacon-url` | String. Default: `""`. Value to send with the HTTP Authorization: header for Beacon REST requests, must include both scheme and scheme parameters | -| `--node.batch-poster.data-poster.blob-tx-replacement-times` | durationSlice. Default: `[5m0s,10m0s,30m0s,1h0m0s,4h0m0s,8h0m0s,16h0m0s,22h0m0s]`. comma-separated list of durations since first posting a blob transaction to attempt a replace-by-fee | -| `--node.batch-poster.data-poster.max-blob-tx-tip-cap-gwei` | float. Default: `1`. the maximum tip cap to post `EIP-4844` blob-carrying transactions at | -| `--node.batch-poster.data-poster.min-blob-tx-tip-cap-gwei` | float. Default: `1`. the minimum tip cap to post `EIP-4844` blob-carrying transactions at | +| `--parent-chain.blob-client.authorization` | String. Default: `""`. Value to send with the HTTP Authorization: header for Beacon REST requests, must include both scheme and scheme parameters | +| `--parent-chain.blob-client.secondary-beacon-url` | String. Default: `""`. Value to send with the HTTP Authorization: header for Beacon REST requests, must include both scheme and scheme parameters | +| `--node.batch-poster.data-poster.blob-tx-replacement-times` | durationSlice. Default: `[5m0s,10m0s,30m0s,1h0m0s,4h0m0s,8h0m0s,16h0m0s,22h0m0s]`. comma-separated list of durations since first posting a blob transaction to attempt a replace-by-fee | +| `--node.batch-poster.data-poster.max-blob-tx-tip-cap-gwei` | float. Default: `1`. the maximum tip cap to post `EIP-4844` blob-carrying transactions at | +| `--node.batch-poster.data-poster.min-blob-tx-tip-cap-gwei` | float. Default: `1`. the minimum tip cap to post `EIP-4844` blob-carrying transactions at |