We're building Pumex — the MetaDEX of Injective. This post explains what we're building, why we chose Injective, and what it means for the ecosystem.
Why Injective needs a dedicated liquidity layer
Injective is one of the most performant L1s in DeFi: sub-second finality, near-zero transaction costs, a chain architecture purpose-built for financial applications. The infrastructure is there.
But infrastructure alone doesn't create efficient markets. On high-cost networks like Ethereum, gas fees discourage frequent repositioning — capital stays where it is. On Injective, low costs and fast execution remove that friction. Capital moves freely. That's powerful — but it also means liquidity fragments if there's no coordination layer keeping it productive.
That's the gap Pumex fills. Injective handles execution. Pumex handles liquidity.
Built on InjectiveEVM
Injective supports both Cosmos and EVM environments on a single chain. Pumex is built specifically for InjectiveEVM — the EVM execution layer within Injective's L1.
This gives us full Solidity support and familiar EVM tooling for developers, Injective's speed and cost profile for users, bridge access from Ethereum and other EVM chains, and IBC connectivity to the broader Cosmos ecosystem on the native side.
We chose InjectiveEVM because it lets us deploy battle-tested DeFi primitives — concentrated liquidity, V4 hooks, ve-tokenomics — on a chain fast enough and cheap enough to make them work the way they're supposed to.
What Pumex brings to the table
Concentrated liquidity — LPs deploy capital within specific price ranges instead of across the entire curve. Higher capital efficiency, greater fee capture per unit of capital, less idle liquidity.
Automated Liquidity Managers (ALMs) — The Yield Strategy Hub gives LPs access to automated strategies that handle range selection and rebalancing. Rather than managing positions manually, LPs can deposit into strategy vaults that optimize continuously. Multiple ALMs compete for liquidity based on performance, creating a strategy marketplace instead of a static pool list.
Smart trade routing — Every swap evaluates multiple paths and executes the one with the best output after fees and price impact. Multi-hop routes are settled efficiently with flash accounting that nets transfers across hops.
V4 architecture with hooks — An immutable core handles swap and liquidity math. Pluggable hooks extend pool behavior — dynamic fees, custom incentive logic, limit orders — without forcing LPs to migrate. The protocol evolves without breaking what's already working.
ve(3,3) governance — Lock PMX to receive vePMX. Each epoch, vePMX holders vote to direct emissions toward specific pools and strategies. Voters earn 100% of trading fees from the pools they vote for, plus any external incentives (bribes) protocols add to attract votes. The flywheel: votes direct emissions, emissions attract LPs, deeper liquidity improves execution, volume and fees return to voters.
What this means for Injective
For traders — deeper liquidity and better execution on the pairs that matter.
For LPs — capital efficiency with automated strategies, plus gauge-directed emissions for positions staked into active gauges. Note: on Pumex, trading fees flow to vePMX voters; LP returns come from oPMX emissions and position performance.
For protocols — a structured, permissionless way to bootstrap liquidity through gauge voting and bribe incentives, without relying on mercenary capital.
The goal: make Injective the most capital-efficient trading environment in DeFi.
Built to last
Pumex's AMM and ve(3,3) stack are built on audited upstream infrastructure with third-party reviews covering the core architecture. Significant protocol changes go through independent review. Governance operates under a two-tier multisig with 24-hour and 72-hour timelocks. We don't cut corners on security to ship faster.
What's next
We'll publish a detailed roadmap shortly. In the meantime, explore the docs to understand how the protocol works, and follow us on X or join the Discord for updates.