Why Jengev
Jengev is the price provider behind these pools. It is built for Robinhood Chain tokens whose market is a handful of Uniswap pools, including ecosystem tokens: young, volatile, and sometimes taxed on buys or sells by Uniswap v4 hooks.
1
Quotes from the real markets
At every swap it reads the Uniswap v2, v3 and v4 pools where the token actually trades. There is no off-chain price feed for the token, so there is nothing to go stale between updates.
2
All-in prices, including fees and token taxes
What you really pay or receive differs from venue to venue: LP fees, and taxes that some tokens charge through Uniswap v4 hooks (measured on-chain). Jengev compares these all-in prices and quotes just inside the best of them.
3
Any pair, wherever the liquidity is
A pool can pair a token with USDG or with ETH, whichever unit its own markets use. Jengev converts between ETH and USD with Pyth ETH/USD, so a trader gets the pair they want in one swap instead of two. For example, a token that trades mainly against ETH can still have a USDG pool:
4
Wider when it must be, paused only as a last resort
Unusually fast moves and disagreement between venues widen the spread first. Quoting pauses only in clear cases and recovers automatically.
5
Inventory-aware
When the pool holds too much of one token, the quotes lean to rebalance toward 50/50. The reference price itself does not move.
6
Immutable
No owner, no admin setter, no proxy. Each provider is locked into its pool, and its configuration is identified on-chain by a config hash shown on each pool's page.
→
Why it is an advantage
Quoting just inside the best all-in price means aggregators route flow to the pool, and every routed swap earns the spread for LPs. Prices are read at swap time, so the pool keeps quoting even if any off-chain helper stops, and there is no delayed feed to race.
How tokens are chosen
- Tokens are added by hand from a whitelist.
- The venues each provider reads are selected by fixed rules (depth, agreement with other venues) and tested against recorded market history before deployment.
- The code went through a self-audit (static analysis, invariant and fuzz tests, attack simulations on a fork) before the first deployment.
The provider source code is not published. Behaviour is described here; the deployed contracts and their config hashes are listed on each pool page.
On the name
je' — to buy
ngev — to sell
The name is forged from the Klingon tongue, a language of warriors that wastes no syllable on courtesy. Two verbs, struck together on one anvil: je', to buy, and ngev, to sell. Every quote this provider gives is exactly that pair — a bid and an ask, offered in the same breath — and so its name is nothing more and nothing less than its duty.
A warrior does not haggle, and does not flee the field. Jengev names its price at every swap, holds it just inside the best the markets can offer, widens its guard when the battle turns, and sheathes its blade only when honour demands it. Then it returns. Always it returns.
Klingon spelling writes the pair as je'ngev; the apostrophe was left on the battlefield.