Layer-2 Gas Costs Reach Sub-Cent Territory as ZK Rollups Scale

Fees have long been the awkward part of using public blockchains. When the base network is busy, a simple transfer can cost more than the thing being bought. This Launch edition explainer looks at why layer-2 rollups, and zero-knowledge (ZK) rollups in particular, can bring fees down to fractions of a cent in good conditions, and what you give up in exchange. We avoid quoting live fee figures because they change by the hour; we speak in ranges and conditions instead.

Where the savings come from

A rollup executes transactions on its own network and then posts a compact record of the results to the base chain. The base chain is the expensive, scarce resource. By sharing one submission across hundreds or thousands of user transactions, a rollup divides that cost into very small portions.

Three ingredients matter most:

• Batching. Transactions are grouped so the fixed overhead of a base-chain submission is paid once per batch rather than once per user.
• Compression. Rollups strip out data that the base chain does not need, such as redundant signatures or repeated fields, so each transaction occupies fewer bytes.
• Cheaper data availability. Publishing the data that lets anyone reconstruct the rollup's state has become less costly on networks designed with rollups in mind, and that cost is usually the largest slice of what a user pays.

What a zero-knowledge proof adds

A ZK rollup accompanies each batch with a validity proof, a mathematical argument that the new state follows correctly from the old one. The base chain checks the proof rather than re-running every transaction. Verifying a proof is far cheaper than redoing the work, and the cost of one proof is also shared across the whole batch. In general, the larger the batch, the smaller each user's share.

Generating proofs is computationally heavy, and operators run specialised hardware or software to do it. That cost is real, but it is paid by the operator and spread across many users, which is why it can be small per transaction at healthy volumes. At low volumes the shares are larger, so a quiet rollup is not automatically a cheap one.

The trade-offs behind low fees

Cheap does not mean free of compromise. Readers should weigh several points before treating a rollup as a drop-in replacement for the base chain.

• Sequencer centralisation. Most rollups rely on a sequencer, the party that orders transactions. If one operator runs it, that operator can delay or reorder transactions, and users may depend on an escape mechanism to exit if it fails. Plans to decentralise sequencing exist in many projects, but progress varies and should be checked, not assumed.
• Bridging. Moving assets between the base chain and a rollup involves bridge contracts and sometimes third-party liquidity providers. Bridges have been a frequent target for attackers across the industry, so each extra hop adds risk and time.
• Finality. A transaction can appear confirmed on the rollup within moments, yet stronger settlement comes only after the batch is posted and, for ZK designs, the proof is verified. The gap between those two states matters for large or irreversible payments.

What it means for micro-payments

When a fee is a tiny fraction of a cent, new payment shapes become plausible: tipping a writer a small amount, paying per article, charging per API call, or splitting a purchase among several recipients. Under a fee of a few dollars, these ideas collapse. Under a fee that is negligible next to the payment, they at least become worth testing.

The key phrase is worth testing. A payment amount only works if all the surrounding costs are also small. Users still need a wallet, some balance on the right network, and a way in, and the on-ramp from ordinary money often costs more than the transaction. Fees can also rise sharply if demand spikes or if the cost of publishing data on the base chain climbs. A business building around micro-payments should model a range of fee scenarios, including bad ones, rather than designing around today's best case.

Consider an illustrative example. A small newsletter wants to charge readers a tiny amount per article. On a quiet day the rollup fee is negligible and the idea works. On a congested day the fee might eat a meaningful share of each payment. The newsletter could bundle several articles into one charge, or let readers prepay a balance and settle in batches. Design choices like these, not the headline fee alone, decide whether micro-payments hold up.

Questions to ask before relying on a rollup

Treat the following as a checklist rather than a recommendation to use or avoid any network:

1. Who runs the sequencer today, and what is the documented path to exit if it stops?
2. How long does it take to move funds back to the base chain under normal conditions?
3. How has the network's fee range behaved across quiet and busy periods?
4. Where does the data for the rollup's state get published, and who can reconstruct it?
5. Has the code, including the bridge and the proof system, been independently reviewed?

Low fees are a genuine engineering result of batching, compression and proof sharing. They are also a moving target that depends on demand, data costs and design decisions that sit outside any single user's control. This article is educational, not financial or investment advice. Understand the trade-offs, size your exposure accordingly, and verify current conditions from primary sources before you act.