Gas Limit and LP Transaction Flow

Why Liquidity Providers Must Send Multiple Transactions

HyperBrick uses a custom liquidity book design inspired by bin-based liquidity provisioning. This architecture provides efficient capital deployment across price ranges but can incur higher gas costs—especially when interacting with many bins.

Why Multiple Transactions Are Required

Due to Hyperliquid’s dual-block structure, small EVM blocks are produced every 1 second with a 2 million gas limit, while large blocks (called "big blocks") are produced every 60 seconds with up to 30 million gas.

However, by default, most user transactions are routed through small blocks—and this is where the issue begins.

Providing liquidity to bins covering more than ~20 price ranges often exceeds the 2M gas limit of a small block.

Because of this, a single transaction cannot include all bin interactions. Instead, users need to:

  1. Split the transaction into multiple parts, each covering a portion of the bins (default 21 bins).

  2. Sign and approve each transaction separately.

  3. Ensure all transactions are confirmed to fully provide liquidity across the desired bin range.

This is a technical limitation of the EVM block gas capacity, not a protocol design flaw.

Can We Use Big Blocks Instead?

Yes—in theory, HyperEVM allows transactions to target big blocks for larger deployments via Big Block

However:

  • This requires converting the user into a Core user by receiving a Core asset like USDC.

  • It adds complexity and friction for most users.

  • HyperBrick currently does not enforce or require the use of big blocks to maintain simplicity and broader accessibility.

🔒 Summary

Action
Reason

Multiple transactions required

Gas limit (2M) on small EVM blocks

Cannot provide >20 bins in 1 tx

Transaction would exceed gas cap

Use big blocks?

Possible but requires Core user conversion

Best practice

Follow UI prompts to submit and approve multiple txs when needed


Subject to Change

This behavior may evolve as Hyperliquid’s infrastructure scales and new tooling (e.g., automatic big block routing) becomes available. HyperBrick will update this flow accordingly to reduce friction for liquidity providers.

Last updated