As Ethereum scales through rollups, one challenge has become clear: every rollup has its own way of pricing gas. Some use calldata, some use blobs, others rely on proof costs or computation complexity. This diversity makes it hard for wallets, protocols, and relayers to reason about costs - let alone optimize them.
To solve this, we’re introducing RIGID: the Rollup Interoperable Gas Interface Declaration.
RIGID is a proposed onchain standard that lets rollups publish their gas market logic in a structured, machine-actionable, and verifiable format. Think of it as an onchain schema for gas - one designed for automation, versioning, and trustless interoperability.
RIGID declarations are encapsulated in a GasMarketDeclaration
struct and include:
FeeComponent
arrays with RPN (Reverse Polish Notation) formulas, parameters, and accepted payment tokens.In short: RIGID would serve as the source of truth for how gas works on every chain.
The diversity of rollup fee models isn't the problem - the lack of structured, onchain visibility is. Today, fee logic is often opaque, undocumented, or not published in a way that external agents can reliably use. This creates significant friction across the ecosystem, impacting various participants:
Without clear, verifiable declarations of gas mechanics, every participant - from developers to automated agents - is left guessing. This is a growing liability in a multichain world where execution is increasingly dynamic, asynchronous, and decentralized.
RIGID fixes that by bringing clarity, automation, and governance alignment to gas pricing. It shifts the source of truth from opaque offchain sources to verifiable onchain declarations, enabling machine interpretability and aggregation across the L2 ecosystem.
RIGID leverages highly optimized data structures for its declarations. These are designed for maximum efficiency in onchain storage and for machine-actionable parsing. The core of any RIGID declaration is encapsulated within the GasMarketDeclaration
struct.
Here’s a diagram representing a GasMarketDeclaration
any rollup can use to define its gas market:
GasMarketDeclaration Onchain Data Structure Diagram V1.0
For more details, refer to the RIP draft here: https://github.com/ethereum/RIPs/pull/73
As we move from transaction-centric to message-based architectures (ERC-7786: The Crosschain Messaging Gateway), applications need to estimate and verify gas costs across multiple chains - even if they don't control routing.
This is where RIGID and Gas Network work together:
Together, they enable:
We believe RIGID is a foundational step toward a multichain world where:
Just like we have standards for tokens (ERC-20), metadata (ERC-1046), and node discovery - it’s time we had one for gas.
RIGID is still in draft form. We’re sharing it with the community for feedback and iteration. If you’re building on rollups, care about gas fee UX, or operate infrastructure that spans L2s, we’d love your input.
👉 Read the full RIP draft here: https://github.com/ethereum/RIPs/pull/73
👉 Join the conversation on Eth Magicians.