> For the complete documentation index, see [llms.txt](https://spire-docs.gitbook.io/spire/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spire-docs.gitbook.io/spire/da-builder/the-rollup-cost-killer.md). # The Rollup Cost Killer tldr; We can save rollups thousands of dollars on Ethereum transactions. [Get in touch](https://www.spire.dev/contact) today to stop wasting money! ### The Execution Layer Cost Crisis While blob fees get the attention, the reality is that for rollup operators the execution layer gas costs are currently the bulk of the cost for running most rollups. Blob fees are such a small part of the cost to advance a rollup that EIPs are being created to keep them from dropping too low and multiple proposals have been made to modify their pricing in order to improve Ethereum’s economics. {% embed url="" %} This cost impacts blob submission rate and therefore the time-to-finality and time-to-withdrawal for users on L2s. The following thread shows how Scroll has 7x’ed their time-to-finality likely because blob submission costs are too high to justify posting blobs more often. {% embed url="" %} **Current Reality:** Each rollup pays full execution costs for their individual blob submissions. **The Numbers:** You can see a breakdown of the costs of blob submission for Taiko in the dune query below. ![Potential Blob Savings.png](/files/ZjW0jFw2J6Qgrc5W2gcK) {% embed url="" %} Taiko, at the time of this post, sees an average of \~$20k/week in total blob transaction costs since Pectra. i.e. On a weekly average rollups spend \~99.999% of their total blob submission costs on execution layer transactions alone. Looking at the data for the week of 2025-06-09 Taiko paid $21,101.58 in total fees, with less than a cent going specifically to the cost of blobs and everything else going to execution layer costs. This means rollups are spending tens of thousands of dollars on transaction overhead rather than data availability. ### The Blob Aggregation Revolution Blob aggregation helps to solve both blob AND execution layer costs. When multiple rollups can submit blobs using the same L1 transaction the 21k min gas cost is only paid once and the cost can be split across the rollups participating in the aggregation. For Taiko that 21k gas cost is still \~$2k/week. If those transactions were paired with another rollup’s that would be \~$4k/month in savings or the ability to post blobs more often and halve the time-to-finality for the chain. If we had 10 rollups all posting together that 21k in gas would cost \~$200/week with $7,200/month in savings. Of course, this is only a baseline savings estimate for execution costs. When blob pricing EIPs land on mainnet and/or blob saturation is reached the savings will be even greater. ### Conclusion The execution layer cost savings from blob aggregation represent a fundamental shift in rollup economics. By eliminating redundant transaction overhead rollups can achieve significant cost reductions to improve their profitability while improving reliability and user experience at the same time. Don't miss out! **Register now** through our [sign-up form](https://www.spire.dev/contact) to secure your place for our mainnet launch and start saving on execution costs immediately! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://spire-docs.gitbook.io/spire/da-builder/the-rollup-cost-killer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.