[OP Stack Deployment] Optimizing Gas Consumption for OP Batcher with Blob data avaibility type on Sepolia #588
Replies: 2 comments 2 replies
-
sepolia support eip-4844,so you can use blob in sepolia but not every chain using blob can have lower gas fees, because if your chain has less activity then use blob without filling it all, will cause the waste |
Beta Was this translation helpful? Give feedback.
-
@imtipi I had added export OP_BATCHER_DATA_AVAILABILITY_TYPE=blobs in .envec file ,each step before batcher is working but getting below error while initializing batcher INFO [09-11|14:13:39.709] Initializing Batch Submitter |
Beta Was this translation helpful? Give feedback.
-
Did you check the documentation?
Did you check for duplicate questions?
Issue Description
Hello Team,
I’m currently running my own L2 Rollup Testnet using Sepolia and observed that transactions from the OP batcher use the Transfer method there, while on Mainnet, the method shows as commit blob.
I’m considering setting the environment variable OP_BATCHER_DATA_AVAILABILITY_TYPE=blobs to enable blob-based data availability similar to the Mainnet setup. I have a few questions:
Can I enable blob commitments on Sepolia using the OP_BATCHER_DATA_AVAILABILITY_TYPE=blobs environment variable, just like on Mainnet?
Will using blobs on Sepolia reduce gas consumption for the batcher compared to the current Transfer method?
Does the batcher inherently consume fewer resources when using blobs, or are there additional steps or optimizations I should consider to further reduce gas fees?
Kindly assist me best practices on optimizing gas consumption in this setup.
Logs
No response
Additional Information
No response
Feedback
No response
Beta Was this translation helpful? Give feedback.
All reactions