While markets stayed noisy, Pumex focused inward. Less commentary. More work. The priority was not announcements, but structure.

That work is now live.

Pumex supports v4 liquidity, expanding how liquidity can be deployed, customised, and maintained across the platform. This is not a new protocol version or a surface-level update. It is an upgrade in how liquidity itself is allowed to behave as conditions change.

“Stillness before movement is not hesitation.
It is preparation.”

v4 liquidity introduces a more flexible, programmable liquidity design, built to operate cleanly as usage patterns and market dynamics shift.

v4 liquidity represents a new generation of liquidity architecture focused on customisation and efficiency.

At its core is a singleton-style design, where all pools are managed within a single contract rather than each pool requiring its own deployment. This significantly reduces the cost of pool creation and lowers execution costs for more complex swap paths.

Layered on top of this are hooks.

Hooks allow external logic to run at specific moments in a pool’s lifecycle, such as before or after swaps, or when liquidity is added or removed. This makes it possible to design pools with behaviour tailored to their purpose rather than forcing all liquidity to behave the same way.

Liquidity becomes intentional rather than generic.

v4 builds on the foundation of concentrated liquidity, where capital is deployed within defined price ranges instead of spread thinly across the entire curve.

This improves capital efficiency for liquidity providers and allows pools to reflect realistic price movement rather than theoretical extremes.

What changes in v4 is flexibility.

Pools are now defined by a small set of core parameters, including assets, fee configuration, tick spacing, and optional logic modules. This turns liquidity into a specialised asset that can be shaped around real conditions instead of fixed assumptions.

Two architectural changes account for most of the efficiency gains.

First, the singleton design reduces duplication. Managing pools within a unified contract cuts deployment overhead and lowers gas costs for multi-step swaps.

Second, flash-style accounting changes how balances are handled during execution. Instead of transferring assets after every intermediate step, balances are settled once at the end of the transaction.

Fewer transfers.
Lower gas usage.
Cleaner execution.

Supporting v4 liquidity expands the range of liquidity strategies Pumex can coordinate.

This is not about chasing complexity. It is about building the capacity to support liquidity that can adapt as conditions change, without destabilising the system.

Programmable liquidity allows incentives to be aligned more precisely, depth to be managed more deliberately, and behaviour to evolve without tearing down existing structures.

That capability matters most when markets stop behaving politely.

Injective is building towards a market structure that extends beyond crypto-native assets.

As real-world assets and on-chain equities become more prominent, liquidity requirements change. Depth needs to behave predictably. Fees need to adapt to different trading profiles. Risk characteristics are not uniform.

v4 liquidity provides the structural flexibility to support these environments.

Through programmable logic, liquidity can be tailored to the needs of different asset types. Hooks make it possible to design pools that adjust behaviour based on usage, volatility, or asset-specific constraints, without fragmenting the system or introducing surface-level complexity.

This is particularly relevant for institutional-style liquidity, where consistency, control, and predictable behaviour matter more than experimentation.

Rather than forcing traditional market structures into crypto-native assumptions, v4 liquidity allows the underlying mechanics to adapt to the asset being traded.

As the Injective ecosystem expands into new asset classes, this flexibility becomes foundational.

On the surface, very little changes.

The interface remains familiar. Workflows stay clean. No one is asked to relearn the platform.

Underneath, liquidity has more room to behave intelligently. Over time, this should translate into more consistent pool behaviour during volatility, incentives that track real usage more closely, and lower friction for advanced liquidity strategies.

The experience feels steadier because the structure underneath it is more flexible.

The quiet period was intentional.

v4 liquidity is not a cosmetic upgrade. It is groundwork. A strengthening of how liquidity is shaped, controlled, and sustained so the platform can operate calmly under pressure and scale without compromising stability.

v4 liquidity is now live on Pumex.

The structure is firmer.
The footing is steadier.
Liquidity is ready to move.

While markets stayed noisy, Pumex focused inward. Less commentary. More work. The priority was not announcements, but structure.

That work is now live.

Pumex supports v4 liquidity, expanding how liquidity can be deployed, customised, and maintained across the platform. This is not a new protocol version or a surface-level update. It is an upgrade in how liquidity itself is allowed to behave as conditions change.

“Stillness before movement is not hesitation.
It is preparation.”

v4 liquidity introduces a more flexible, programmable liquidity design, built to operate cleanly as usage patterns and market dynamics shift.

v4 liquidity represents a new generation of liquidity architecture focused on customisation and efficiency.

At its core is a singleton-style design, where all pools are managed within a single contract rather than each pool requiring its own deployment. This significantly reduces the cost of pool creation and lowers execution costs for more complex swap paths.

Layered on top of this are hooks.

Hooks allow external logic to run at specific moments in a pool’s lifecycle, such as before or after swaps, or when liquidity is added or removed. This makes it possible to design pools with behaviour tailored to their purpose rather than forcing all liquidity to behave the same way.

Liquidity becomes intentional rather than generic.

v4 builds on the foundation of concentrated liquidity, where capital is deployed within defined price ranges instead of spread thinly across the entire curve.

This improves capital efficiency for liquidity providers and allows pools to reflect realistic price movement rather than theoretical extremes.

What changes in v4 is flexibility.

Pools are now defined by a small set of core parameters, including assets, fee configuration, tick spacing, and optional logic modules. This turns liquidity into a specialised asset that can be shaped around real conditions instead of fixed assumptions.

Two architectural changes account for most of the efficiency gains.

First, the singleton design reduces duplication. Managing pools within a unified contract cuts deployment overhead and lowers gas costs for multi-step swaps.

Second, flash-style accounting changes how balances are handled during execution. Instead of transferring assets after every intermediate step, balances are settled once at the end of the transaction.

Fewer transfers.
Lower gas usage.
Cleaner execution.

Supporting v4 liquidity expands the range of liquidity strategies Pumex can coordinate.

This is not about chasing complexity. It is about building the capacity to support liquidity that can adapt as conditions change, without destabilising the system.

Programmable liquidity allows incentives to be aligned more precisely, depth to be managed more deliberately, and behaviour to evolve without tearing down existing structures.

That capability matters most when markets stop behaving politely.

Injective is building towards a market structure that extends beyond crypto-native assets.

As real-world assets and on-chain equities become more prominent, liquidity requirements change. Depth needs to behave predictably. Fees need to adapt to different trading profiles. Risk characteristics are not uniform.

v4 liquidity provides the structural flexibility to support these environments.

Through programmable logic, liquidity can be tailored to the needs of different asset types. Hooks make it possible to design pools that adjust behaviour based on usage, volatility, or asset-specific constraints, without fragmenting the system or introducing surface-level complexity.

This is particularly relevant for institutional-style liquidity, where consistency, control, and predictable behaviour matter more than experimentation.

Rather than forcing traditional market structures into crypto-native assumptions, v4 liquidity allows the underlying mechanics to adapt to the asset being traded.

As the Injective ecosystem expands into new asset classes, this flexibility becomes foundational.

On the surface, very little changes.

The interface remains familiar. Workflows stay clean. No one is asked to relearn the platform.

Underneath, liquidity has more room to behave intelligently. Over time, this should translate into more consistent pool behaviour during volatility, incentives that track real usage more closely, and lower friction for advanced liquidity strategies.

The experience feels steadier because the structure underneath it is more flexible.

The quiet period was intentional.

v4 liquidity is not a cosmetic upgrade. It is groundwork. A strengthening of how liquidity is shaped, controlled, and sustained so the platform can operate calmly under pressure and scale without compromising stability.

v4 liquidity is now live on Pumex.

The structure is firmer.
The footing is steadier.
Liquidity is ready to move.